Istio ingress gateway deployment succeeds on one cluster but fails on a second cluster

1

Hello, The deployment of a simple Istio ingress gateway succeeds in a first cluster, but systematically fails on a second cluster.
It would be greatly appreciated to get some clue on how to solve it. Below is the yaml config:

apiVersion: install.istio.io/v1alpha1
kind: IstioOperator
metadata:
  name: istio-ingressgateway-operator
  namespace: istio-system
spec:
  profile: minimal
  components:
    ingressGateways:
      - name: istio-ingressgateway
        enabled: true
        k8s:
          service:
            type: NodePort

I am using minikube on Linux Ubuntu VM with 4 CPUs, 10GB of RAM and 100GB of storage.
I have two instances of minikube: cluster-1 and cluster-2.
My cluster-1 has istiod and istio ingress gateway, and is running fine.
However, as soon as I try to deploy the same istio ingress gateway yaml config on minikube cluster-2, Istio fails with following errors:

✘ HorizontalPodAutoscaler: istio-ingressgateway.istio-system: horizontalpodautoscalers.autoscaling “istio-ingressgateway” not found
✘ Deployment: istio-ingressgateway.istio-system: deployments.apps “istio-ingressgateway” not found
✘ PodDisruptionBudget: istio-ingressgateway.istio-system: poddisruptionbudgets.policy “istio-ingressgateway” not found
✘ Role: istio-ingressgateway-sds.istio-system: --roles.rbac.authorization.k8s.io “istio-ingressgateway-sds” not found
✘ RoleBinding: istio-ingressgateway-sds.istio-system: --rolebindings.rbac.authorization.k8s.io “istio-ingressgateway-sds” not found
✘ Service: istio-ingressgateway.istio-system: services “istio-ingressgateway” not found
✘ ServiceAccount: istio-ingressgateway-service-account.istio-system: serviceaccounts “istio-ingressgateway-service-account” not found

I compared the resource capacity, request and limits of the two clusters, and they are similar (“kubectl describe node” gives similar result). So, I have hard time to understand how it works on one cluster but not on a second one?

Some other logs:

$ kubectl describe istiooperator istio-ingressgateway-operator -n istio-system

Name:         istio-ingressgateway-operator
Namespace:    istio-system
Labels:       <none>
Annotations:  <none>
API Version:  install.istio.io/v1alpha1
Kind:         IstioOperator
Metadata:
  Creation Timestamp:  2023-11-20T22:56:30Z
  Generation:          1
  Resource Version:    29298
  UID:                 cb85b1d5-a112-424a-803c-0e5c85f921d5
Spec:
  Components:
    Ingress Gateways:
      Enabled:  true
      k8s:
        Service:
          Type:  NodePort
      Name:      istio-ingressgateway
  Profile:       minimal
Events:          <none>

$ kubectl get --istiooperators.install.istio.io -n istio-system

NAME                            REVISION   STATUS   AGE
installed-state                                     34m
istio-ingressgateway-operator                       4m59s

$ kubectl get pods -n istio-system --cluster=cluster-1

NAME                                   READY   STATUS    RESTARTS        AGE
istio-ingressgateway-cf99dfc5c-q8qss   1/1     Running   20 (161m ago)   14d
istiod-78c4f7f756-pb5rg                1/1     Running   22 (161m ago)   19d

$ kubectl get pods -n istio-system --cluster=cluster-2

NAME                      READY   STATUS    RESTARTS   AGE
istiod-78c4f7f756-89mt5   1/1     Running   0          38m

Thanks