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
Expose the pod name/namespace to APB #546
Conversation
Use kubernetes downward API to expose the pod name and namespace to the APB. This will give us more flexibility w.r.t. managing APB execution, secrets, and annotations.
|
I know that @maleck13 was working on the proposal in #537 where APBs could annotate themselves. Also, if we wish to move away from @shawn-hurley I remember you suggesting using volumes, I can make that change, I just wanted to get eyeballs on this change. |
|
This looks pretty reasonable to me. Wondering what advantages we would gain from using a volume rather than an envvar? |
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.
Man kube apis are heinously ugly. My eyes hurt.
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.
LGTM. This could also be used for handling deprovision as we expand the capability to do multiple provisions in the same namespace.
Use kubernetes downward API to expose the pod name and namespace to the APB. This will give us more flexibility w.r.t. managing APB execution, secrets, and annotations.
Use kubernetes downward API to expose the pod name and namespace to the
APB. This will give us more flexibility w.r.t. managing APB execution,
secrets, and annotations.