Ingress Configuration
Last updated
Was this helpful?
Last updated
Was this helpful?
This guide demonstrates how to configure . Ingress can be configured in numerous ways. Configurations for the most popular controllers are outlined below.
The Immuta web service listens on the following ports:
443
TCP
HTTPS
False
80
TCP
HTTP (redirects to HTTPS)
True
Edit the immuta-values.yaml
file to include the following Helm values.
Perform a to apply the changes made to immuta-values.yaml
.
Edit immuta-values.yaml
to include the following Helm values.
Create a file named frontendconfig.yaml
with the following content.
Apply the FrontendConfig
CRD.
Edit immuta-values.yaml
to include the following Helm values.
Edit immuta-values.yaml
to include the following Helm values.
Edit immuta-values.yaml
to include the following Helm values.
Create a file named middleware.yaml
with the following content.
Apply the Middleware
CRD.
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.
Apply the Route
CRD.
Refer to the for further assistance.
Perform a to apply the changes made to immuta-values.yaml
.
Refer to the for further assistance.
Perform a to apply the changes made to immuta-values.yaml
.
Refer to the for further assistance.
Perform a to apply the changes made to immuta-values.yaml
.
Refer to the for further assistance.
Perform a to apply the changes made to immuta-values.yaml
.
Refer to the for further assistance.
Create a file named route.yaml
with the following content. Update all with your own values.
Perform a to apply the changes made to immuta-values.yaml
.
Refer to the for further assistance.