-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Service Catalog API Server should use service serving-cert-secret-name #7924
Comments
/assign jboyd01 |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
@openshift-bot: Closing this issue. 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/test-infra repository. |
Service Catalog API Server creates a self signed SSL cert in roles/openshift_service_catalog/tasks/generate_certs.yml. We should not do this as it creates a big issue for cert renewal for customers. Instead we should make use of auto cert creation/renewal via the service annotation service.alpha.openshift.io/serving-cert-secret-name.
This issue exists in versions 3.7-3.10. This issue should be fixed in 3.11.
The text was updated successfully, but these errors were encountered: