Kubernetes Manifest File Creation for Gateway and PS

[prasad-takale-eminds]

Description

Develop Kubernetes manifest files to deploy the Gateway and PS components. The manifest files should include specifications for deployment, services, and other necessary resources to ensure scalable and reliable deployments.

Goals

• Create deployment YAML files for Gateway and PS components.
• Include service configurations for each component.
• Ensure the manifests support scalability and reliability.
• Verify compatibility with the existing Kubernetes cluster configuration.

Expected Outcome

Well-defined Kubernetes manifest files for Gateway and PS, enabling seamless deployment, scaling, and management within the Kubernetes cluster.

Acceptance Criteria

• Deployment YAML files are functional and error-free.
• Services are correctly configured to expose Gateway and PS components.
• Resources (CPU, memory) are optimized and defined in the manifests.
• Successfully deploy and test the components on the Kubernetes cluster.

Mockups / Wireframes

NA

Product Name

Beckn

Domain

TBD

Tech Skills Needed

• Kubernetes
• YAML
• Kubernetes Deployment and Service Management
• CI/CD Integration

Complexity

High

Category

Infrastructure

Sub Category

Kubernetes Configuration

[prasad-takale-eminds]

As part of this task, I have successfully created the necessary Kubernetes manifest files for the gateway service. These include the Deployment, Service, ConfigMap, and PersistentVolume resources.

Key details:

• The swf.properties and onix.json configuration files are handled via a ConfigMap with placeholders for dynamic variables (e.g., GATEWAY_URL, GATEWAY_PORT, REGISTRY_ID, etc.).
• PersistentVolume and PersistentVolumeClaim resources are defined to map the external volumes (gateway_data_volume, gateway_database_volume, and gateway_logs_volume).
• The manifests were tested locally and are working as expected.

Next Steps:
I plan to move forward with creating the required manifest files for the protocol server while maintaining consistency in configuration and deployment practices.