Deploying App Outside Data Plane Namespace

You can deploy apps in different namespaces but these namespaces must be existing and accessible by the same service account used during the data plane registration. Use the following steps to create a namespace and associate it with the service account.

Procedure

1. Create app namespace with data plane id associated with it. You can get data plane id from the data plane details page.

   kubectl apply -f - <<EOF
   apiVersion: v1
   kind: Namespace
   metadata:
     name: <appnamespace>
     labels:
       platform.tibco.com/dataplane-id: <dataplaneid>
   EOF

   Example:

   kubectl apply -f - <<EOF
   apiVersion: v1
   kind: Namespace
   metadata:
     name: bw-app-ns
     labels:
       platform.tibco.com/dataplane-id: cl1n2j8geqg12oe78750
   EOF

2. Run the following helm command:

   helm upgrade --install dp-configure-namespace dp-configure-namespace    -n <app_namespace>    --repo https://tibcosoftware.github.io/tp-helm-charts    --set global.tibco.dataPlaneId=<dataplane_id>    --set global.tibco.primaryNamespaceName=<dataplane_namespace>    --set global.tibco.serviceAccount=<service_account_from_dataplane_namespace> 

   Example:

   helm upgrade --install dp-configure-namespace dp-configure-namespace    -n appworkspace    --repo https://tibcosoftware.github.io/tp-helm-charts    --set global.tibco.dataPlaneId=ck3tu70dai01upfq67e0    --set global.tibco.primaryNamespaceName=testing    --set global.tibco.serviceAccount=testingaccount

   Note: Optionally to enable creation of network policies, see Data Plane Network Policies.

   Here primaryNamespaceName is the namespace used when registering data plane. It is same for all application namespaces.