Feat: Example of how a Kubernetes deployment with labels to appear in Kagenti UI

[esnible]

Summary

This PR introduces an example of K8s Deployment manifests for an A2A agent

Related issue(s)

None.

(Optional) Testing Instructions

• Install on a Kagenti cluster using `kubectl apply -f a2a/a2a_currency_converter/deployment/k8s.yaml
• Go to the Kagenti UI and view the Deployment card for the agent

[pdettori]

Good example manifest — well-structured with helpful comments. A few suggestions:

1. managed-by: kagenti-e2e label is misleading for a user-facing example

The app.kubernetes.io/managed-by: kagenti-e2e label on both the Service and Deployment suggests this is E2E test infrastructure. Users copying this manifest will inherit that. Consider changing to something like kagenti-example or removing it, since this is a reference manifest, not a test fixture.

2. Orphan marvin volume

The marvin volume is declared in volumes: but its corresponding volumeMount is commented out. This creates an unused volume. Either comment out both or remove the volume definition entirely:

      # Uncomment if the Agent has a Marvin dependency
      # - emptyDir: {}
      #   name: marvin

3. Consider showing Secret references for API keys

The dummy values are fine for local dev, but since this is a best-practice example, it would be helpful to show a commented-out Secret reference pattern alongside the hardcoded values:

        # For production, use a Secret:
        # - name: OPENAI_API_KEY
        #   valueFrom:
        #     secretKeyRef:
        #       name: llm-credentials
        #       key: openai-api-key

4. Empty securityContext: {}

For a reference manifest, consider adding runAsNonRoot: true or a restrictive pod security context to model good practice.

---

None of these are blockers — nice addition to the examples. 👍

[esnible]

I have addressed the comments.

[pdettori]

/lgtm