Open
Description
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/[email protected] 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/[email protected] 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 |
Metadata
Assignees
Labels
No labels