-
Notifications
You must be signed in to change notification settings - Fork 222
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
Add jinja template support to pod-name config via environment variable #1368
Add jinja template support to pod-name config via environment variable #1368
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.
It would be awesome to add this to gateway provisioners as well!
docs/source/users/kernel-envs.md
Outdated
@@ -75,7 +75,9 @@ There are several supported `KERNEL_` variables that the Enterprise Gateway serv | |||
cases, Enterprise Gateway will honor that value. However, when provided, | |||
it is the user's responsibility that KERNEL_POD_NAME is unique relative to | |||
any pods in the target namespace. In addition, the pod must NOT exist - | |||
unlike the case if KERNEL_NAMESPACE is provided. | |||
unlike the case if KERNEL_NAMESPACE is provided. The KERNEL_POD_NAME can | |||
also be provided as a jinja2 template (e.g "{{ kernel_id }}") string which |
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 it would be good to show a practical example rather than just kernel-id. Could you please add a string prefix like "my-kernel" or something?
f7abefa
to
2a213b6
Compare
for more information, see https://pre-commit.ci
@kevin-bates I added a little more complex jinja template, hopefully gives a better picture to users. As for gateway-provisioners, please let me know where to... |
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.
Excellent. Thank you @lresende!
No description provided.