Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cannot decode incoming new object: json: unknown field "subresource" (Kubernetes 1.22) #429

Closed
AverageMarcus opened this issue Sep 27, 2021 · 1 comment
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now.
Milestone

Comments

@AverageMarcus
Copy link
Contributor

Expected Behavior

Successful installation of Tekton via the Operator TektonConfig CRD

Actual Behavior

Error produced when applying the CRD:

'Warning' reason: 'UpdateFailed' Failed to update status for \"config\": admission webhook \"webhook.operator.tekton.dev\" denied the request: mutation failed: cannot decode incoming new object: json: unknown field \"subresource\"

Steps to Reproduce the Problem

  1. On Kubernetes 1.22 install Tekton Operator
  2. Attempt to apply a new TektonConfig CR

Additional Info

  • Kubernetes version: 1.22

  • Tekton Pipeline version: N/a

  • Tekton Operator version: 0.49.0

I think it's related to Knative and this issue: knative/serving#11448 which was apparently fixed in the knative-0.22 release on the 2nd Sept.

@vdemeester on Slack:

We patched it in master but it's not on a release version yet. cc Nikhil Thomas we should probably do a patch release of 0.49.x

So it seems like this is just requiring a new patch release to be created.

@AverageMarcus AverageMarcus added the kind/bug Categorizes issue or PR as related to a bug. label Sep 27, 2021
@vdemeester vdemeester added this to the 0.49 milestone Sep 27, 2021
@vdemeester vdemeester added the priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. label Sep 29, 2021
@AverageMarcus
Copy link
Contributor Author

AverageMarcus commented Oct 23, 2021

Update: This issue is still present in the v0.50.0 release

Ignore that, I didn't update the install manifest. Looks like it might be resolved now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now.
Projects
None yet
Development

No branches or pull requests

2 participants