The Microgateway Operator injects the Microgateway Engine containers to the upstream application Pods based on annotations. They allow configuring whether the containers should be injected and some general behavior. The table below lists and explains the annotations the Operator is aware of.
Annotation | Default | Possible values | Description |
---|---|---|---|
| false | true, false | If true, an Microgateway Engine sidecar is injected during Pod creation. Adding the annotation to an existing, running Pod has no effect. Use |
| "" | "<int>, ..." | Comma-separated list of inbound ports to be excluded from redirection to the Microgateway Engine by the Microgateway CNI plugin. The Istio default ports for the Istio sidecar proxy are automatically excluded when setting the annotation
|
|
|
| Annotation to set which service mesh should be used. This annotation is relevant info for the Microgateway CNI plugin to configure the redirection of the traffic to the Microgateway Engine correctly. |
|
|
| Annotation to set the Microgateway Engine log level. |
| absent, the defaults specified in the engineContainerTemplate are used | 1, 100m, 0.5, ... | Sets the CPU requests for the Microgateway engine by replacing the template value for |
| absent, the defaults specified in the engineContainerTemplate are used | 1, 100m, 0.5, ... Any CPU resource unit can be used. | Sets the CPU limit for the Microgateway engine by replacing the template value for |
| absent, the defaults specified in the engineContainerTemplate are used | 64Mi, 1G, ... Any Kubernetes memory resource unit can be used. | Sets the memory requests for the Microgateway engine by replacing the template value for |
| absent, the defaults specified in the engineContainerTemplate are used | 128Mi, 1G, ... Any Kubernetes memory resource unit can be used. | Sets the memory limit for the Microgateway Engine by replacing the template value for |