Peter Brachwitz
Peter Brachwitz
> Where is the logic that configures Fleet Server to run for reference? https://github.com/elastic/cloud-on-k8s/blob/08c73c3d5ae1f14eb74a3d048be171d08c244746/pkg/controller/agent/pod.go#L525-L542 > The URLs in the logs are a bit surprising since I see attempting to enroll...
This is a tricky one. I believe we are bound by the behaviour of controller-runtime/the k8s client here. I would probably see if it is possible to run the operator...
Closing due to inactivity
The failures on 8.19 seem to be an ECK regression introduced in 3.1.0. I am marking this a bug therefore.
We were testing versions without the fix for https://github.com/elastic/kibana/pull/230211 We need to test instead 8.17.10, 8.18.8, 8.19.2 or later
buildkite test this -f p=gke,E2E_TAGS=agent,s=9.3.0-SNAPSHOT
buildkite test this -f p=gke,E2E_TAGS=agent,s=9.3.0-SNAPSHOT
This workaround is relying on implementation internals of the ECK operator that can change from release to release. The readiness probe implementation is not part of our public interface for...
buildkite test this -f p=gke,E2E_TAGS=epr
The ECK operator uses a file realm user for orchestration purposes. We want to make sure that ECK is always able to manage Elasticsearch by giving the file realm a...