Skip to content

Retrieve TLS config from apiserver for OpenShift 5.0 - #2188

Draft
dkwon17 wants to merge 1 commit into
eclipse-che:mainfrom
dkwon17:tls-adherence
Draft

Retrieve TLS config from apiserver for OpenShift 5.0#2188
dkwon17 wants to merge 1 commit into
eclipse-che:mainfrom
dkwon17:tls-adherence

Conversation

@dkwon17

@dkwon17 dkwon17 commented Aug 31, 2026

Copy link
Copy Markdown
Contributor

What does this PR do?

Configures operator webhook and metric server to apply the cluster TLS profile when tlsAdherence is set to StrictAllComponents. Watcher restarts the operator on profile or adherence policy changes.

Screenshot/screencast of this PR

What issues does this PR fix or reference?

How to test this PR?

  1. Deploy the operator:

OpenShift

oc create namespace devworkspace-controller
oc apply --server-side -f https://raw.githubusercontent.com/devfile/devworkspace-operator/refs/heads/main/deploy/deployment/openshift/combined.yaml

OPERATOR_IMAGE=<...>
sed 's|quay.io/eclipse/che-operator:next|'${OPERATOR_IMAGE}'|g' deploy/deployment/openshift/combined.yaml | oc apply --server-side -f  -
oc apply --server-side -f deploy/deployment/openshift/org_v2_checluster.yaml
oc wait checluster eclipse-che -n eclipse-che --for=jsonpath='.status.chePhase'=Active   --timeout=120s

on Minikube

./build/scripts/minikube-tests/test-operator-from-sources.sh

Common Test Scenarios

  • Deploy Eclipse Che
  • Start an empty workspace
  • Open terminal and build/run an image
  • Stop a workspace
  • Check operator logs for reconciliation errors or infinite reconciliation loops

PR Checklist

As the author of this Pull Request I made sure that:

Reviewers

Reviewers, please comment how you tested the PR when approving it.

Configure operator webhook and metrics servers to apply the cluster TLS
profile when tlsAdherence is set to StrictAllComponents. Watcher restarts
the operator on profile or adherence policy changes.

Signed-off-by: David Kwon <dakwon@redhat.com>
Assisted-by: Claude Sonnet 4.6
@openshift-ci

openshift-ci Bot commented Aug 31, 2026

Copy link
Copy Markdown

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

openshift-ci Bot commented Aug 31, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dkwon17

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

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant