v1beta1 failed mutation requests #4533
In what area(s)?
What version of Knative?
Updating Knative Services through the v1beta1 endpoint works.
Editing a Knative Service objects returns an error from the API Server.
Steps to Reproduce the Problem
This is how my cluster got into this state. Not sure which parts are relevant.
Easiest way I have reproduced this.
referenced this issue
Jun 26, 2019
Here's how this is shaping up in my head....
By dark launching v1beta1 in 0.7 we bumped our minimum required Kubernetes version from 1.11 to 1.14 (the version where the fix landed), this was unintentional.
The "fix" for this is a relatively simple config-only change: strip these lines, and disable some tests. In a perfect world we'd have the operator already, and we could optionally enable
So I think we have a few options:
At this point, I think 1.14 is far too new for
So I think
The idea would be to release something like:
instead of our normal:
The diff between the two release YAMLs would be the addition of the "v1beta1" endpoint in the
The idea is that:
The downsides as discussed in the API working group meeting is:
We did not reach a conclusion between option 1 and option 2 in the meeting. There is also likely some space between these options (i.e. setup 1.14 test cluster with v1beta1, but don't create a release yaml for it).
I tested using
I have a feeling it is not going to work but I will try to add it in our upgrade tests and give it a go.…
On Wed, Jun 26, 2019 at 1:06 PM Dave Protasowski ***@***.***> wrote: @dgerd <https://github.com/dgerd> Out of curiosity does a versioned v1beta1 client work? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#4533?email_source=notifications&email_token=AKLJ6MQ2MZKXEH35EHL4DC3P4PD27A5CNFSM4H3NCB4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYUVIEY#issuecomment-506024979>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AKLJ6MVMQX63N2QQSDUJGQ3P4PD27ANCNFSM4H3NCB4A> .
referenced this issue
Jun 27, 2019
The current thought on this is:
As we approach the release of Knative 0.8 we should re-evaluate the need to ship separate YAMLs based upon the adoption of Kubernetes 1.14 across users and cloud vendors.