Uploaded image for project: 'OpenShift Kueue'
  1. OpenShift Kueue
  2. OCPKUEUE-465

E2E tests for TLS profile compliance

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • 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)

              harpatil@redhat.com Harshal Patil
              harpatil@redhat.com Harshal Patil
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: