HH:MM:SS: Template failed
| ytt: Error: Overlaying (in following order: overlay/authenticated-registry-overlay.yaml, overlay/istio-ambient-overlay.yaml, overlay/istio-base-overlay.yaml, overlay/istio-gateways-overlay.yaml, overlay/istio-support-overlay.yaml, overlay/istiod-overlay.yaml):
| Document on line overlay/istio-gateways-overlay.yaml:90:
| Expected number of matched nodes to be 1, but was 0
|
| Templating dir: Error (see .status.usefulErrorMessage for details)
HH:MM:SS: Error tailing or reconciling app: Reconciling app: Template failed
istio-data-values.yaml file has the egress and ingress gateway set to enabled: false: gateways: egress: enabled: false namespace: "istio-egress" priorityClassName: "" replicas: 1 resources: limits: cpu: 2000m memory: 1024Mi requests: cpu: 100m memory: 128Mi autoscaling: enabled: true minReplicas: 1 maxReplicas: 5 ingress: enabled: false namespace: "istio-ingress"VMware vSphere Kubernetes Service
This issue occurs because the gateways (Ingress and/or Egress) are explicitly disabled in the user-provided values.yaml configuration file.
If enabled: false is set for the gateways in values.yaml, the base Istio configuration is generated without these gateway objects. Consequently, the overlay file cannot find the target nodes it expects to patch, resulting in the "Expected number of matched nodes to be 1, but was 0" error.
To resolve this issue, ensure that the gateways are enabled in the configuration so that the overlay has a valid target to apply patches to.
Locate the configuration file - istio-data-values.yaml file being used for the Istio package installation.
Edit the file in a text editor and locate the gateways section.
Change the enabled flag from false to true for the ingress and egress gateways.
Incorrect Configuration (Causing Error):
gateways:
ingress:
enabled: false
egress:
enabled: false
Correct Configuration:
gateways:
ingress:
enabled: true
egress:
enabled: true