We have a Azure Kubernetes Service running for our apps. We are trying to use Istio as a frontal ingress gateway. We are experiencing issues while trying to deploy the ingress gateway pod as DaemonSet.
Our version of Kubernetes are 1.19.7. We also tried it with 1.19.11.
We tried the following configuration after deploying Istio Operator either by using IstioCtl or with Helm chart.
In both cases, we get the following error …
info installer using server side apply to update obj: DaemonSet/istio-system/istio-ingressgateway error installer failed to update resource with server-side apply for obj DaemonSet/istio-system/istio-ingressgateway: failed to create typed patch object: .spec.strategy: field not declared in schema - Pruning removed resources ✘ Ingress gateways encountered an error: failed to update resource with server-side apply for obj DaemonSet/istio-system/istio-ingressgateway: failed to create typed patch object: .spec.strategy: field not declared in schema
… when applying the following configuration:
apiVersion: install.istio.io/v1alpha1 kind: IstioOperator metadata: namespace: istio-system name: istio-config spec: profile: demo meshConfig: connectTimeout: "10s" accessLogFile: /dev/stdout defaultConfig: tracing: sampling: "100" components: ingressGateways: - name: istio-ingressgateway enabled: true k8s: service: externalTrafficPolicy: Local loadBalancerIP: <OUR_PUBLIC_IP_OBJECT_IN_AZURE_FOR_ISTIO> serviceAnnotations: service.beta.kubernetes.io/azure-dns-label-name: "demo-istio" overlays: - apiVersion: apps/v1 kind: Deployment name: istio-ingressgateway patches: - path: kind value: DaemonSet
If we disable the Overlays part, deployment succeeds but we get the ingress gateway pod only on one node.
According to this documentation, we have to deploy the ingressgateway as DaemonSet for it to be deployed on every node in the cluster. (" However, you must run an ingress gateway pod on every node.", it says)
We tried with Istio Operator v1.10.0 or 1.10.1 without any luck on either version.
Do you have any insight on why this spec.strategy error is happening?
Best Regards from France,