Kubernetes: Missing Sidecar Containers in Container Selection

Problem:
When trying to select a container in the "Container Selection" dropdown during a Kubernetes experiment, you may notice that some containers are missing, particularly SidecarContainers.

Cause:
Currently, Gremlin doesn't support targeting SidecarContainers directly when running Kubernetes-specific experiments. This means that sidecar containers will not appear in the Container Selection dropdown for Kubernetes experiments.

Impact of Network Experiments:
Although you can't directly target SidecarContainers, any network experiments against a Kubernetes pod that includes SidecarContainers will still affect those sidecars, as long as they share the same network as the application container. By default, this is usually the case.

Workaround:
To impact SidecarContainers directly, you can use Container Experiments instead of Kubernetes experiments. The Container Experiments allows you to select the sidecar container and apply the desired experiment directly.

Note:
For network experiments, this workaround isn't needed because network disruptions will automatically impact all containers (including sidecars) within the pod that share the same network.

Summary:

• SidecarContainers are not selectable in Kubernetes experiment Container Selection.

• Network experiments on a pod will still affect all containers, including sidecars, if they share the network.

• Use Container Experiments to target sidecar containers directly until Kubernetes experimetns support them.