Gloo Operator and ServiceMeshController
Troubleshoot the installation, upgrade, or uninstallation of Istio components with the ServiceMeshController resource in the Gloo Operator.
If your installation settings are configured incorrectly, you might experience issues with traffic in your service mesh, or with other Istio components such as gateways.
Before reviewing these specific Istio installation topics, try Debugging Istio.
Check Istio installation status and values
If you used the Gloo Operator to install a service mesh, use the ServiceMeshController resource to monitor the status of the Gloo Operator installation for each Istio component, such as istiod or ztunnel.
Verify that the Gloo Operator pod is running, and has no errors.
kubectl get pods -n gloo-mesh -l app.kubernetes.io/name=gloo-operatorDescribe the ServiceMeshController resource in your cluster.
kubectl describe servicemeshcontroller -n gloo-mesh managed-istioIn the
Statussection of this example output, all statuses areTrueand the phase isSUCCEEDED, which indicates that the installation values are valid and the installation process successfully completed.... Status: Conditions: Last Transition Time: 2024-12-27T20:47:01Z Message: Manifests initialized Observed Generation: 1 Reason: ManifestsInitialized Status: True Type: Initialized Last Transition Time: 2024-12-27T20:47:02Z Message: CRDs installed Observed Generation: 1 Reason: CRDInstalled Status: True Type: CRDInstalled Last Transition Time: 2024-12-27T20:47:02Z Message: Deployment succeeded Observed Generation: 1 Reason: DeploymentSucceeded Status: True Type: ControlPlaneDeployed Last Transition Time: 2024-12-27T20:47:02Z Message: Deployment succeeded Observed Generation: 1 Reason: DeploymentSucceeded Status: True Type: CNIDeployed Last Transition Time: 2024-12-27T20:47:02Z Message: Deployment succeeded Observed Generation: 1 Reason: DeploymentSucceeded Status: True Type: WebhookDeployed Last Transition Time: 2024-12-27T20:47:02Z Message: All conditions are met Observed Generation: 1 Reason: SystemReady Status: True Type: Ready Phase: SUCCEEDED Events: <none>To see the Helm values that were used during the installation or upgrade attempt, check the
Specsection. Be sure that you set all required fields and that the values are valid by referring to the ServiceMeshController reference.- If you set the value of
installNamespaceto a namespace other thangloo-system,gloo-mesh, oristio-system, you must include the--set manager.env.WATCH_NAMESPACES=<namespace>setting. - If the values that you want to set are not available in the ServiceMeshController, review the available settings provided by the
gloo-extensions-configconfigmap.
- If you set the value of
If you use the
gloo-extensions-configconfigmap for advanced settings, be sure that the configmap is explicitly namedgloo-extensions-config, and that it exists in the same namespace as thegloo-operator.