V1beta1 Beats and the note about upgrades

Elastic Orchestration Elastic Cloud on Kubernetes (ECK)
1

Hello,

I can't tell if the note in the documentation about Operator upgrades running on Openshift 3.11 applies to the Beats or just the Elasticsearch deployments through ECK. Our Beat yamls are based on the quickstarts and are `apiVersion: beat.k8s.elastic.co/v1beta1

Thanks!
`

2

Hey @SeanPlacchetti, thanks for your question.

Beat CRD in ECK 1.3.0 didn't change its apiVersion so this note does not apply.

1 Like
3

Thanks again David. The explanation that the documentation note is only applicable when it's resource apiVersion being updated and not the ECK version is helpful. Do you think we could clarify the wording for others? Maybe something like:

If you are running Openshift 3.11 or a Kubernetes version older than 1.13 and have existing resources created using the v1beta1 API version, in-place upgrade is not possible due to an upstream bug.

Changes to:

If you are running Openshift 3.11 or a Kubernetes version older than 1.13 and have existing resources created using the v1beta1 API version that are being updated to v1 API version as part of the ECK upgrade, then in-place upgrade of those resources is not possible due to an upstream bug.

-Sean

1 Like
4

Thanks for your suggestion @SeanPlacchetti, we've made the change.

2 Likes