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 on-premises 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:

   Information	Description	Example
   namespace	Name of the Kubernetes or OpenShift namespace	iionpremk8s
   storageclass	Name of the storage class Tip: Use the following command to get the storage class: kubectl -n namespace get storageclass	ceph-rbd-sc-neoceph
   ingressclass	Name of the ingress class. Tip: Use the following command to get the ingress class: kubectl -n namespace get ingressclass	nginx
   registryhost	Host where the Docker registry runs with the BMC Helix container images. Depending on the method you are using to access the container images, note one of the following names: If you are pulling container images directly from the BMC Helix DTR, note docker.io.  If you have synchronized images to a local Harbor registry, note the local Harbor registry host name Important: Do not specify the host path, specify only the host name.	docker.io local-host.mydomain.com.
   imagepullsecret	Image pull secret that you created in step 2.	dockerpull
   imageformat	legacy	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 org names: If you are pulling container images directly from BMC Helix DTR, note bmchelix/lpk11: as images are located in the bmchelix/lpk11 repository on BMC Helix DTR. If you have set up a Harbor registry, note the name of the image registry org as configured for your Harbor registry. For more information about the Harbor registry, see Setting up a Harbor registry in a local network and synchronizing it with BMC Helix DTR or Setting up a Harbor registry in an air-gapped environment and synchronizing it with BMC Helix DTR.	bmchelix/lpk11:  helixiigw/IIGW01:
   swpuiingress	Ingress URL to access the on-premises gateway UI	http://swpui-iionpremk8s-dev1.dsm-01.abc.com
   (Applicable for Kubernetes only) grafanaingress	Ingress URL to access the UI to monitor the on-premises gateway by using dashboards	http://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