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

Add tlsSecurityProfile field to Kueue CRD

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • None
    • None

      Add optional TLSSecurityProfile field to KueueOperandSpec for operator-level TLS override.

      File to modify:

      • pkg/apis/kueueoperator/v1/types.go

      Implementation:

      import (
          configv1 "github.com/openshift/api/config/v1"
      )
      
      type KueueOperandSpec struct {
          operatorv1.OperatorSpec `json:",inline"`
          // config is the desired configuration for the Kueue operator.
          // +required
          Config KueueConfiguration `json:"config"`
          // tlsSecurityProfile specifies TLS settings for the Kueue components.
          // When not specified, the cluster-wide APIServer TLS profile is used.
          // When the cluster-wide profile is also not specified, the Intermediate profile is used.
          // +optional
          TLSSecurityProfile *configv1.TLSSecurityProfile `json:"tlsSecurityProfile,omitempty"`
      }
      

      Additional tasks:

      • Run make generate to regenerate deepcopy functions
      • Run make manifests to update CRD YAML files
      • Update bundle manifests

      Acceptance Criteria:

      • TLSSecurityProfile field added to Kueue CRD
      • CRD accepts Old, Intermediate, Modern, and Custom profile types
      • CRD manifests regenerated and committed

      No upstream dependency - can start immediately

              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: