Skip to content

STOR-2809: Central TLS Profile consistency#579

Open
dfajmon wants to merge 1 commit intoopenshift:mainfrom
dfajmon:tls-config
Open

STOR-2809: Central TLS Profile consistency#579
dfajmon wants to merge 1 commit intoopenshift:mainfrom
dfajmon:tls-config

Conversation

@dfajmon
Copy link
Contributor

@dfajmon dfajmon commented Feb 3, 2026

Changes include:

  • add TLS cipher version and suites
  • enable tls-profiles feature
  • implement configobserver
  • update vendor

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 3, 2026
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Feb 3, 2026

@dfajmon: This pull request references STOR-2809 which is a valid jira issue.

Details

In response to this:

add TLS cipher version
enable tls-profiles feature

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
Contributor

openshift-ci bot commented Feb 3, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dfajmon

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 Feb 3, 2026
@dfajmon
Copy link
Contributor Author

dfajmon commented Feb 3, 2026

/retest-required

@dfajmon
Copy link
Contributor Author

dfajmon commented Feb 5, 2026

/test e2e-operator

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Mar 3, 2026

@dfajmon: This pull request references STOR-2809 which is a valid jira issue.

Details

In response to this:

Changes include:

  • add TLS cipher version and suites
  • enable tls-profiles feature
  • implement configobserver
  • update vendor

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.

add TLS cipher version and suites
enable tls-profiles feature
implement configobserver
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 9, 2026

@dfajmon: 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.

func GetTLSProfileValues(ctx context.Context, c client.Client) (minVersion, cipherSuites string, err error) {
listers := &apiServerListers{&clientAPIServerLister{client: c, ctx: ctx}}
// InMemoryRecorder captures change events without logging them on every reconcile.
recorder := libevents.NewInMemoryRecorder("tls-profile", clock.RealClock{})
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not sure about using in-memory recorder here. in-memory recorder is mainly used for tests.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see how LocalVolumeDeviceDiscovery controller do not instantiate a proper recorder, but IMO that can be fixed and an explicit recorder passed to GetTLSProfileValues function.

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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants