<p>I have managed to solve it myself later that day, I had to disable one of the apigroups within the specific crd that is responsible for the given object.
In that case it was editing:
kubectl edit crd virtualservices.networking.istio.io
And then change:</p>

<pre><code>  versions:
  - name: v1alpha3
    served: true
    storage: true
  - name: v1beta1
    served: true
    storage: false
</code></pre>

<p>to</p>

<pre><code>  versions:
  - name: v1alpha3
    served: true
    storage: true
  - name: v1beta1
    served: false
    storage: false
</code></pre>

<p>Then on redeploy I had the correct apigroup which I wanted.</p>

CC BY-SA 4.0
2020-05-26T14:43:41.233Z
2020-05-26T14:43:41.233Z
anVzdGFub3RoZXJodW1hbg
<p>I am having troubles creating an object within specific api group it gets switced from alpha to beta, why? networking.istio.io/v1beta1 vs networking.istio.io/v1alpha3</p>

<p>Note: I can control in the crd virtualservice.</p>

<kubernetes><istio>
Istio Virtual service - enforce specific api version
anVzdGFub3RoZXJodW1hbg
# Istio Virtual service - enforce specific api version

(Asked by: username_0 on 2020-05-22)

I am having troubles creating an object within specific api group it gets switced from alpha to beta, why? networking.istio.io/v1beta1 vs networking.istio.io/v1alpha3

Note: I can control in the crd virtualservice.

**Tags:** kubernetes, istio


---

## 1 answers

### Answer by username_0 on 2020-05-26. Score: 0 | Accepted answer

I have managed to solve it myself later that day, I had to disable one of the apigroups within the specific crd that is responsible for the given object.
In that case it was editing:
kubectl edit crd virtualservices.networking.istio.io
And then change:
  versions:
  - name: v1alpha3
    served: true
    storage: true
  - name: v1beta1
    served: true
    storage: false

to
  versions:
  - name: v1alpha3
    served: true
    storage: true
  - name: v1beta1
    served: false
    storage: false

Then on redeploy I had the correct apigroup which I wanted.


---

