Uploaded image for project: 'Flink'
  1. Flink
  2. FLINK-35340

Flink Kubernetes Operator CRDs not applying correctly

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Minor
    • Resolution: Unresolved
    • kubernetes-operator-1.7.0, kubernetes-operator-1.8.0
    • None
    • Kubernetes Operator
    • None

    Description

      From version 1.7.0 onwards, CRDs include an additional parameter for additionalPrinterColumns, "priority":

        - additionalPrinterColumns:
          - description: Last observed state of the job.
            jsonPath: .status.jobStatus.state
            name: Job Status
            priority: 0
            type: string
          - description: "Lifecycle state of the Flink resource (including being rolled\
              \ back, failed etc.)."
            jsonPath: .status.lifecycleState
            name: Lifecycle State
            priority: 0
            type: string 

      When applying the CRDs initially or as an upgrade the CRD doesn't apply correctly and omits the newly added "priority" field. This is both tested on a fresh install via Minikube as well as an existing GKE deployment.

      For what it's worth, the versions test on is k8s v1.29.3. When applying these CRDs, there is no error message that comes up and nothing appears in the api server logs.

      Attachments

        Activity

          People

            Unassigned Unassigned
            neilprasad Neil Prasad
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: