-
Notifications
You must be signed in to change notification settings - Fork 486
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
Release for Kong 3.9 #1218
Comments
Feel free to submit a PR. You can base your work on #1192 which was done for 3.8. |
ybasket
added a commit
to ybasket/kong-charts
that referenced
this issue
Jan 15, 2025
Just bumping the version under the assumption that the new version doesn't require any changes to the helm chart itself. Closes Kong#1218
ybasket
added a commit
to ybasket/kong-charts
that referenced
this issue
Jan 15, 2025
Just bumping the version under the assumption that the new version doesn't require any changes to the helm chart itself. Closes Kong#1218
ybasket
added a commit
to ybasket/kong-charts
that referenced
this issue
Jan 15, 2025
Just bumping the version under the assumption that the new version doesn't require any changes to the helm chart itself. Closes Kong#1218
pmalek
added a commit
that referenced
this issue
Jan 17, 2025
* (feat): bump Kong version to 3.9 Just bumping the version under the assumption that the new version doesn't require any changes to the helm chart itself. Closes #1218 * Update charts/kong/CHANGELOG.md --------- Co-authored-by: Patryk Małek <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
as far as I can see, there's no updated
kong/kong
helm chart version for Kong 3.9. Is that correct?Would be great to get one so people can safely and easily update – especially helpful as Kong 3.9 resolves some CVEs scanners detect. With the chart non being updated, I can bump the image tag by setting the specific helm value, but I don't know whether there are any changes the helm chart should cater for. Are there any?
If it's only about bumping the version, I can volunteer to send a PR.
The text was updated successfully, but these errors were encountered: