-
Notifications
You must be signed in to change notification settings - Fork 733
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
Support CertManager for the Webhook cert generation #2049
Comments
/kind feature |
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. |
/remove-lifecycle stale |
/good-first-issue |
@andreyvelich: Please ensure the request meets the requirements listed here. If this request no longer meets these requirements, the label can be removed In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/assign |
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. |
/remove-lifecycle stale |
Heyy @tariq-hasan are you still working on this issue ? |
Sure, but I suggest that we implement this feature for Kubeflow Training V2 given that V1 is already released. |
Thanks, @andreyvelich , |
/kind feature
Currently, the training-operator generates certs for the webhook using the internal cert generation mechanism for all installation ways.
However, we know that some administrators prefer to use the cert-manager to manage all certifications for security and so on.
So, I would suggest supporting the cert generation mechanism by the cert-manager.
xref: #2035
The text was updated successfully, but these errors were encountered: