[feat]Add centrally managed TLS configuration for console-plugin nginx#3218
[feat]Add centrally managed TLS configuration for console-plugin nginx#3218jkhelil wants to merge 1 commit intotektoncd:mainfrom
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Manual Validation — TLS Propagation from APIServer Profile to nginxTested on OCP cluster: SetupTest 1 — Intermediate Profile (default, no tlsSecurityProfile set)APIServer TLS Profile:
Generated nginx.conf (server block): ✅ Test 2 — Old Profile (TLS 1.0+)Generated nginx.conf (server block) after reconcile: ✅ Observations
TektonConfig state: |
Summary
Enables the console-plugin nginx server to inherit TLS settings from the centrally managed APIServer TLS Profile for Post-Quantum Cryptography (PQC) readiness compliance.
Changes
Modified:
pkg/reconciler/openshift/tektonconfig/console_plugin_reconciler.goTLS_MIN_VERSION,TLS_CIPHER_SUITES,TLS_CURVE_PREFERENCES)Modified:
pkg/reconciler/openshift/tektonconfig/console_plugin_reconciler_test.goTest Results
Test 1: Default Configuration (No Env Vars)
Environment:
Generated nginx.conf:
Result: ✅ Pod starts successfully, TLS 1.3 negotiated, no errors
Test 2: With TLS Environment Variables
Environment:
Generated nginx.conf:
Result: ✅ Pod starts successfully, TLS 1.3 negotiated, curves applied, no errors
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
make test lintbefore submitting a PRSee the contribution guide for more details.
Release Notes