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

[openshift-cherrypick-robot]

This is an automated cherry-pick of #258

/assign openshift-cherrypick-robot

/cherrypick release-coo-ocp-4.12

[openshift-ci-robot]

@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: TRACING-6116

Details

In response to this:

This is an automated cherry-pick of #258

/assign openshift-cherrypick-robot

/cherrypick release-coo-ocp-4.12

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]

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: f40fe1e0-7a73-4a57-b429-b2bd57826b5c

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

---

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

[andreasgerstmayr]

/lgtm

[openshift-ci]

[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:

• OWNERS [andreasgerstmayr]

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

[IshwarKanse]

/label qe-approved

[openshift-ci-robot]

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

Details

In response to this:

This is an automated cherry-pick of #258

/assign openshift-cherrypick-robot

/cherrypick release-coo-ocp-4.12

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]

@openshift-cherrypick-robot: 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.

[openshift-cherrypick-robot]

@openshift-cherrypick-robot: #259 failed to apply on top of branch "release-coo-ocp-4.12":

Applying: Add TLS min version and cipher suite configuration support
Using index info to reconstruct a base tree...
M	go.mod
M	go.sum
M	pkg/server.go
Falling back to patching base and 3-way merge...
Auto-merging pkg/server.go
Auto-merging go.sum
CONFLICT (content): Merge conflict in go.sum
Auto-merging go.mod
CONFLICT (content): Merge conflict in go.mod
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Patch failed at 0001 Add TLS min version and cipher suite configuration support

Details

In response to this:

This is an automated cherry-pick of #258

/assign openshift-cherrypick-robot

/cherrypick release-coo-ocp-4.12

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.