-
Notifications
You must be signed in to change notification settings - Fork 120
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
Mention kapp default update strategy flag in faq #774
Mention kapp default update strategy flag in faq #774
Conversation
fa47ae6
to
494c8bc
Compare
✅ Deploy Preview for carvel ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for carvel ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
LGTM! Thank you for the changes @ringerc! Could you please make the changes in older versions as well? |
@praveenrewar How far back, which versions? Do you have a backport script or helper, or just tend to diff, apply, resolve conflicts? I can do latest-stable. Will update PR. |
That will do. Thank you! |
Add mention of the kapp `--apply-default-update-strategy` flag to the FAQ and the annotation docs. Backport to latest stable. Signed-off-by: Craig Ringer <[email protected]>
1e61229
to
c9c238d
Compare
@praveenrewar Rebased and backported |
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.
LGTM! Thank you for the change!
Add mention of the kapp
--apply-default-update-strategy
flag to the FAQ and the annotation docs.This would've been helpful to me as it was not immediately obvious how to force kapp to replace resources in case of label conflicts or other issues that prevent patching.