Installing Gremlin on OpenShift 4
Pre-requisites
Download authentication keys
Gremlin requires authentication during installation. You will need to download your Gremlin certificate key-pair in order to connect to your Gremlin team. The downloaded zip contains two files: <team-name>-client.pub_cert.pem is the certificate and <team-name>-client.priv_key.pem is the private key. With the key pair extracted to your local system, export the following variables into a local shell, supplying the appropriate values.
SELinux considerations
Gremlin's container targeting features require the Gremlin Agent to run with hostPID=true. OpenShift's container runtime CRI-O automatically runs hostPID containers with the spc_t SELinux process label. No custom SELinux profile installation is required.
Previous versions of Gremlin would allow hostPID=false and as a result required a custom SELinux module to grant the Gremlin agent access to system calls and file access. If you have installed a custom SELinux policy using Gremlin's 96-worker-gremlin-semodule MachineConfig, you should remove this MachineConfig and ensure the Gremlin Daemonset is installed with hostPID=true .
Helm installation
To install with Helm, log into the OpenShift cluster and run the following:
This command uses the classic Gremlin Helm repository. To pull the chart from Gremlin's OCI registry instead, see Note on using the Gremlin Helm repository.
Run attacks
You can now run experiments on your cluster, including Kubernetes experiments. For step-by-step instructions, see How to run an experiment.
Troubleshooting
For common issues and solutions, see Troubleshooting Gremlin on OpenShift.

