-
Notifications
You must be signed in to change notification settings - Fork 384
OCPBUGS-58475: Enforce secure TLS settings in CMO #2618
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
Conversation
|
@danielmellado: This pull request references Jira Issue OCPBUGS-58475, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn 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 openshift-eng/jira-lifecycle-plugin repository. |
|
/jira refresh |
|
@danielmellado: This pull request references Jira Issue OCPBUGS-58475, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
Requesting review from QA contact: DetailsIn 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 openshift-eng/jira-lifecycle-plugin repository. |
|
@danielmellado: This pull request references Jira Issue OCPBUGS-58475, which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: DetailsIn 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 openshift-eng/jira-lifecycle-plugin repository. |
|
/test golangci-lint |
35bc3bd to
b046c00
Compare
This commit enforces secure TLS settings in order to eliminate insecure cipher warnings in cluster-monitoring-operator logs. It changes Alertmanager configurations used by Prometheus and Thanos. - Set `min_version: TLS1.2` and explicitly define secure `cipher_suites` - Applied to all additional Alertmanager configs - Updated tests accordingly Signed-off-by: Daniel Mellado <[email protected]>
|
/retest-required |
4 similar comments
|
/retest-required |
|
/retest-required |
|
/retest-required |
|
/retest-required |
|
@danielmellado: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
/retest-required |
|
/cc @marioferh |
marioferh
left a comment
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
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: danielmellado, marioferh The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest-required |
d59e266
into
openshift:main
|
@danielmellado: Jira Issue OCPBUGS-58475: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-58475 has been moved to the MODIFIED state. DetailsIn 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 openshift-eng/jira-lifecycle-plugin repository. |
|
[ART PR BUILD NOTIFIER] Distgit: cluster-monitoring-operator |
This commit enforces secure TLS settings in order to eliminate insecure
cipher warnings in cluster-monitoring-operator logs. It changes
Alertmanager configurations used by Prometheus and Thanos.
min_version: TLS1.2and explicitly define securecipher_suites