Ingress Configuration
Last updated
Last updated
This guide demonstrates how to configure Ingress. Ingress can be configured in numerous ways. Configurations for the most popular controllers are outlined below.
Kubernetes namespace
The following section(s) presume the Immuta Enterprise Helm chart was deployed into namespace immuta
and that the current namespace is immuta
.
The Immuta web service listens on the following ports:
Port | Protocol | Description | Optional |
---|---|---|---|
Ingress hostname
This is the fully qualified domain name (FQDN) as defined by RFC 3986 used to access the Immuta UI. If a FQDN has yet to be determined set Secure's ingress hostname to immuta.local
.
Edit the immuta-values.yaml
file to include the following Helm values.
Perform a Helm upgrade to apply the changes made to immuta-values.yaml
.
Refer to the Ingress-Nginx Controller documentation for further assistance.
Edit immuta-values.yaml
to include the following Helm values.
Create a file named frontendconfig.yaml
with the following content.
Apply the FrontendConfig
CRD.
Perform a Helm upgrade to apply the changes made to immuta-values.yaml
.
Refer to the Google Cloud documentation for further assistance.
Edit immuta-values.yaml
to include the following Helm values.
Perform a Helm upgrade to apply the changes made to immuta-values.yaml
.
Refer to the AWS Load Balancer Controller documentation for further assistance.
Edit immuta-values.yaml
to include the following Helm values.
Perform a Helm upgrade to apply the changes made to immuta-values.yaml
.
Refer to the Application Gateway Ingress Controller documentation for further assistance.
Edit immuta-values.yaml
to include the following Helm values.
Create a file named middleware.yaml
with the following content.
Apply the Middleware
CRD.
Perform a Helm upgrade to apply the changes made to immuta-values.yaml
.
Refer to the Traefik documentation for further assistance.
Edit immuta-values.yaml
to include the following Helm values. Because the Ingress resource will be managed by the OpenShift route you create and not the Immuta Enterprise Helm chart, ingress
is set to false
below.
Get the service name for Secure.
Create a file named route.yaml
with the following content. Update all placeholder values with your own values.
Apply the Route
CRD.
Perform a Helm upgrade to apply the changes made to immuta-values.yaml
.
Refer to the Red Hat OpenShift documentation for further assistance.