Skip to main content

Known Issue: Configuring Gatekeeper values

Steven Sylvester
  • Updated
There is a known issue in DKP 2.4 and older where adjusting Gatekeeper via the Kommander UI does not result in changes reaching the pods due to differences between the Appdeployment and the Helm release.

Solution

As a workaround, you can create a configmap directly in your cluster that contains the Helm overrides you need. For instance, if you need to increase the memory limits of the gatekeeper-audit pod, create a file on your local machine called gatekeeper-overrides.yaml with the following contents:

 
apiVersion: v1
data:
  values.yaml: |-
    audit:
      resources:
        limits:
          memory: 1Gi
kind: ConfigMap
metadata:
  name: gatekeeper-overrides
  namespace: kommander
 
You can then apply the file to create the configmap in your cluster:
kubectl apply -f gatekeeper-overrides.yaml
Once this configmap is created, the gatekeeper-audit pod should restart within a few minutes with the new memory values.