Add component-gateway-api as dependency for CRD install and resource generation and update kgateway to v2.4.2 - #13
Conversation
|
🚀 This PR has been released as Triggering workflows 🛠️ Auto tagging enabled with label |
0639708 to
651217f
Compare
651217f to
f2f835f
Compare
3d831ed to
2abdff5
Compare
simu
left a comment
There was a problem hiding this comment.
Same here, technically a breaking change, but not sure if this component is ready for v1.
kgateway v2.4.x supports GWAPI versions 1.4 - 1.6 https://kgateway.dev/docs/envoy/latest/reference/versions/
Definitely makes sense. I’ll be releasing this as v1.0.0 while also bumping the actual kgateway version to v2.4.2. According to the compatibility matrix, the least supported version of GWAPI is 1.4. I also ran a successful migration test using kgateway v2.4.2 with the separate GWAPI component on one of my kgateway enabled clusters. It was a smooth transition. |
| kgateway-crds: | ||
| source: oci://cr.kgateway.dev/kgateway-dev/charts/kgateway-crds | ||
| version: 2.3.6 | ||
| version: 2.4.2 |
There was a problem hiding this comment.
With this change, the PR clearly doesn't check the box "PR contains a single logical change (to build a better changelog)." anymore.
Checklist
changelog.
The PR has a meaningful description that sums up the change. It will be
linked in the changelog.
bug,enhancement,documentation,change,breaking,dependencyas they show up in the changelog.