-
Notifications
You must be signed in to change notification settings - Fork 17
feat: promote ingress settings to public #177
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
Conversation
|
This pull request has been linked to Shortcut Story #18924: Remove compatibility code for old ingress controller. |
|
This has some of the changes in #169 (namely, exposing the ingress in our docs), but I split it into a separate PR to make it less risky and easier to review |
* Add ingress section to values.yaml and re-generate documentation
* Add tests for ingress settings
* Change comment syntax to {{/* */}} to prevent it from appearing
in the generated Ingress spec
07913a2 to
60a8175
Compare
johnstcn
left a comment
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 haven't tested this, but it looks fine to me. Some minor comments.
Emyrk
left a comment
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.
Those tests look tedious to write!
Do you have ideas for how to improve/simplify the API or test code? I'm open to suggestions! I'm not in love with this code, but it's better than the alternative of manual tests only |
|
Tested this in dev-4 and everything deploys fine, should be safe to merge |
Uh oh!
There was an error while loading. Please reload this page.