-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Improve Helm post-setup NOTES #11269
Improve Helm post-setup NOTES #11269
Conversation
Please set the appropriate release note label. |
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.
Nice work, the output you posted on the other issue looks accurate and helpful.
We might consider adding an extra piece of notes below this chunk to mention Hubble; other than that I don't think any of the toplevel charts need specific logic to generate different notes.
Two more comments below on phrasing.
@@ -1,4 +1,10 @@ | |||
You have successfully installed {{ title .Chart.Name }}. | |||
{{- if (and (.Values.preflight.enabled) (not (.Values.agent.enabled)) (not (.Values.config.enabled)) (not (.Values.operator.enabled))) }} | |||
You have successfully completed the prefight check. |
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.
I'm actually wondering about the phrasing here. The only thing we know was successful at this point in time is that the YAMLs were generated and injected into the cluster.
Looking at the preflight check documentation, we actually suggest using another command to monitor the status of the prefilght check until it becomes successful. I wonder if those instructions would be appropriate to include in the snippet here?
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.
Will check it out and see what makes sense.
You are right, I missed the hubble-ui, since it has already merged, we can add that too. |
9b522ba
to
e333e39
Compare
You have successfully ran the prefight check. | ||
Now make sure to check the number of READY pods is the same as the number of running cilium pods. | ||
Then make sure the cilium preflight deployment is also marked READY 1/1. | ||
If you have an issues please refer to the CNP Validation section in the upgrade guide. |
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.
I recognize that the user likely already has the upgrade docs up at this point so this should make sense without needing to add a direct link to the upgrade guide.
test-me-please |
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.
Blocking the merge until https://github.com/cilium/cilium/pull/11269/files#r419407275 has been discussed.
This PR fixes the NOTES.txt file to reflect the correct action at the upper level, when preflight alone is installed. Also adds the NOTES.txt file that was missing for hubble-ui and handles the hubble-ui and hubble-cli text in the upper level NOTES.txt file. Fixes: cilium#11245 Signed-off-by: Swaminathan Vasudevan <svasudevan@suse.com>
e333e39
to
f33e8df
Compare
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.
Awesome, thank you!
test-me-please |
Note to backporters: When backporting this commit, please do not backport the file creation of |
This PR fixes the NOTES.txt file to reflight the correct
action at the upper level, when preflight alone is installed
Fixes: #11245
Signed-off-by: Swaminathan Vasudevan svasudevan@suse.com