APIServer compatibility is failing

[liangyuanpeng]

What happened:

https://github.com/karmada-io/karmada/actions/runs/15241477746/job/42862086548

KEP-3998 brings JobSuccessPolicy, it means that the feature-gate is enabled, JobSuccessCriteriaMet status needs to be added when the job is completed .

this feature-gate introduced as :

• alpha in 1.30 (false by default)
• beta in 1.31 (true by default)
• GA in 1.33 (lock to true )

workflow is failing with karmada-apiserver 1.32 and not 1.31, let me check it.

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

• Karmada version:
• kubectl-karmada or karmadactl version (the result of kubectl-karmada version or karmadactl version):
• Others:

[liangyuanpeng]

Another feature-gate related to "job" is JobManagedBy:

- name: JobManagedBy
  versionedSpecs:
  - default: false
    lockToDefault: false
    preRelease: Alpha
    version: "1.30"
  - default: true
    lockToDefault: false
    preRelease: Beta
    version: "1.32"

If set JobManagedBy to true, We will get the same error on karmada-apiserver 1.31:

Invalid value: cannot set Complete=True condition without the SuccessCriteriaMet=true condition"

[RainbowMango]

https://github.com/karmada-io/karmada/actions/runs/15241477746/job/42862086548

This test is against Kubernetes v1.30? As you mentioned the feature became enabled default since v1.31.