Skip to content

Conversation

@jmesnil
Copy link
Contributor

@jmesnil jmesnil commented Nov 26, 2025

This updates the list of tls cipher suites allowed for the kube-rbac-proxy container of the insight-runtime-extractor resources.

JIRA: https://issues.redhat.com/browse/OCPBUGS-62239

  • Bugfix

Breaking Changes

No

This updates the list of tls cipher suites allowed for the kube-rbac-proxy
container of the insight-runtime-extractor resources.

JIRA: https://issues.redhat.com/browse/OCPBUGS-62239

Signed-off-by: Jeff Mesnil <[email protected]>
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Nov 26, 2025
@openshift-ci
Copy link

openshift-ci bot commented Nov 26, 2025

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@openshift-ci-robot openshift-ci-robot added jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Nov 26, 2025
@openshift-ci-robot
Copy link
Contributor

@jmesnil: This pull request references Jira Issue OCPBUGS-62239, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.21.0) matches configured target version for branch (4.21.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

This updates the list of tls cipher suites allowed for the kube-rbac-proxy container of the insight-runtime-extractor resources.

JIRA: https://issues.redhat.com/browse/OCPBUGS-62239

  • Bugfix

Breaking Changes

No

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.

@openshift-ci
Copy link

openshift-ci bot commented Nov 26, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: jmesnil
Once this PR has been reviewed and has the lgtm label, please assign ncaak for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@jmesnil
Copy link
Contributor Author

jmesnil commented Dec 10, 2025

/test all

@openshift-ci
Copy link

openshift-ci bot commented Dec 10, 2025

@jmesnil: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/insights-operator-e2e-tests 9a15e7e link true /test insights-operator-e2e-tests
ci/prow/e2e-gcp-ovn-techpreview 9a15e7e link true /test e2e-gcp-ovn-techpreview

Full PR test history. Your PR dashboard.

Details

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants