Based on configmaps it will inject Init or regular containers to the pod
This needs cert-manager
to generate and renew the tls certificates
Apply customizations to the yaml files inside the deploy folder as needed
- Find and replace all instances of
tools
with something else if you want to install in a different namespace - Modify the
certificate.yaml
file as needed- Install certmanager and apply the
selfsigned.yaml
(ifselfsigned-issuer
doesn't exist) - Alternatively setup a ClusterIssuer/Issuer using cert-manager and edit the
certificate.yaml
with customizations - Replace
tools
with alternative namespace if installing elsewhere
- Install certmanager and apply the
- Modify the
deployment.yaml
file as needed with the following options- Change environment variables as needed (see Available Variables below)
- Change the replica and resources values as needed depending on how many targeted pods your evironment might have (the defaults are probably fine for anything under 10k)
- Modify the
mutatingwebhook.yaml
as needed- Remove the
namespaceSelector
lines if you want all pods targeted (careful as this will include itself/kube-system) - Change the
namespaceSelector
to select the namespaces you want to target (see namespaceSelector docs)
- Remove the
Apply in the following order after making any needed modifications
kubectl apply -f selfsigned.yaml # this should be already in the cluster as a global object and not linked to this solution
kubectl apply -f certificate.yaml
kubectl apply -f service-account.yaml
kubectl apply -f deployment.yaml
kubectl apply -f service.yaml
kubectl apply -f configmap.yaml
kubectl apply -f mutatingwebhook.yaml
s
These variables can be set when running the docker image to customize the functionality
Variable | Default | Description |
---|---|---|
LOG_LEVEL | DEBUG,INFO,WARN,ERROR | If set to DEBUG will enable additional output including a dump of input and output objects for debugging purposes |