Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Separately publish CRD.yaml in relases #793

Open
jacksgt opened this issue May 20, 2022 · 5 comments
Open

Separately publish CRD.yaml in relases #793

jacksgt opened this issue May 20, 2022 · 5 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. triage/wg-discuss Indicates an issue that needs to be discussed during a working group call.

Comments

@jacksgt
Copy link
Contributor

jacksgt commented May 20, 2022

For installing the Helm chart and CRDs separately, it would be super useful to have separate openshift-crds.yaml and kubernetes-crds.yaml files attached to the Github releases.

It should be fairly simply to extract these manifests when generating the kustomize manifests during the release process.
@jacksgt jacksgt added the kind/bug Categorizes issue or PR as related to a bug. label May 20, 2022
@nikhil-thomas
Copy link
Member

/grooming

@nikhil-thomas nikhil-thomas added the grooming This issue is used during working group to mark issues to be discussed label May 25, 2022
@jacksgt jacksgt mentioned this issue May 31, 2022
Closed
3 tasks
@vdemeester vdemeester added triage/wg-discuss Indicates an issue that needs to be discussed during a working group call. and removed grooming This issue is used during working group to mark issues to be discussed labels Jun 2, 2022
@tekton-robot
Copy link
Contributor

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

@tekton-robot tekton-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 31, 2022
@vdemeester vdemeester added triage/wg-discuss Indicates an issue that needs to be discussed during a working group call. and removed triage/wg-discuss Indicates an issue that needs to be discussed during a working group call. labels Sep 1, 2022
@piyush-garg
Copy link
Contributor

@jacksgt Is this still valid as we have started publishing helm charts. cc @sm43

@tekton-robot
Copy link
Contributor

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle rotten

Send feedback to tektoncd/plumbing.

@tekton-robot tekton-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Oct 1, 2022
@jacksgt
Copy link
Contributor Author

jacksgt commented Oct 3, 2022

/remove-lifecycle rotten

/lifecycle frozen

@tekton-robot tekton-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels Oct 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. triage/wg-discuss Indicates an issue that needs to be discussed during a working group call.
Projects
Tekton Community Roadmap
Status: Todo
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Generate standalone CRDs manifests and update Helm chart in release pipeline jacksgt/operator
5 participants
@vdemeester @nikhil-thomas @jacksgt @piyush-garg @tekton-robot