[docs] add a warning for ServiceEntry in migration steps #624
Conversation
This file contains hidden or 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
Signed-off-by: Cameron Garrison <[email protected]>
|
Hi @cam-garrison, I believe this is partly covering https://issues.redhat.com/browse/OSSM-11390. Could you please extend the text to also cover remaining parts of that jira so it can be also closed? e.g. a workaround and how to verify if your 2.6 installation is affected. We also have https://issues.redhat.com/browse/OSSM-11391 but that's lower priority I think. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Add a warning for users to check their ServiceEntry resources based on recent issues hit by customers.