-
Notifications
You must be signed in to change notification settings - Fork 1.8k
OCPBUGS-57824 added Known Issues section to cert-manager release notes #96128
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
base: main
Are you sure you want to change the base?
Conversation
5860ffa
to
ff85fe4
Compare
🤖 Tue Jul 15 19:40:42 - Prow CI generated the docs preview: |
[id="cert-manager-operator-1-16-1-known-issues_{context}"] | ||
=== Known Issues | ||
|
||
When using the Venafi issuer with username/password authentication in cert-manager versions 1.16.0 and later, the default client ID is hardcoded as `cert-manager.io` and cannot be customized. This limitation can affect users requiring a specific client ID for authentication with the Venafi platform. Support for configurable client IDs will be introduced in cert-manager version 1.17.0. |
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.
🤖 [error] RedHat.TermsErrors: Use 'hard-coded' rather than 'hardcoded'. For more information, see RedHat.TermsErrors.
ff85fe4
to
778010c
Compare
@wgabor0427: all tests passed! Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
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.
We need to add this into 1.16.0 section (this place:
[id="cert-manager-operator-1-16-1-known-issues_{context}"] | ||
=== Known Issues | ||
|
||
When using the Venafi issuer with username/password authentication in cert-manager versions 1.16.0 and later, the default client ID is hard-coded as `cert-manager.io` and cannot be customized. This limitation can affect users requiring a specific client ID for authentication with the Venafi platform. Support for configurable client IDs will be introduced in cert-manager version 1.17.0. |
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.
When using the Venafi issuer with username/password authentication in cert-manager versions 1.16.0 and later, the default client ID is hard-coded as `cert-manager.io` and cannot be customized. This limitation can affect users requiring a specific client ID for authentication with the Venafi platform. Support for configurable client IDs will be introduced in cert-manager version 1.17.0. | |
When using the Venafi issuer with username/password authentication in cert-manager version 1.16.0, the default client ID is hard-coded as `cert-manager.io` and cannot be customized. This limitation can affect users requiring a specific client ID for authentication with the Venafi platform. Support for configurable client IDs will be introduced in cert-manager version 1.17.0. |
Version(s):
4.14+
Issue:
https://issues.redhat.com/browse/OCPBUGS-57824
Link to docs preview:
https://96128--ocpdocs-pr.netlify.app/openshift-enterprise/latest/security/cert_manager_operator/cert-manager-operator-release-notes.html
QE review:
Additional information: