Open joshdover opened 9 months ago
Hello @joshdover in this draft PR https://github.com/elastic/cloud-on-k8s/pull/7356 you can find an initial effort that satisfies some of the bullets mentioned in the description.
In a high-level overview:
cc @norrietaylor
From my perspective, the progress on https://github.com/elastic/cloud-on-k8s/pull/7356 is already very solid. I think we have a few things to tighten up, but I'd like to discuss what we need to merge in an initial version of this and start iterating towards a beta. Here's what I'm thinking:
Blockers to merge initial PR:
Blockers to beta release:
Optional for GA, can be done later:
We are going to need some automation to keep the integrations configurations in the helm charts up to date as well.
@joshdover I just pushed the first basic e2e test for the Helm Chart PoC (https://github.com/elastic/cloud-on-k8s/pull/7356/commits/a7f9aa7ea10a46648ef34212c94a7c7eaad1e916). As proposed in this e2e test, the integrations Helm charts gets deployed, as a user would deploy it through cli, and there are checks that events exist in the expected data streams. However, all this investigation of e2e testing and the remaining debate should we go ECK or bare-k8s was the reason I reached out to certain individuals from ECK and MKI teams. My findings so far are:
Do the above findings help to make a final decision on the debate ECK vs bare-k8s?
cc @norrietaylor
With the latest iteration of this PR that captures the effort of this ticket, I consider multiple "features" as supported, namely:
Examples of the above can be found here
Although there are still some minor rough edges to polish, I think it would be tremendously helpful if we had an early run of feedback from key individuals trying out the helm chart.
cc @norrietaylor
@pkoutsovasilis according to the demo you gave us, should we consider this issue and its subtask as done?
@pkoutsovasilis according to the demo you gave us, should we consider this issue and its subtask as done?
sorry for the delay @jlind23 another issue came up and I had to switch to it, however, today I am gonna open up the Helm chart PR on elastic-agent repo that will close this one when it gets merged 🙂
Description
Extracted from an internal discussion document:
We can solve many of the challenges with deploying Agent on Kubernetes through a Helm chart for Elastic Agent. This allows us to improve the current experience by (mapped to priorities above that are not already met and easy):