You can configure odigos installation using the following options:

​
Ignore Namespaces

Don’t show specific uninteresting namespaces in the Odigos UI.

Default values: kube-system, local-path-storage, istio-system, linkerd, kube-node-lease

Add additional namespaces to ignore with cli:

odigos install --ignore-namespace <namespace1> --ignore-namespace <namespace2>

List all namespaces to be ignored with helm chart:

helm install odigos odigos/odigos --set ignoreNamespace=<namespace1>,<namespace2>

Any Source objects for the namespace and workloads in the namespace will still be honored.

​
Ignore Containers

This option is useful for excluding specific sidecar containers from being instrumentated by odigos.

Default values: istio-proxy

Add additional containers to ignore with cli:

odigos install --ignore-container <container1> --ignore-container <container2>

List all containers to be ignored with helm chart:

helm install odigos odigos/odigos --set ignoreContainer=<container1>,<container2>

​
OpenShift Installation

Installing on OpenShift requires additional settings that can be configured based on your installation mode:

Run the Odigos CLI with the --openshift flag:

odigos install --openshift

OpenShift installation does the following:

  • Uses Red Hat certified component container images
  • Configures required SELinux permissions for pods to access auto-instrumentation agents on RHEL nodes
  • Configures RBAC permissions for Odigos components required by default in OpenShift clusters

By default, the --openshift flag will pull Odigos component images from registry.connect.redhat.com/odigos. These images are based on Red Hat’s Universal Base Image 9 and denoted with the -ubi9 suffix. These images are also hosted on the Odigos DockerHub registry, which you can deploy by setting --openshift with --image-prefix docker.io/keyval.

InstallationCustom Docker Registry