Thanks, that fixed the problem! Sadly I am now running into a different problem with S3 HA when running in standalone mode, see https://lists.apache.org/thread/rf62htkr6govpr41fj3br4mzplsg9vg8
Cheers, Javier El vie, 7 oct 2022 a las 22:02, Gyula Fóra (<gyula.f...@gmail.com>) escribió: > Hi! > > Seems like you still have an older version CRD installed for the > FlinkDeployment which doesn’t contain the newly introduced mode setting. > > You can check > > https://nightlies.apache.org/flink/flink-kubernetes-operator-docs-release-1.2/docs/operations/upgrade/ > for the upgrade process. > > Cheers > Gyula > > On Sat, 8 Oct 2022 at 00:00, Javier Vegas <jve...@strava.com> wrote: > >> >> I am following the operator quickstart >> >> https://nightlies.apache.org/flink/flink-kubernetes-operator-docs-release-1.2/docs/try-flink-kubernetes-operator/quick-start/ >> >> kubectl create -f >> https://raw.githubusercontent.com/apache/flink-kubernetes-operator/release-1.2/examples/basic.yaml >> >> >> works fine, but >> >> >> kubectl create -f >> https://raw.githubusercontent.com/apache/flink-kubernetes-operator/release-1.2/examples/basic-reactive.yaml >> >> >> which has the mode: standalone setting >> >> >> gives me this error: >> >> >> error: error validating " >> https://raw.githubusercontent.com/apache/flink-kubernetes-operator/release-1.2/examples/basic-reactive.yaml": >> error validating data: ValidationError(FlinkDeployment.spec): unknown field >> "mode" in org.apache.flink.v1beta1.FlinkDeployment.spec; if you choose to >> ignore these errors, turn validation off with --validate=false >> >> >> >>
