Networking Operators

Procedure

1. Run ocm create cluster -h and confirm that your ocm version lists the --exclude-namespace-selector flag.

2. Build your ocm create cluster command with the required parameters for your cloud provider and subscription model.

   The following example shows only the ingress-related fragment. Replace the rest of the flags with the values required for your environment.

   $ ocm create cluster <cluster_name> \
     --provider=<aws_or_gcp> \
     <other_required_flags> \
     --default-ingress-excluded-namespace-selectors '<key>=<value>,<key2>=<value2>'

   where:

   <cluster_name>

   Specifies the cluster name.

   --provider=<aws_or_gcp>

   Specifies the cloud provider.

   <other_required_flags>

   Required parameters such as region, version, Customer Cloud Subscription (CCS) settings, or billing flags, as described in the cluster creation documentation for your platform.

   --default-ingress-excluded-namespace-selectors

   Specifies label selectors that exclude matching namespaces from the default application ingress. The service validates these exclusions. Replace <key>=<value> with your labels. Do not include spaces around the = sign.

Procedure

1. Run the following command to pass the namespace exclusions to your cluster:

   $ ocm edit ingress <ingress_name> -c <cluster_id> \
     --excluded-namespace-selectors "key1=val1,key2=val2,key1=val3,foo=bar" \
     <cluster_name>

   where:

   <ingress_name>

   Specifies your ingress name.

   <cluster_id>

   Specifies your cluster ID.

   --excluded-namespace-selectors "key1=val1,key2=val2,key1=val3,foo=bar"

   Specifies label selectors that exclude matching namespaces from the default application ingress. The service validates these exclusions. Replace <key>=<value> with your labels. Do not include spaces around the = sign.

   <cluster_name>

   Specifies the cluster name.

Procedure

1. On the Networking screen, select Custom Settings under Application ingress settings.

   Note

   All of the custom settings are optional.

2. In Route selector, enter a comma-separated list of key=value pairs to limit which routes this ingress exposes. Leave the field empty if all routes should remain eligible based on your other choices.
3. In Excluded namespaces, enter a comma-separated list of namespace names whose routes must not use this ingress.

4. In Exclude namespace selectors, specify one or more label selectors. For each selector, provide a label key and a comma-separated list of label values. The default Ingress Controller does not apply to namespaces whose labels satisfy any of the configured selectors.

   Important

   Do not include spaces around commas, for example, use finance,HR,legal, and not finance, HR, legal.

5. Set Namespace ownership policy for route admission when namespaces share hostnames, for example, select Strict for restrictive admission.

6. Set Wildcard policy to allow or disallow wildcard patterns in route hostnames, for example, select Disallowed to block wildcard host routes.

   For more information about custom application ingress settings, click the information icon provided for each setting.

Procedure

1. From OpenShift Cluster Manager, navigate to the Cluster List page and select the cluster that you want to set namespace exclusions for.
2. On the selected cluster, select the Networking tab.

3. Select Edit application ingress.

   Note

   All of the custom settings are optional.

4. In Route selector, enter a comma-separated list of key=value pairs to limit which routes this ingress exposes. Leave the field empty if all routes should remain eligible based on your other choices.
5. In Excluded namespaces, enter a comma-separated list of namespace names whose routes must not use this ingress.

6. In Exclude namespace selectors, specify one or more label selectors. For each selector, provide a label key and a comma-separated list of label values. The default Ingress Controller does not apply to namespaces whose labels satisfy any of the configured selectors.

   Important

   Do not include spaces around commas, for example, use finance,HR,legal, and not finance, HR, legal.

7. Set Namespace ownership policy for route admission when namespaces share hostnames, for example, select Strict for restrictive admission.

8. Set Wildcard policy to allow or disallow wildcard patterns in route hostnames, for example, select Disallowed to block wildcard host routes.

   For more information about custom application ingress settings, click the information icon provided for each setting.

9. Select Save to configure the ingress with your changes.