I think you forgot to upgrade the CRD during the upgrade process on your
cluster.

As you can see here:
https://github.com/apache/flink-kubernetes-operator/blob/release-1.4/helm/flink-kubernetes-operator/crds/flinkdeployments.flink.apache.org-v1.yml#L38-L44
The newer version already contains support for 1.17.

For docs you can refer to:
https://nightlies.apache.org/flink/flink-kubernetes-operator-docs-main/docs/operations/upgrade/#1-upgrading-the-crd


Cheers,
Gyula

On Tue, Mar 28, 2023 at 10:29 PM Ivan Webber via user <user@flink.apache.org>
wrote:

> Hello Flink Users:
>
>
>
> I'm trying to upgrade to use Flink 1.17.0 with my pipeline in order to
> have support for writing to Azure Data Lake Storage. However when I change
> the `spec.flinkVersion` to v1_17 I get an error message:
>
>
>
> ```bash
>
> The FlinkDeployment "test-replay-streaming-run" is invalid:
> spec.flinkVersion: Unsupported value: "v1_17": supported values: "v1_13",
> "v1_14", "v1_15", "v1_16"
>
> ```
>
>
>
> The documentation (here
> <https://flink.apache.org/downloads/#:~:text=Flink%20version(s)%3A-,1.17.0,-1.16.1>)
> says latest version of Flink Operator (1.4) should support 1.17.0 and I
> made sure to update by running the below commands. I’m wondering if an Enum
> needs updated or if the latest stable Flink Operator doesn’t actually
> support 1.17.0 yet. Any pointers would be appreciated.
>
>
>
> ```bash
>
> helm uninstall flink-kubernetes-operator
> flink-operator-repo/flink-kubernetes-operator
>
> helm repo rm flink-operator-repo
>
> helm repo add flink-operator-repo
> https://downloads.apache.org/flink/flink-kubernetes-operator-1.4.0/
>
> helm install flink-kubernetes-operator
> flink-operator-repo/flink-kubernetes-operator
>
> ```
>
>
>
> Thanks,
>
>
>
> Ivan Webber
>
>
>

Reply via email to