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.
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
Update install instructions, making them consistent for all sub-projects #1449
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: Tim Ramlot <42113979+inteon@users.noreply.github.com>
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
✅ Deploy Preview for cert-manager-website ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Seems like unnecessary churn to me.
- It introduces the cert-manager version everywhere, giving the false impression (I think) that istio-csr, csi-driver, etc depend on that particular version. As I already said in another review.
- I think the goal should be to remove the
helm **upgrade**
instruction from each of the component install pages, because it risks users accidentally upgrading an important existing cert-manager installation and this change does not advance that goal. - I don't have time to test all the changes.
Have you tested everything?
Have you tested everything? |
PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Goal:
Reach base level of consistency for installation commands across all installation pages.
Once we reach consistency, we can think about improving these instructions (keeping in mind the CRD changes coming in 1.15).
Next steps:
helm upgrade --install
vshelm upgrade
vshelm install
in our instructions & update.