recursive dirs

[mtcderek]

No description provided.

[cloudsprints-grader]

❌ CloudSprints Grading — 0/2 tasks passed

	Task	Status
❌	Convert the Webapp pod to a Deployment	FAILED
❌	Scale the Webapp to 3 replicas	FAILED

---

💡 Convert the Webapp pod to a Deployment

Kumar Singh: Great start on setting up your environment! I can see you have a well-configured Pod with proper resource limits, health checks, and labels - that's excellent foundational work! However, the configuration still shows a standalone Pod (kind: Pod) rather than a Deployment (kind: Deployment). To scale your application properly for the go-live, you'll need to convert this to a Deployment. Here's what you need to do:

1. Change kind: Pod to kind: Deployment
2. Add a spec.replicas field to specify how many instances you want
3. Wrap your Pod specification inside a spec.template section
4. Add a spec.selector with matchLabels that match your Pod labels

Here's a hint for the structure:

apiVersion: apps/v1
kind: Deployment
metadata:
  name: webapp
spec:
  replicas: 1  # You'll adjust this in the next task!
  selector:
    matchLabels:
      app: webapp
      tier: frontend
  template:
    metadata:
      labels:
        app: webapp
        tier: frontend
        version: v1
    spec:
      # Your existing container spec goes here

You're on the right track - just need to restructure it as a Deployment!

💡 Scale the Webapp to 3 replicas

Kumar Singh: Almost there! Since the configuration is still using a Pod instead of a Deployment, we can't scale it to 3 replicas yet. Pods are single instances and don't have a replica field - that's a Deployment feature! Once you complete Task 1 and convert to a Deployment, scaling will be super easy. You'll just need to set spec.replicas: 3 in your Deployment manifest. The beauty of Deployments is that Kubernetes will automatically create and manage 3 identical copies of your webapp Pod, ensuring high availability for your go-live! Keep going - you're building the right foundation with those resource limits and health checks!

---

Graded by CloudSprints

[cloudsprints-grader]

❌ CloudSprints Grading — 0/2 tasks passed

	Task	Status
❌	Convert the Webapp pod to a Deployment	FAILED
❌	Scale the Webapp to 3 replicas	FAILED

---

💡 Convert the Webapp pod to a Deployment

Rachel Osgood: Per our success metrics and stakeholder requirements, this deliverable presents an opportunity for realignment. The configuration still maintains a standalone Pod architecture (apiVersion: v2, kind: Pod) rather than leveraging a Deployment resource. To synergize with industry best practices and meet our KPIs, the student needs to action the following items: (1) Convert the 'kind' field from 'Pod' to 'Deployment', (2) Update the apiVersion to 'apps/v1', (3) Restructure the manifest to include a spec.template section that encapsulates the current Pod specification, and (4) Add a spec.selector.matchLabels field to align with the label strategy. The current implementation is misaligned with our scalability objectives and does not position us for horizontal scaling capabilities.

💡 Scale the Webapp to 3 replicas

Rachel Osgood: This action item remains unaddressed and presents a critical gap in our deliverables. The configuration lacks a 'spec.replicas' field entirely, which is a fundamental requirement for achieving our scaling targets. Since the resource has not been converted to a Deployment architecture (as noted in Task 1), the replica scaling mechanism cannot be implemented. To circle back and realign with expectations, the student must first complete the Deployment conversion, then add 'replicas: 3' under the spec section. Without these changes, we cannot leverage horizontal scaling capabilities or meet our go-live readiness criteria. This represents a blocking issue for our production deployment strategy.

---

Graded by CloudSprints

[cloudsprints-grader]

✅ CloudSprints Grading — All 2 tasks passed!

	Task	Status
✅	Convert the Webapp pod to a Deployment	COMPLETED
✅	Scale the Webapp to 3 replicas	COMPLETED

---

Graded by CloudSprints