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.

Sign up for GitHub

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

Jump to bottom

bug: status subresource can not be record when using CRD apiextensions.k8s.io/v1 #709

Closed
gxthrj opened this issue Oct 13, 2021 · 0 comments · Fixed by #706
Closed

bug: status subresource can not be record when using CRD apiextensions.k8s.io/v1 #709

gxthrj opened this issue Oct 13, 2021 · 0 comments · Fixed by #706
Labels
checking question Further information is requested
Projects
v1.4 Planning
Milestone
1.4.0

Comments

@gxthrj
Copy link
Contributor

gxthrj commented Oct 13, 2021

Issue description

status subresource can not be record when using CRD apiextensions.k8s.io/v1

Use CRD apiextensions.k8s.io/v1beta1 is ok.

Environment

  • your apisix-ingress-controller version (output of apisix-ingress-controller version --long); master
  • your Kubernetes cluster version (output of kubectl version); 1.14 ~ 1.21
@tokers tokers added checking question Further information is requested labels Oct 13, 2021
@tao12345666333 tao12345666333 added this to the 1.4.0 milestone Oct 13, 2021
@tao12345666333 tao12345666333 added this to To do in v1.4 Planning via automation Oct 13, 2021
@gxthrj gxthrj linked a pull request Oct 21, 2021 that will close this issue
fix: verify generation in record status #706
Merged
4 tasks
v1.4 Planning automation moved this from To do to Done Oct 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
checking question Further information is requested
Projects
No open projects
v1.4 Planning
Done
Milestone
1.4.0
Development

Successfully merging a pull request may close this issue.

fix: verify generation in record status gxthrj/apisix-ingress-controller
3 participants
@tao12345666333 @gxthrj @tokers