Michael Morello

[As mentioned in the documentation](https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-upgrading-eck.html#k8s-beta-to-ga-upgrade) could you try to use `kubectl replace` instead of `kubectl apply` when upgrading the CRDs ? Thanks

> I actually had to sync first to add the crd's then do the replace otherwise it would complain some crd's were not there. Sorry, I'm not familiar with ArgoCD....

APM package is already set to `latest` in Kibana: ``` spec: config: xpack.fleet.packages: - name: apm version: latest ``` I'm still trying to figure out what's going on, maybe it's...

Tests are back to green status:

Hi, thanks for opening this issue and your proposals. I would like to have a better understanding of the 2 use cases you described, and understand where it would make...

@ahalamir Please use our discuss forum at https://discuss.elastic.co/c/eck for any questions. The use of custom certificates is described in the [documentation](https://www.elastic.co/guide/en/cloud-on-k8s/1.1/k8s-custom-http-certificate.html).

What is described here sounds like a request for a "federation" feature: a layer for coordinating multiple ECK deployments, potentially running in multiple Kubernetes clusters. Assuming ECK operators are aware...

On OpenShift 4, I _think_, we might need these tolerations on the `Pods`: ```yaml tolerations: - effect: NoSchedule key: node-role.kubernetes.io/master operator: Exists ``` This is because master nodes have this...

It also failed yesterday https://devops-ci.elastic.co/job/cloud-on-k8s-e2e-tests-main/384/testReport/ The most notable recent change is #5844

We are discussing an option in https://github.com/elastic/cloud-on-k8s/issues/5528 where only `MaybeForceUpgrade` would be allowed if Elasticsearch is not available/cannot be reached.