# Description

We are testing and exploring Agent Registry and we have realized that
deploying it to Kubernetes is easier using a Helm Chart, we could not
find one and that is why we build it.

This will be my first contribution to the project, please bear with me,
as adding a license is needed, following the project's guidelines as
well, etc. I would say this is a bare bones Helm Chart. I am completely
aware that the team needs to review it and most likely I will need to
make changes, happy to do so.

**What is included:**
**- Application Management:** Exposing and HTTP API through port 12121,
I can access the UI in my browser through this port using for example,
`kubectl port-forward` command. Also a gRPC Agent Gateway through 21212.
**- Includes a PostgreSQL with pgvector:** One can choose the version to
be deployed. Persistent storage through StorageClass. It also supports
an external database if you don't want the bundled one.
**- Security:** Non-root containers with read-only root filesystem,
secrets are auto-generated on first install. Hex-encoded JWT. Supports
pre-existing secrets so you can integrate with external secret managers.
Network policies with granular rules. Least-privilege RBAC by default.
**- Kubernetes Operations:** liveness, readiness and startup health
probes. HPA with CPU and Memory targets. PDB for voluntary disruptions.
Resource presets and affinity presets or full override block for more
control if needed.
**- Extensions:** You can change and extend through extraEnvVars,
extraVolumes; commonLabels and commonAnnotations are also supported for
better tagging. Global overrides for image, pull secrets, StorageClass
etc.

I can also provide a minimal and basic terraform code to deploy this
chart.

I was about to open an Issue and found agentregistry-dev#242 this morning so I realized
that at least there is one more person interested on having a Helm Chart
for the Agent Registry so I decided to go ahead and open a PR. I hope
this is ok.

# Change Type

```
/kind feature
```

# Release Notes

```release-note
add Helm chart to agentregistry
```

# Additional Notes

I am happy to maintain this Chart for the project.

**I have a few questions/comments to the team:**

1. What license should I use for the Chart?
2. Where shall it be hosted? what should be the release cycle?
3. I have followed Bitnami's Helm Charts best practices. I have been
using those Charts for a couple years and I like their approach however
if the project team is not happy with that, I can make the changes
needed.

Please, make suggestions and comments so this Helm can be improved and
hopefully approved by the team. Again, bear with me, this is my first
contribution.

---------

Co-authored-by: Copilot <[email protected]>

# Description
This is a follow up to PR #245. This PR addresses the suggestions from
@peterj and @timflannagan. This continues the implementation of #242.
This PR includes 2 new workflows one to test and another to create a
release of the chart. The set of targets in the Makefile just for the
charts. I have tried to be very careful on messing with something else.

**I want to bring to your attention a couple things:**
1. There are variables that need to be set for the workflow to work (I
can change them if needed):

```
HELM_REGISTRY_PASSWORD
HELM_REGISTRY
HELM_REGISTRY_USERNAME
HELM_REPO
```

2. In our tests we have noticed that you always need kMCP (CRDs and the
tool itself). We initially through it was kAgent but we narrowed it down
to kMCP so Agent Registry can actually created the pod. We tested with
just the CRDs, the MCP is deployed but no pod is created, with the tool
itself it seems to work correctly.

Shall I add kMCP as a dependency of the Agent Registry chart and also
create a section in the values.yaml in which it can be enabled and
configured? otherwise administrators will have to do this separately and
it seems the documentation is not including this information.

# Change type
/kind cleanup

# Changelog
```release-note
Adding a Helm Chart
```

---------

Co-authored-by: Copilot <[email protected]>