cloud-on-k8s
cloud-on-k8s copied to clipboard
Elastic Cloud on Kubernetes
I'm opening this issue mostly to document a discussion around supporting [`.spec.ordinals.start`](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#statefulsetordinals-v1-apps) in the [`nodeSet` specification](https://www.elastic.co/guide/en/cloud-on-k8s/master/k8s-api-elasticsearch-k8s-elastic-co-v1.html#k8s-api-github-com-elastic-cloud-on-k8s-v2-pkg-apis-elasticsearch-v1-nodeset). This would allow users to move selectively ES nodes in a more flexible way...
We added a new way to do the readiness probe, by using a tcp port. When this is enabled we remove the credentials that were added as ENV and used...
We are seeing issues with upgrading to 2.14.0 when there are overrides present for the readiness probe, adding the ENVs that have the credentials for the old readiness probe to...
## Bug Report **What did you do?** We wanted to define our pipeline via secret, so we have configured pipelinesRef in values: ```yaml eck-logstash: enabled: true pipelinesRef: secretName: logstash-pipelines-secret ```...
We had several failures for these tests, including on ECK 2.4.0: ### TestLogstashEsOutput/Logstash_should_respond_to_default_pipeline_requests ~ stack-8-15-0-sna ``` === RUN TestLogstashEsOutput/Logstash_should_respond_to_default_pipeline_requests step.go:51: Error Trace: /go/src/github.com/elastic/cloud-on-k8s/test/e2e/test/utils.go:94 Error: Received unexpected error: fail to request...
We have documented how to add SAML based SSO, but we do not have documentation on how to configure OIDC based SSO in general, we only have documentation on how...
## Bug Report This is very similar to the problem reported in https://github.com/elastic/cloud-on-k8s/issues/2266, except it is surfaced in a way that the fix for that issue doesn't work. The way...
## Proposal Adding Elastic Maps Server: 8.14+ to eck-stack **Use case. Why is this important?** Complete Management of ElasticSearch CRD instances as helm dependency via eck-stack instead of using custom...
## Allow ECK deployed Elastic Agents to output to a Logstash Ref I'm trying to configure my Elastic Agents to output to Logstash so that I can do some logstashy...
- #5240 was implemented for the purpose of Stack Monitoring but we designed it to be usable for all associations. Today, it is tested and documented only for Stack Monitoring....