KE/TZ/UG/SWIFT K8S Deployment Guide

1. Connect to CyberArk.
2. Connect to Host cont16059.
3. cd IMAGE
4. rm -rf <SERVICE-NAME-SHARED-BY-DEV-TEAM>
5. Clone the Repository as shared by Dev/Admin:

   Copy
   
   git clone git@extio_git_srv1/<SERVICE-NAME>.git
   # OR
   git clone git@extio_git_srv2/<SERVICE-NAME>.git
   cd <MODULE-NAME>
   # Example:
   cd az-some-module
   

   Clone issues (SSH/Network)

   ! Clone Issues? If “Host key verification failed”, confirm SSH keys and host trust; if “Connection timed out”, check firewall or use the alternate host; use ssh -v git@extio_git_srv1 for verbose debugging.
6. Switch to the latest branch:

   Copy
   
   git branch --all
   git checkout <LATEST-BRANCH-NAME>
   

   ! If the branch is not found, confirm the exact name with Dev/Admin and run git fetch --all.
7. Export the Docker Registry Host (see Table A):

   Copy
   
   export DOCKER_HOST=tcp://<DOCKER-HOST-IP>:2375
   

   Environment variable not set?

   i Verify with echo $DOCKER_HOST; if empty, re-run export and add to shell profile for persistence (e.g., ~/.bashrc).
8. Run Maven build & push:

   Copy
   
   mvn clean package fabric8:build fabric8:push -DskipTests
   

   ! Build failures may indicate network/proxy issues, Docker daemon problems (docker info), disk space (df -h), or incompatible Maven/Java versions.
9. If it shows BUILD SUCCESS, proceed to Part 2; otherwise, escalate to Dev/Admin with logs.

1. Connect to Host cont160150.
2. Navigate to deployment specs:

   Copy
   
   cd /home/bastion/DEPLOYMENT-SPECS/<ENVIRONMENT>/<COUNTRY>
   # Example:
   cd /home/bastion/DEPLOYMENT-SPECS/UAT/KE
   

   Cannot find directory?

   ! Confirm environment and country folders, check permissions (ls -ld /home/bastion/DEPLOYMENT-SPECS/*), and verify the correct host.
3. Change to module directory:

   Copy
   
   cd <MODULE-NAME>
   # Example:
   cd az-some-module
   

   ! If missing, ensure the module was cloned correctly in Part 1 and verify path spelling/casing.
4. Edit the deployment YAML to update the image version:

   Copy
   
   vi deploy.yaml
   # OR
   vi production-deploy.yaml
   

   Example line inside YAML:

   image: registry.apizone.io:3000/az-some-module:1.0.6-RELEASE

   Image version errors?

   ! Confirm the exact tag from build logs; mistyped tags cause pull failures; optionally verify with docker pull <image>:<tag>.
5. Add or update required ENV variables:

   Copy
   
   - name: SOME_VARIABLE
     value: "someValue"
   

   ! Missing or incorrect ENV variables commonly cause crashes or misconfiguration; confirm with Dev/Admin.
6. Source environment (see Table B):

   Copy
   
   source ke-msb-uat
   

   Source file fails?

   ! Verify file existence/permissions (ls -l ke-msb-uat) and correct for syntax errors inside the source file.
7. Deploy to K8S:

   Copy
   
   kubectl apply -f <DEPLOYMENT-YAML-FILE>
   # Example:
   kubectl apply -f deploy.yaml
   

   ! If deployment fails, validate YAML syntax with kubectl apply --dry-run=client, check context (kubectl config current-context), and ensure RBAC permissions.
8. Check Pod status and logs:

   Copy
   
   pods | grep <MODULE-NAME>
   n-logs 100 <POD-NAME>
   desc <POD-NAME> | grep -i image
   

   Pods not running or crashing?

   ! Use kubectl describe pod <POD-NAME> and kubectl logs <POD-NAME>; common issues include image pulls, env vars, resource limits, and volumes.

1. Follow the same KE/TZ/UG build steps on host cont16059.
2. Before running the Maven build, set the DOCKER_HOST for SWIFT UAT:

   Copy
   
   export DOCKER_HOST=tcp://10.137.160.187:2375
   

3. Proceed with the mvn clean package … build and push.

1. Connect to Host cont160150.
2. Navigate to SWIFT UAT deployment directory:

   Copy
   
   cd /home/bastion/DEPLOYMENT-SPECS/UAT/SWIFT/<Module_Directory>
   

3. Update YAML, source the environment, and apply with kubectl as in Part 2.

1. On host cont16059: set Docker Host to the registry.

   Copy
   
   export DOCKER_HOST=tcp://10.137.160.187:2375
   

2. On host cont16059: save the Docker image to a tar file.

   Copy
   
   docker save -o /tmp/image-name.tar image:tag
   

3. From local machine: copy image from cont16059 to local Downloads.

   Copy
   
   scp cont16059:/tmp/image-name.tar Downloads/
   

4. From local machine: copy to intermediate host cont17150.

   Copy
   
   scp Downloads/image-name.tar cont17150:/tmp/
   

5. On host cont17150: transfer to production registry 10.0.1.100.

   Copy
   
   # Log in to cont17150
   su - extio_user
   # Pass: T@er!shn2fed9
   sudo su -
   # Pass: T@er!shn2fed9
   su - apizone
   scp /tmp/image-name.tar 10.0.1.100:/tmp/
   

6. On production registry host 10.0.1.100: load and push.

   Copy
   
   ssh 10.0.1.100
   sudo su -
   cd /tmp
   docker load -i /tmp/image-name.tar
   docker push image:version
   

1. Connect to Host cont160150.
2. Navigate to SWIFT PROD deployment directory:

   Copy
   
   cd /home/bastion/DEPLOYMENT-SPECS/PROD/SWIFT
   

3. Update production-deploy.yaml, source correct env (e.g., source swift-msb-prod), and apply.

i For unresolved issues, collect exact error messages, relevant YAML, and recent logs before escalation to Dev/Admin.