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
Helm: Improved description for tunnel, tunnelProtocol, routingMode flags #27926
Helm: Improved description for tunnel, tunnelProtocol, routingMode flags #27926
Conversation
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.
Travis is failing with a legitimate error:
HINT: to fix this, run 'make -C Documentation update-helm-values'
Otherwise this looks good to me from a Helm perspective.
c35453d
to
fd3dd22
Compare
Ugh, I forgot about this, thanks @gandro! I just run this command and git amend'ed the generated file. |
Restarting both |
/test |
fd3dd22
to
3ee196c
Compare
- Improved description for tunnel, tunnelProtocol, routingMode flags to make it clearer for users to know the possible values. - Added deprecation note for the tunnel flag to be in line with the v1.14.0 release notes and cilium#24561. Signed-off-by: Philip Schmid <philip.schmid@isovalent.com>
3ee196c
to
53d4125
Compare
Rebased & fixed two word spellings. @gandro, @nathanjsweet do you think we could merge this PR anytime soon? Let's please backport this to 1.14. For 1.15, |
The main reason why this was not yet merged is that there is an outstanding review request for docs by @qmonnet - Quentin, mind taking a look? Otherwise I think we can merge without docs approval, since the changes mainly affect the Helm README. Let's also run CI and then this should be mergable. |
/test |
|
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.
Looks all good, thanks
--tunnel
flag to allow setting a tunneling protocol for a subset of traffic #24561.Please ensure your pull request adheres to the following guidelines:
Internal Slack discussion: https://isovalent.slack.com/archives/C01742ANV9P/p1693834569477619