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

Release Kong 2.8.0 #576

Merged
merged 2 commits into from
Apr 15, 2022
+39 −7
Merged

Release Kong 2.8.0 #576

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
81d6d3f
chore(deps) update controller to 2.3
rainest Apr 6, 2022
aa6e734
chore(*) release Kong 2.8.0
rainest Apr 7, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
chore(*) release Kong 2.8.0
  • Loading branch information
@rainest
rainest committed Apr 14, 2022
commit aa6e73442e5d32c8af3f4e2f000e439578020996
11 changes: 7 additions & 4 deletions charts/kong/CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,14 +2,15 @@

## Unreleased

* Updated podDisruptionBudget from `policy/v1beta1` to `policy/v1`.
([574](https://github.com/Kong/charts/pull/574))
Nothing yet.

## 2.8.0

### Improvements

* feat(services) add Ingress for cluster sync
* Added Ingress for cluster sync.
([583](https://github.com/Kong/charts/pull/583))
* feat(deployment) allow custom environment variables to be configured for the ingress-controller container
* Added controller support for custom environment variables.
([568](https://github.com/Kong/charts/pull/568))
* Ingress `pathType` field is now configurable.
([564](https://github.com/Kong/charts/pull/564))
Expand All @@ -28,6 +29,8 @@
* Improved support and documentation for installations that [lack
cluster-scoped permissions](https://github.com/Kong/charts/blob/main/charts/kong/README.md#removing-cluster-scoped-permissions).
([565](https://github.com/Kong/charts/pull/565))
* Updated podDisruptionBudget from `policy/v1beta1` to `policy/v1`.
([574](https://github.com/Kong/charts/pull/574))
* Updated controller version to 2.3.

### Fixed
Expand Down
2 changes: 1 addition & 1 deletion charts/kong/Chart.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ maintainers:
email: [email protected]
name: kong
sources:
version: 2.7.0
version: 2.8.0
appVersion: "2.8"
dependencies:
- name: postgresql
Expand Down
28 changes: 28 additions & 0 deletions charts/kong/UPGRADE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,7 @@ upgrading from a previous version.
## Table of contents

- [Upgrade considerations for all versions](#upgrade-considerations-for-all-versions)
- [2.8.0](#280)
- [2.7.0](#270)
- [2.4.0](#240)
- [2.3.0](#230)
Expand Down Expand Up @@ -62,6 +63,33 @@ text ending with `field is immutable`. This is typically due to a bug with the
If you encounter this error, deleting any existing `init-migrations` jobs will
clear it.

## 2.8.0

2.8 updates the Postgres subchart version from 8.6.8 to 11.1.15. This changes
a number of values.yaml keys and the default Postgres version. The previous
default Postgres version was [11.7.0-debian-10-r37](https://github.com/bitnami/charts/blob/590c6b0f4e07161614453b12efe71f22e0c00a46/bitnami/postgresql/values.yaml#L18).

To use the new version on an existing install, you should [follow Bitnami's
instructions for updating values.yaml keys and upgrading their chart]() as well
as [the Postgres upgrade instructions](https://www.postgresql.org/docs/current/upgrading.html).

You can alternately use the new chart without upgrading Postgres by setting
`postgresql.image.tag=11.7.0-debian-10-r37` or use the old version of the
chart. Helm documentation is unclear on whether ignoring a subchart version
change for a release is possible, so we recommend [dumping the
database](https://www.postgresql.org/docs/current/backup-dump.html) and
creating a separate release if you wish to continue using 8.6.8:

```
$ helm install my-release -f values.yaml --version 8.6.8 bitnami/postgresql
```

Afterwords, you will upgrade your Kong chart release with
`postgresql.enabled=false` and `env.pg_host` and `env.pg_password` set to the
appropriate hostname and Secret reference for your new release (these are set
automatically when the subchart is enabled, but will not be set automatically
with a separate release).

## 2.7.0

2.7 updates CRDs to the version released in KIC 2.1.0. Helm does not upgrade
Expand Down