Hi Morgan Karl, Could you please post the logs of your operator pod? A possible explanation is that your operator might be stuck in an unhealthy state, hence the webhook can not be accessed.
Best, Marton On Thu, Jul 28, 2022 at 5:37 PM Geldenhuys, Morgan Karl < morgan.geldenh...@tu-berlin.de> wrote: > Greetings all, > > > I am attempting to start a flink job using the Flink oeprator (version > 1.1) however am running into a problem. While attempting to create the > deployment i receive the following error: > > > Resource: "flink.apache.org/v1beta1, Resource=flinkdeployments", > GroupVersionKind: "flink.apache.org/v1beta1, Kind=FlinkDeployment" > Name: "target-job", Namespace: "test" > for: "flink-job.yml": Internal error occurred: failed calling webhook " > flinkoperator.flink.apache.org": failed to call webhook: Post " > https://flink-operator-webhook-service.test.svc:443/validate?timeout=10s": > service "flink-operator-webhook-service" not found > > Taking a look at the quickstart ( > https://nightlies.apache.org/flink/flink-kubernetes-operator-docs-release-1.1/docs/try-flink-kubernetes-operator/quick-start/), > the recommendation is to either create the certificate manager: > > kubectl create -f > https://github.com/jetstack/cert-manager/releases/download/v1.8.2/cert-manager.yaml > > Or set the webhook to false: > > helm install flink-kubernetes-operator flink-kubernetes-operator -n test > --repo https://archive.apache.org/dist/flink/flink-kubernetes-operator-1.1.0 > --set webhook.create=false > > I have tried both options but still the same error, and advice for getting > this working? > > Regards, > M. > > > > >
