-
Notifications
You must be signed in to change notification settings - Fork 54
Documented ingress functionality #416
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
Documented ingress functionality #416
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.
cc: @sutaakar this might be of interest, do we need more details on this documentation?
It is fine for me. |
/lgtm |
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 think we should include this in the actual code as well as descriptions for other config options. This /lgtm though, I will open another issue for documenting options in the source code, no need to make any changes here.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: KPostOffice The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Issue link
Closes #399
What changes have been made
Added documentation detailing the use of the
ingress_domain
andingress_options
config variables.Verification steps
N/A
Checks