You can add annotations to Kubernetes Pod objects to customize Piggy's behavior.
piggysec.com/aws-secret-namespecifies an AWS secret name, e.g., "/myapp/name".piggysec.com/aws-regionspecifies an AWS Secrets Manager region, e.g., "ap-southeast-1".piggysec.com/aws-secret-versionspecifies an AWS secret version. The default value isAWS_CURRENT.
piggysec.com/piggy-env-imageoverrides the piggy-env image location. If no value is specified, the piggy-env image location will be taken from the Piggy Webhooks settings in the Helm chart.piggysec.com/piggy-env-image-pull-policyoverrides the piggy-env image pull policy. If no value is specified, the piggy-env image pull policy will be taken from the Piggy Webhooks settings in the Helm chart.piggysec.com/piggy-env-resource-cpu-requestoverrides the piggy-env init-container resource CPU requests. Defaults to50m.piggysec.com/piggy-env-resource-memory-requestoverrides the piggy-env init-container resource memory requests. Defaults to64Mi.piggysec.com/piggy-env-resource-cpu-limitoverrides the piggy-env init-container resource CPU limit. Defaults to200m.piggysec.com/piggy-env-resource-memory-limitoverrides the piggy-env init-container resource memory limit. Defaults to64Mi.piggysec.com/piggy-psp-allow-privilege-escalationallow a piggy-env init-container to run as root. Default tofalsepiggysec.com/piggy-addressan endpoint of piggy-webhooks. This is required when it is running in proxy mode.piggysec.com/piggy-skip-verify-tlsDo not verify TLS certificate between application and piggy-webhooks.piggysec.com/piggy-ignore-no-envdoes not terminate the container if no variables are found in Secrets Manager. Defaults tofalse. Setting this value tofalse(the default) is recommended for most applications; the container will not start if required environment variables are missing.piggysec.com/piggy-enforce-integrityenforces checking command integrity before injecting secrets. Defaults totrue. Setting this value totrueis recommended for most applications. Setting it tofalsewill allow piggy-env to run with different arguments.piggysec.com/debugallows to run piggy-env in debug mode. Default tofalse.piggysec.com/standaloneallows to run piggy-env in standalone mode. Default tofalse. If this value istrue, the piggysec.com/piggy-address will not be used.piggysec.com/piggy-enforce-service-accountForce to checkPIGGY_ALLOWED_SAenv value in AWS secret managerpiggysec.com/piggy-default-secret-name-prefixSet default prefix string for secret namepiggysec.com/piggy-default-secret-name-suffixSet default suffix string for secret namepiggysec.com/piggy-dns-resolverSet Go DNS resolver such astcp,udp. See https://pkg.go.dev/netpiggysec.com/piggy-initial-delaysets a delay in n[ns|us|ms|s|m|h] before starting to retrieve secrets. If you are using Istio/Envoy, you may need to set this value to2s. Envoy will block all outgoing requests from piggy-env until it is fully started. This delay allows Envoy to become operational before Piggy runs.piggysec.com/piggy-number-of-retrysets the number of retries for retrieving secrets before giving up. Each retry will wait for 500 milliseconds. You can use this to resolve issues with delayed pod initialization, such as with Istio/Envoy.
piggysec.com/image-pull-secretspecifies the name of the container image pull secret. Piggy will try to read the container image configuration by using secrets in the following order:pod.spec.imagePullSecretspiggysec.com/image-pull-secretannotation- ServiceAccount permissions from the cloud provider
piggysec.com/image-pull-secret-namespacespecifies the namespace of the container image pull secret.piggysec.com/image-skip-verify-registryskips registry verification when trying to read the image. Defaults totrue.