Skip to content

[release-coo-ocp-4.12] TRACING-6116: Add TLS min version and cipher suite configuration support#260

Merged
openshift-merge-bot[bot] merged 5 commits intoopenshift:release-coo-ocp-4.12from
ozzywalsh:cherry-pick-259-to-release-coo-ocp-4.12
May 7, 2026
Merged

[release-coo-ocp-4.12] TRACING-6116: Add TLS min version and cipher suite configuration support#260
openshift-merge-bot[bot] merged 5 commits intoopenshift:release-coo-ocp-4.12from
ozzywalsh:cherry-pick-259-to-release-coo-ocp-4.12

Conversation

@ozzywalsh
Copy link
Copy Markdown
Contributor

This is a manual cherry-pick of #259 to release-coo-ocp-4.12.

The automated cherry-pick failed due to merge conflicts in go.mod and go.sum. Conflicts were resolved by keeping the 4.12 dependency versions and running go mod tidy.

/assign andreasgerstmayr

ozzywalsh added 5 commits May 6, 2026 14:49
Add --tls-min-version and --tls-cipher-suites flags with env var
fallback (TLS_MIN_VERSION, TLS_CIPHER_SUITES). Uses k8s component-base
for TLS version and cipher suite validation, matching the approach in
the opentelemetry-operator. Defaults to TLS 1.2 when no min version is
specified.
Simplify TLS cipher suites flag handling by using a plain string flag
instead of a custom flag.Value type. The operator is expected to provide
valid values, so whitespace trimming is unnecessary.
Previously errors from k8sapiflag.TLSVersion and TLSCipherSuites were
silently discarded when configuring the proxy TLS settings. This adds
fatal error logging consistent with how the server TLS config handles
parse failures.
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 6, 2026
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented May 6, 2026

@ozzywalsh: This pull request references TRACING-6116 which is a valid jira issue.

Details

In response to this:

This is a manual cherry-pick of #259 to release-coo-ocp-4.12.

The automated cherry-pick failed due to merge conflicts in go.mod and go.sum. Conflicts were resolved by keeping the 4.12 dependency versions and running go mod tidy.

/assign andreasgerstmayr

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.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 6, 2026

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 896494cd-de04-43d0-a3af-1c31842ea761

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

  • Generate code and open pull requests
  • Plan features and break down work
  • Investigate incidents and troubleshoot customer tickets together
  • Automate recurring tasks and respond to alerts with triggers
  • Summarize progress and report instantly

Built for teams:

  • Shared memory across your entire org—no repeating context
  • Per-thread sandboxes to safely plan and execute work
  • Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci openshift-ci Bot requested review from kyoto and zhuje May 6, 2026 13:57
@openshift-ci openshift-ci Bot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label May 6, 2026
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented May 6, 2026

Hi @ozzywalsh. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

@andreasgerstmayr
Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label May 6, 2026
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented May 6, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andreasgerstmayr

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

The pull request process is described 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

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 6, 2026
@andreasgerstmayr
Copy link
Copy Markdown
Contributor

/ok-to-test

@openshift-ci openshift-ci Bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels May 6, 2026
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented May 6, 2026

@ozzywalsh: all tests passed!

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.

@IshwarKanse
Copy link
Copy Markdown
Member

/label qe-approved

@openshift-ci openshift-ci Bot added the qe-approved Signifies that QE has signed off on this PR label May 7, 2026
@openshift-merge-bot openshift-merge-bot Bot merged commit d5df367 into openshift:release-coo-ocp-4.12 May 7, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. qe-approved Signifies that QE has signed off on this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants