Skip to content
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

Job level webhook for metrics collector sidecar container #928

Closed
hougangliu opened this issue Nov 24, 2019 · 6 comments
Closed

Job level webhook for metrics collector sidecar container #928

hougangliu opened this issue Nov 24, 2019 · 6 comments

Comments

@hougangliu
Copy link
Member

/kind feature
/P2
Describe the solution you'd like
[A clear and concise description of what you want to happen.]
for now, we inject metrics collector sidecar container in Pod webhook, we can consider metrics collector sidecar container in Job webhook level for performance.

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

@johnugeorge
Copy link
Member

/priority p2

@johnugeorge
Copy link
Member

This is no more required in k8s 1.15 as we could use more efficient object selector in web hooks

@vpavlin
Copy link
Member

vpavlin commented Dec 17, 2019

This could actually solve #963 as it would reorder actions - first add the container in the Job and then let a job controller generate the pod, so it makes sense form my point of view:)

@hougangliu
Copy link
Member Author

hougangliu commented Dec 19, 2019

This could actually solve #963 as it would reorder actions - first add the container in the Job and then let a job controller generate the pod, so it makes sense form my point of view:)

@vpavlin yes, it can solve #963, but it is low priority as plan and will be included in Kubeflow 1.0 release. As #964 (comment), I think #963 is a very common issue for openshift, we should solve it in a common way.

@stale
Copy link

stale bot commented Nov 25, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale
Copy link

stale bot commented Dec 19, 2020

This issue has been automatically closed because it has not had recent activity. Please comment "/reopen" to reopen it.

@stale stale bot closed this as completed Dec 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants