-
Notifications
You must be signed in to change notification settings - Fork 174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Operator for deployment of the API server on Kubernetes/OpenShift #106
Comments
IMHO Helm is a good choice, relatively lightweight and simple while being sufficiently flexible. |
I have the beginnings of a Helm chart; it's very simple right now, just a |
❯ helm list
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
ara ara 2 2021-10-04 06:33:24.576997 -0400 EDT deployed ara-0.3.0 1.5.7
|
@mamercad thanks for sharing ! I don't use k8s day-to-day (much less helm) and it will be great to at least be able to point at a working example to help users get started. When (or if) you feel it is ready, I would be happy to share it more broadly in case anyone would be interested in contributing. It reminds me we are due for an update of the base container image -- with fedora 35 around the corner I will wait until it comes out and skip fedora 34 in the process. |
Yep, this is the first Helm chart I've written, so, I barely know what I'm doing -- as you've mentioned, it's something someone can look at, a start. |
I found an Ara helm chart here: https://artifacthub.io/packages/helm/lib42/ara |
I still don't personally have a use case for ara with helm but I came across this chart a while back: https://github.com/sspreitzer/helm-ara |
What component is this about ?
API server
What is the idea ?
There is a demand for being able to easily deploy the ARA API server on Kubernetes and OpenShift.
We should determine what is the best way for the project to support this, whether it would be through helm charts, a native operator or perhaps using the Ansible operator SDK with our existing roles.
This is dependant on the project publishing container images so they can be deployed.
Getting images built and published is tracked in this issue: #105
The text was updated successfully, but these errors were encountered: