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

The upstream k8s API is invalid #165

Closed
kluevandrew opened this issue Dec 22, 2022 · 0 comments · Fixed by #167
Closed

The upstream k8s API is invalid #165

kluevandrew opened this issue Dec 22, 2022 · 0 comments · Fixed by #167
Assignees
@kluevandrew
Labels
bug Something isn't working
Milestone
Release 1.0.0-rc2

Comments

@kluevandrew
Copy link
Contributor

According to discussion kubernetes-sigs/controller-tools#753 and PR kubernetes/kubernetes#114585 the k8s api has a wrong type for "Claims" field in version v1.26, it fixed in version v1.27 but not released yet. We need to update workaround made in #164 to change type of field but and not add an "atomic", or may-be completely drop that field form our CRD's while v1.27 is not released
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kluevandrew kluevandrew

Labels
bug Something isn't working
Projects
None yet
Milestone
Release 1.0.0-rc2
Development

Successfully merging a pull request may close this issue.

Workaround for invalid upstream k8s API tarantool/tarantool-operator
1 participant
@kluevandrew