Skip to content

Latest commit

 

History

History
39 lines (28 loc) · 1.17 KB

troubleshooting.md

File metadata and controls

39 lines (28 loc) · 1.17 KB
Raw

Troubleshooting

Be sure to check out solutions to common issues.

KRM function troubleshooting

If the KRM function fails to look up the image digest, you can increase the logging verbosity by using the DEBUG environment variable:

export DEBUG=true
kpt fn [...]

Webhook troubleshooting

The webhook fails open because the failurePolicy on the MutatingWebhookConfiguration is set to Ignore. This means that if there is an error calling the webhook, the API server allows the request to continue.

If the webhook fails to look up the image digest, you can enable development mode logging and increase the logging verbosity.

  1. Set the DEBUG environment variable to true in the webhook Deployment manifest and redeploy the webhook:

    kpt fn eval manifests --image gcr.io/kpt-fn/apply-setters:v0.2 -- debug=true
kpt live apply manifests

  2. Tail the webhook logs:

    kubectl logs --follow deployment/digester-controller-manager \
    --namespace digester-system --all-containers=true