Helm

The Gremlin agent daemonset and the Chao agent deployment now support priorityClassName by setting either gremlin.priorityClassName, chao.priorityClassName, or both. See gremlin/helm#89

AWS SSM Parameter Store or AWS Secrets Manager ARN values can now be supplied for secret inputs such as gremlin.secret.teamSecret. See How to use config values stored in AWS

Introduced gremlin.serviceAccount.annotations and chao.serviceAccount.annotations for supplying custom annotations to the service accounts managed by this chart. This is useful for passing annotations such as eks.amazonaws.com/role-arn.

Introduced gremlin.extraEnv and chao.extraEnv for supplying custom environment variables to the Gremlin and Chao agents.

Removed deprecated configuration values:

• gremlin.client.secretName: please use gremlin.secret.name
• gremlin.client.certCreateSecret: please use gremlin.secret.managed
• gremlin.installK8sClient: please use: chao.create

Helm chart now explicitly declares DAC_READ_SEARCH, which is required to discover dependencies and run Certificate Expiry attacks. Most container runtimes already provide a superset of this capability (DAC_OVERRIDE) by default.

Make gremlin.container.driver=any the new default, when set gremlin.container.driver=any will attempt to mount all possible container driver paths, delegating to gremlin to pick the runtime. This option has served as the easiest way to get Gremlin up and running on containerized systems because you don't need to know or muck with container driver details.

You can now add labels to the deployed Gremlin Pods using the chao.podLabels and gremlin.podLabels parameters. See the Chart documentation for details.

You can now specify SELinux options to apply to the Gremlin DaemonSet container securityContext using the gremlin.podSecurity.seLinuxOptions parameter. See the Chart documentation for details.