Hello, I am using minikube in a Linux Ubuntu VM (created with VirtualBox on Windows 11).
The VM has 4 CPUs, 10GB of RAM and 100GB of disk storage. I have the default "minikube" cluster, and one additional cluster named "cluster-1".
My cluster are both single Node. I am using NodePort with Istio Ingress Gateway to externally access the clusters. This Setup is for development only.
In "cluster-1", I have installed "istiod" with minimal profile, "istio-ingressgateway" (see yaml config below). This cluster is in running status without any issue.
In the default "minikube" cluster, I have only the default pods. My problem is that I am not able to successfully install the istio-ingressgateway in the default cluster.
I can install istiod with minimal profile in the default "minilube" cluster, but as soon as I apply the yaml configuration to deploy the "istio-ingressgateway" (see yaml config below), it systematically fails with the following error:
✘ 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
It seems mysterious to me that it systematically works on "cluster-1" but not on "minikube" default cluster. Below is the yaml config of the Istio operator:
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
Does anyone have a solution to this issue?
Thanks!