-
Story
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
Quality / Stability / Reliability
-
False
-
-
False
-
None
-
None
-
None
-
None
Add end-to-end tests to verify operator respects cluster-wide and CRD-level TLS profiles.
Test file to create:
- test/e2e/e2e_tls_test.go
Test scenarios:
1. Default TLS Profile:
- Deploy Kueue without TLS profile in CRD or APIServer
- Verify Intermediate profile is applied (TLS 1.2 minimum)
- Verify correct cipher suites are used
2. Cluster-wide TLS Profile:
- Set TLS profile on APIServer to Old
- Deploy Kueue without TLS profile in CRD
- Verify Old profile is applied to Kueue endpoints
3. CRD Override:
- Set TLS profile on APIServer to Intermediate
- Set TLS profile on Kueue CRD to Modern
- Verify Modern profile takes precedence
4. Dynamic Updates:
- Deploy Kueue with Intermediate profile
- Change APIServer TLS profile to Old
- Verify Kueue pods are rolled out with new TLS settings
5. Custom Profile:
- Set Custom TLS profile with specific ciphers
- Verify only specified ciphers are accepted
Acceptance Criteria:
- E2E tests verify TLS settings on all Kueue endpoints
- Tests verify dynamic TLS profile updates
- Tests verify CRD override precedence
- Tests run in CI pipeline
Depends on: OCPKUEUE-464 (unit tests)