Update installation documentation to handle kube object removal #6668
Assignees
Labels
good first issue
Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
Hacktoberfest
Categorizes issue as one for Hacktoberfest 2021
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
kind/documentation
Categorizes issue or PR as related to documentation.
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
Comments
Shouldn't it be |
|
yes thanks :) |
|
Issues go stale after 90d of inactivity. /lifecycle stale Send feedback to tektoncd/plumbing. |
|
/lifecycle frozen |
|
/assign jgustafsoniii |
|
When running |
|
We could mention here that the install guide is meant for a quickstart with Tekton but not meant for production use. |
|
@afrittoli I ran some tests starting off with v0.46.0 and then tried replace --force and apply --force to see if runs.tekton.dev would disappear but it never did. This was a suggestion from @pritidesai. I agree that the quick start should mention that its not for production use. What should the upgrade steps be if you are upgrading from an older version? |
|
@JGustafsonIII, we had discussion this morning in the API WG, the conclusion of this discussion was to add a note in the installation section first bullet: |
|
Thank you, I will update the doc and submit a PR. |
7 tasks
|
I think this can be closed now @JGustafsonIII ? |
|
@dibyom Yes this can be closed |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Our installation documentation instructs users to use
kubectl apply. However, if a release of Pipelines removes an object in the config folder,kubectl applywill not remove this object from clusters that are upgrading their Pipelines version. For example, we removed theRunCRD, but the CRDruns.tekton.devmay still be present on clusters that have upgraded (it's still present on the dogfood cluster).We should update our documentation to instruct users to install Pipelines w/
kubectl replace, or some other option that will remove Tekton config objects that are no longer present. The Tekton operator may need similar changes as well, but this should be tracked separately.Note: It is unclear whether
kubectl applywill correctly handle changes to the storage version of CRDs.kubectl applywill update any existing CRD definitions; however, the docs make it a bit unclear how these changes are merged:cc @vdemeester
The text was updated successfully, but these errors were encountered: