WFM-Auth Component Deployment on Kubernetes
This document illustrates the procedure and steps to deploy WFM-Auth Components on Kubernetes.
Before you begin, verify
- Installed Kubernetes. If not, see Deployment Planning
- Have already setup storage. If not yet, see Storage Solution - Getting Started
Prepare for WFM-Auth Deployments
Step 1: Clone the WFM-Auth repository
git clone -b <branch Name> https://gitlab.expertflow.com/wfm/wfm-auth.git
cd wfm-auth/
Step 2: Create Namespaces
Create a namespace
wfm
for all WFM components.
kubectl create namespace wfm
Step 3: Apply Image Pull secret
Run the following commands for applying ImagePullSecrets of WFM images.
kubectl apply -f WFM/registryCredits/ef-imagePullSecret-wfm-auth.yaml
Step 4: Update FQDN
Wfm-Auth Component should be accessible by a fully qualified domain name. Assign the FQDN.
Replace <FQDN> with your FQDN for wfm-reports and run this command.
sed -i 's/devops[0-9]*.ef.com/<FQDN>/g' WFM/ConfigMaps/* WFM/Ingresses/nginx/* WFM/Ingresses/traefik/*
Step 5: Deploy WFM-Auth Component
Change the directory
CODEcd WFM/
Apply ConfigMaps
CODEkubectl apply -f ConfigMaps/ef-wfm-auth-configmap.yaml
Create services for wfm-core
CODEkubectl apply -f Services/ef-wfm-auth-service.yaml
Apply the Deployment manifest
CODEkubectl apply -f Deployments/ef-wfm-auth-deployment.yaml
Before proceeding to the the next steps, wait for all the solution components to be up and ready.
CODEkubectl get pods -n wfm
Step 6 :Setup Ingress Routes
For RKE2-based Ingresses using Ingress-Nginx Controller
kubectl apply -f Ingresses/nginx/ef-wfm-auth-Ingress.yaml