Skip to content

Conversation

@t-persson
Copy link
Collaborator

Applicable Issues

Description of the Change

This change creates a program for deploying a local ETOS cluster on an existing kind cluster. It is very similar to how we deploy ETOS when running e2e tests. This deployment should be used to test changes locally before sending a PR.
The program has a few Packs which can return a set of Commands that should be run to deploy that Pack. The name Pack is not that descriptive but I struggled to find a better name for a collection of commands to deploy and verify a set of resources.
Then we just execute the commands in the order they are defined to deploy ETOS properly. At the end we also run a quick verification that the cluster works by running a TestRun in the new cluster.

The cluster be deployed using make deploy-local and undeployed using undeploy-local
The cluster will not work with the etos client at the moment since we do not deploy an ingress (and deploying an ingress would make everything much more complex).
It is still possible to create TestRun resources directly to the cluster which allows us to test ETOS locally.

Alternate Designs

We could add this to etosctl to make it more available, but it would require the makefile to install etos client which I wanted to avoid for now. Currently we have no external python dependencies with this program.

Possible Drawbacks

There are a few things here that we should investigate.
The program assumes that the config/samples work and don't change too much.
It hard codes versions for cert-manager and prometheus.
It uses the config/samples/*cluster.yaml file which does not get updated image versions.

All of these problems should be fixed and I will write issues for them after I've merged this PR.

Sign-off

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
indicated in the file; or

(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
permitted to submit under a different license), as indicated
in the file; or

(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
it.

(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including all
personal information I submit with it, including my sign-off) is
maintained indefinitely and may be redistributed consistent with
this project or the open source license(s) involved.

Signed-off-by: Tobias Persson tobias.persson@axis.com

Can be deployed using make deploy-local and undeployed using
undeploy-local
Deploying a local ETOS this way will enable to use of ETOS locally but
will not work with the etos client at the moment since we do not deploy
an ingress.
It is still possible to create TestRun resources directly to the
cluster which allows us to test ETOS locally.
@t-persson t-persson requested a review from a team as a code owner October 22, 2025 10:26
@t-persson t-persson requested review from andmat900 and fredjn and removed request for a team October 22, 2025 10:26
@andmat900
Copy link
Contributor

Please add some documentation explaining what this is and how to use it.

@t-persson
Copy link
Collaborator Author

Please add some documentation explaining what this is and how to use it.

Done.

@t-persson t-persson requested a review from andmat900 November 5, 2025 07:53
@t-persson t-persson merged commit 110b3b2 into eiffel-community:main Nov 5, 2025
3 checks passed
@t-persson t-persson deleted the local-etos-deployment branch November 5, 2025 09:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants