Sidecar-based installation types
In a Kubernetes cluster, Operators can be deployed in different modes concerning the namespace setup. The default installation mode for Airlock Microgateway is AllNamespaces with a single Operator managing all web application Pods with SidecarGateways in a cluster. This is the only installation mode that can be used with the Community edition license.
For a production environment, multi-namespace installations are commonly used where Airlock Microgateway Operator can watch and operate web application Pods installed in multi-namespace setups. This allows, i.e., to separate production from staging and development.
To achieve an optimum level of segregation and low memory consumption of the Operator, we recommend using a static rather than a dynamic MultiNamespace installation.
The installation modes can be configured via the Microgateway Operator Helm chart by setting the operator.watchNamespaces
and operator.watchNamespaceSelector
values.
Cluster-scoped installation modes
Role-based access control (RBAC) is created cluster-scoped (using ClusterRoles and ClusterRoleBindings) in the respective cluster for the following installation modes:
AllNamespaces (default) | Dynamic MultiNamespace |
---|---|
In a simple AllNamespace installation mode, the Airlock Microgateway Operator and web application Pods with SidecarGateways can be deployed in multiple separate namespaces. | In a dynamic MultiNamespace installation mode, the Airlock Microgateway Operator and web application Pods with SidecarGateways are deployed in multiple separate namespaces. |
The Operator watches all namespaces.
| The Operator watches multiple namespaces where the
|
Namespace-scoped installation modes
Role-based access control (RBAC) is created namespace-scoped (using Roles and RoleBindings) in the respective namespaces for the following installation modes:
Static MultiNamespace | SingleNamespace | OwnNamespace |
---|---|---|
In a static MultiNamespace installation mode, the Airlock Microgateway Operator and web application Pods with SidecarGateways are deployed in multiple separate namespaces. | In a SingleNamespace installation mode, the Airlock Microgateway Operator and one or more web application Pods with SidecarGateways are deployed in two separate namespaces. | In an OwnNamespace installation mode, the Airlock Microgateway Operator and one or more web application Pods with SidecarGateways share a single namespace. |
The Operator watches multiple namespaces according to the
| The Operator watches a single namespace according to the
| The Operator watches all web application Pods with SidecarGateway in his namespace.
|
Finding the most suitable installation mode
Use cases | Installation mode |
---|---|
| Static/Dynamic MultiNamespace |
| Static MultiNamespace |
| OwnNamespace |
Further information and links
Internal links:
External links: