hongyegong

Same problem here. My guess is certificate expired.

Actually, just found the problem. After iOS 10.3, you have to actually go to Settings->General->About->Certificate Trust Settings and manually trust the certificate ;)

What commands exactly did you run to install? Cannot reproduce from my side.

Do you have to make any local change to the operator? if not, could you try directly install with `helm install --name [RELEASE_NAME] flink-operator-repo/flink-operator` instead of fetching it and install...

@dr3s can you paste the log here, based on [comments above](https://github.com/GoogleCloudPlatform/flink-on-k8s-operator/issues/236#issuecomment-622987251) you should see cert-job completed successfully with operator version 0.1.1. @smainv That got removed cuz it was in line...

FYI, there is an ongoing [PR](https://github.com/GoogleCloudPlatform/flink-on-k8s-operator/pull/348#issue-504263325) aiming to move the name of `flinkOperatorNamespace` a level down below, so here might become `flinkOperatorNamespace.name` after the other PR is merged.

What does `cog/authoring/test.yaml` do exactly? Can you attach the exact install commands you've run in CLI?

> I am also seeing this issue. It seems possible that the webhook certs are being overwritten after a helm upgrade? I'm using helm3. see below, `clientConfig.caBundle` had a val...

The fact that we right now heavily rely on Kustomize even for helm chart is mostly because we use it for the [regular operator install process](https://github.com/GoogleCloudPlatform/flink-on-k8s-operator/blob/master/Makefile), there are 3 major...