# V1beta1 Beats and the note about upgrades

**URL:** <https://discuss.elastic.co/t/v1beta1-beats-and-the-note-about-upgrades/255103>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [November 11, 2020, 5:25pm UTC](https://discuss.elastic.co/t/v1beta1-beats-and-the-note-about-upgrades/255103 "2020-11-11T17:25:50Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![SeanPlacchetti](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/seanplacchetti/32/51652_2.png) [@SeanPlacchetti](https://discuss.elastic.co/u/SeanPlacchetti)\
**Post date:** [November 11, 2020, 5:25pm UTC](https://discuss.elastic.co/t/v1beta1-beats-and-the-note-about-upgrades/255103/1 "2020-11-11T17:25:50Z")

</div>

Hello,

I can't tell if the [note in the documentation](https://www.elastic.co/guide/en/cloud-on-k8s/1.3/k8s-upgrading-eck.html#k8s-ga-openshift) 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](http://beat.k8s.elastic.co/v1beta1)

Thanks!  
`

---

<div class="post-metadata">

**Author:** ![dkow](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dkow/32/47340_2.png) [@dkow](https://discuss.elastic.co/u/dkow)\
**Post date:** [November 12, 2020, 10:39am UTC](https://discuss.elastic.co/t/v1beta1-beats-and-the-note-about-upgrades/255103/2 "2020-11-12T10:39:25Z")

</div>

Hey @SeanPlacchetti, thanks for your question.

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

---

<div class="post-metadata">

**Author:** ![SeanPlacchetti](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/seanplacchetti/32/51652_2.png) [@SeanPlacchetti](https://discuss.elastic.co/u/SeanPlacchetti)\
**Post date:** [November 12, 2020, 6:04pm UTC](https://discuss.elastic.co/t/v1beta1-beats-and-the-note-about-upgrades/255103/3 "2020-11-12T18:04:53Z")

</div>

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](https://github.com/kubernetes/kubernetes/issues/73752).

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](https://github.com/kubernetes/kubernetes/issues/73752).

-Sean

---

<div class="post-metadata">

**Author:** ![dkow](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dkow/32/47340_2.png) [@dkow](https://discuss.elastic.co/u/dkow)\
**Post date:** [November 16, 2020, 1:37pm UTC](https://discuss.elastic.co/t/v1beta1-beats-and-the-note-about-upgrades/255103/4 "2020-11-16T13:37:04Z")

</div>

Thanks for your suggestion @SeanPlacchetti, we've made the [change](https://github.com/elastic/cloud-on-k8s/pull/3941).

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [November 4, 2022, 8:17am UTC](https://discuss.elastic.co/t/v1beta1-beats-and-the-note-about-upgrades/255103/5 "2022-11-04T08:17:27Z")

</div>