Kubernetes Configuration Updates for MongoDB Connectivity

[asafchen-dig]

This issue tracks the necessary changes to fix the MongoDB connectivity issues.

Required Changes

1. Create Kubernetes Manifests:

# kubernetes/mongodb.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: petclinic-flaskdb
  labels:
    app: petclinic-flaskdb
spec:
  replicas: 1
  selector:
    matchLabels:
      app: petclinic-flaskdb
  template:
    metadata:
      labels:
        app: petclinic-flaskdb
    spec:
      containers:
      - name: mongodb
        image: mongo:latest
        ports:
        - containerPort: 27017
        env:
        - name: MONGO_INITDB_DATABASE
          value: "feedbacks"
---
apiVersion: v1
kind: Service
metadata:
  name: petclinic-flaskdb
spec:
  selector:
    app: petclinic-flaskdb
  ports:
  - protocol: TCP
    port: 27017
    targetPort: 27017
  type: ClusterIP

2. Update Application Configuration:

• Change connection string from http://petclinic-flaskdb:27017/feedbacks to mongodb://petclinic-flaskdb:27017/feedbacks
• Update any hardcoded URLs in the application code

3. Deployment Steps:
4. Create kubernetes directory in the repository root
5. Add the mongodb.yaml manifest
6. Update application configuration with correct MongoDB protocol
7. Deploy the MongoDB service
8. Verify connectivity

Verification Steps

1. Check that MongoDB pod is running
2. Verify service is accessible within the cluster
3. Test the /api/clinic-feedback/count endpoint
4. Monitor for connection errors

Related to issue: ff76e9d8-81bc-11f0-8462-168ae57aaddf

[Rajdeep1311]

Sir @asafchen-dig can I take a look at the issue?