Extend korifi diff CF docs with container lifecycle #2930
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
beyhan
force-pushed
the
add-container-lifecycle-diff-info
branch
from
c79b20d
to
32ad76f
Compare
danail-branekov
approved these changes
Oct 10, 2023
As discussed in cloudfoundry#2913 there is a difference in the Korifi behaviour during a rolling update compared to CF on VMs. That is why, I think that it makes sense to document this at the moment.
danail-branekov
force-pushed
the
add-container-lifecycle-diff-info
branch
from
32ad76f
to
a6419ad
Compare
danail-branekov
approved these changes
Oct 10, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Is there a related GitHub Issue?
#2913
What is this change about?
As discussed in #2913 there is a difference in the Korifi behaviour during a rolling update compared to CF on VMs. That is why, I think that it makes sense to document this at the moment.
Does this PR introduce a breaking change?
No
Acceptance Steps
Docs change