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

go.mod differs from compat matrix #476

Open
colin-arnott-xero opened this issue Jun 28, 2022 · 0 comments
Open

go.mod differs from compat matrix #476

colin-arnott-xero opened this issue Jun 28, 2022 · 0 comments

Comments

@colin-arnott-xero
Copy link
Contributor

colin-arnott-xero commented Jun 28, 2022

Currently the gloo (edge) docs list explicit compatibility with kubernetes versions. The go.mod on the other hand, pins [recte replace] to one specific kubernetes version. For 1.10 and 1.11, this version is even outside of the gloo (edge) supported range. As well, I am unclear what I should do as a consumer if I want to use symbols from k8s.io/api@v0.22.0 in my controller, when solo-apis requires that I use a lower version. Similarly, because every kubernetes "minor" version may include breaking changes removing deprecated symbols, what should I do if I need symbols that from k8s.io/api@v0.19.0 that do not exist in solo-apis' version?

gloo series kubernetes compat kubernetes go.mod
1.11.x 1.21 - 1.22 1.20.9
1.10.x 1.21 - 1.22 1.20.9
1.9.x 1.19 - 1.22 1.19.6
1.8.x 1.19 - 1.21 1.19.6
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant