Creating a namespace for the on-premises gateway deployment

As a Kubernetes or OpenShift administrator, create a namespace before you deploy the BMC Helix Intelligent Integrations gateway in an on-premises Kubernetes or OpenShift cluster.

To create a namespace

1. Create a namespace.
   kubectl create ns <namespaceName>
   Example:
   kubectl create ns iionpremk8s
2. Depending on the method you are using to access the container images, use one of the following commands to create the image pull secret for the namespace:
   • If you are planning to pull container images directly from the BMC Helix Docker Trusted Repository (DTR), use the following command:
     kubectl -n <namespaceName> create secret docker-registry dockerpull --docker-server=docker.io --docker-username=<userName> --docker-password=<passwword>
     In the above command, replace <username> and <password> with the user name and password generated when creating the Personal Access Token. For more information, see Downloading the container access key.
   • If you have set up a local Harbor registry, use the following command:
     kubectl -n <namespaceName> create secret docker-registry dockerpull --docker-server=<localHarborHost> --docker-username=<userName> --docker-password=<passwword>
     In the above command, replace <localHarborHost>, <username>, and <password> with the details of your local Harbor registry.
3. Note the following information about the Kubernetes or OpenShift deployment:
   • namespace: Name of the Kubernetes namespace. 
   • storageclass: Name of the storage class.
   • ingressclass: Name of the ingress class.
   • registryhost: Name of the registry host. Depending on the method you are using to access the container images, note one of the following names:
     • If you are planning to pull container images directly from the BMC Helix DTR, note docker.io. 
     • If you have set up a local Harbor registry, note the local Harbor registry host name.
   • imagepullsecret: Image pull secret that you created in step 2.
   • imageformat: legacy.
   • org: Name of the image registry org. Depending on the method you are using to access the container images, note one of the following names:
     • If you are planning to pull container images directly from the BMC Helix DTR, note bmchelix/lpk11:. 
     • If you have set up a Harbor registry, note the name for the image registry org according to your Harbor registry configuration, for example, HelixIIGW/IIGW01:.
   • swpuiingress, the ingress URL to access the on-premises gateway UI. For example, swpui-iionpremk8s-dev1.dsm-01.abc.com.
   • (Applicable for Kubernetes only) grafanaingress, the ingress URL to access the UI to monitor the on-premises gateway by using dashboards. For example, swpgrafana-iionpremk8s-dev2.dsm-01.abc.com.

Where to go from here

Deploying the on-premises gateway in an on-premises Kubernetes or OpenShift cluster