Gábor Tóth

Can we merge dchirikov's solution? It would be very useful.

Yes, once it will be modified after creation it stucks. As a workaround I will remove every terraform variable from it, I will use tags and filters only for my...

If I get rid of the variables in the resource and I even use static values, the filters and tags tagged for modification and the apply phase stuck in 'still...

Thank you for your answer @alpeb ! ``` user@ip-10-x-x-65 ~ $ k logs linkerd-proxy-injector-55f86f4fc9-tsmgc -n linkerd Defaulted container "linkerd-proxy" out of: linkerd-proxy, proxy-injector, linkerd-init (init) [ 0.095648s] INFO ThreadId(01) linkerd2_proxy:...

Yes of course! ``` apiVersion: admissionregistration.k8s.io/v1 kind: MutatingWebhookConfiguration metadata: annotations: meta.helm.sh/release-name: linkerd-control-plane meta.helm.sh/release-namespace: linkerd labels: app.kubernetes.io/managed-by: Helm linkerd.io/control-plane-component: proxy-injector linkerd.io/control-plane-ns: linkerd name: linkerd-proxy-injector-webhook-config webhooks: - admissionReviewVersions: - v1 - v1beta1...

Any idea how should I continue? Thank you very much in advance!

Any clue? Thank you very much in advance!

Thank you very much for your help! In the meantime I have found another way to avoid IPv4 exhaustion. In the future if somebody needs it it can be found...

Dear @nguyenthai0107 ! Sorry for not responding for a while! I have installed this version: https://artifacthub.io/packages/olm/community-operators/knative-operator/1.12.0 Thank you for your response!

Hi @skonto! Yes it is still an issue. Hi @nguyenthai0107! We use Terraform and we install every operator and features with helm charts, It would be great to follow and...