Skip to content
You are viewing the documentation for Solo Enterprise for Istio, formerly known as Gloo Mesh (OSS APIs).

For the complete documentation index, see llms.txt. Markdown versions of all docs pages are available by appending .md to any docs URL.

meshctl experimental interop-check

Page as Markdown
Reference for the ‘meshctl experimental interop-check’ command.
meshctl experimental interop-check

Checks your Istio and Kubernetes environment for Istio ambient-sidecar interoperability.
Synopsis

Before you deploy a hybrid service mesh that uses both Istio sidecar and sidecarless modes, you can run this command to verify that:
  • Settings on your control plane allow HBONE tunneling and enable the ambient controllers
  • Required components, including the CNI plugin and ztunnel, are installed
  • Solo.io images are used
  • HBONE tunneling is enabled for sidecars
  • Running versions of Istio support a hybrid mesh
  • Kubernetes Network Policies do not specify a port, which ambient mode tunneling will disrupt
(Istio’s rich L4 policy can still use the original destination port, but Kubernetes will see the tunneled port)
meshctl experimental interop-check [flags]
Options

  -h, --help   help for interop-check
Options inherited from parent commands

      --kubeconfig string    Path to the kubeconfig file for the cluster.
      --kubecontext string   Kubernetes context for the cluster to run the command in.
  -n, --namespace string     Namespace to run the command in. (default "gloo-mesh")
      --plain                Disable styling for terminal output.
  -v, --verbose              Enable verbose logging.
SEE ALSO

meshctl experimentalmeshctl install