Releases: sighupio/fury-kubernetes-kong
Release v2.8.1
Kong Add-on Module Release 2.8.1
Welcome to the latest release of the kong
add-on module for Kubernetes Fury Distribution
maintained by team
SIGHUP.
This is a minor release with the goal to update Kong images and kong ingress controllers to the latest version available.
Component Images 🚢
Component | Supported Version | Previous Version |
---|---|---|
kong |
v2.8.1 |
v2.3.2 |
kong/kong-gateway |
v2.8.1.0 |
v2.4.1.1 |
kong/kubernetes-ingress-controller |
v2.3.1 |
v1.3.1 |
Update Guide for db-less deployment options 🦮
To update your Kong cluster to the latest version, you simply need to apply the updated manifests.
There will be some downtime while the new version is deployed.
Update Guide for db deployment options 🦍
To update your kong cluster to the latest version you need to follow the following upgrade procedure, there will be some
downtime while the new version is deployed:
Delete the existing job using:
kubectl delete job kong-migrations
Then patch the migration with the migrations up
command:
---
apiVersion: batch/v1
kind: Job
metadata:
name: kong-migrations
namespace: kong
spec:
template:
spec:
containers:
- name: kong-migrations
command: [ "/bin/sh", "-c", "kong migrations up" ]
restartPolicy: OnFailure
Apply the new updated manifests and wait for the job to complete.
Then delete the old kong-migrations job:
kubectl delete job kong-migrations
Now patch the migration with the migrations finish
command:
---
apiVersion: batch/v1
kind: Job
metadata:
name: kong-migrations
namespace: kong
spec:
template:
spec:
containers:
- name: kong-migrations
command: [ "/bin/sh", "-c", "kong migrations finish" ]
restartPolicy: OnFailure
Apply the new updated manifests and wait for the job to complete. All the Kong pods now should be running with the latest version.
Preview v2.8.1-rc8
Kong Add-on Module Release 2.8.1
Welcome to the latest release of the kong
add-on module for Kubernetes Fury Distribution
maintained by team
SIGHUP.
This is a minor release with the goal to update Kong images and kong ingress controllers to the latest version available.
Component Images 🚢
Component | Supported Version | Previous Version |
---|---|---|
kong |
v2.8.1 |
v2.3.2 |
kong/kong-gateway |
v2.8.1.0 |
v2.4.1.1 |
kong/kubernetes-ingress-controller |
v2.3.1 |
v1.3.1 |
Update Guide for db-less deployment options 🦮
To update your Kong cluster to the latest version, you simply need to apply the updated manifests.
There will be some downtime while the new version is deployed.
Update Guide for db deployment options 🦍
To update your kong cluster to the latest version you need to follow the following upgrade procedure, there will be some
downtime while the new version is deployed:
Delete the existing job using:
kubectl delete job kong-migrations
Then patch the migration with the migrations up
command:
---
apiVersion: batch/v1
kind: Job
metadata:
name: kong-migrations
namespace: kong
spec:
template:
spec:
containers:
- name: kong-migrations
command: [ "/bin/sh", "-c", "kong migrations up" ]
restartPolicy: OnFailure
Apply the new updated manifests and wait for the job to complete.
Then delete the old kong-migrations job:
kubectl delete job kong-migrations
Now patch the migration with the migrations finish
command:
---
apiVersion: batch/v1
kind: Job
metadata:
name: kong-migrations
namespace: kong
spec:
template:
spec:
containers:
- name: kong-migrations
command: [ "/bin/sh", "-c", "kong migrations finish" ]
restartPolicy: OnFailure
Apply the new updated manifests and wait for the job to complete. All the Kong pods now should be running with the latest version.
Preview v2.8.1-rc7
Kong Add-on Module Release 2.8.1
Welcome to the latest release of kong
module of Kubernetes Fury Distribution
maintained by team
SIGHUP.
This is a minor release with the goal to update kong images and kong ingress controllers to the latest version available.
Component Images 🚢
Component | Supported Version | Previous Version |
---|---|---|
kong |
v2.8.1 |
v2.3.2 |
kong/kong-gateway |
v2.8.1.0 |
v2.4.1.1 |
kong/kubernetes-ingress-controller |
v2.3.1 |
v1.3.1 |
Update Guide for db-less deployment options 🦮
To update your kong cluster to the latest version, you simply need to apply the updated manifests.
There will be some downtime while the new version is deployed.
Update Guide for db deployment options 🦍
To update your kong cluster to the latest version you need to follow the following upgrade procedure, there will be some
downtime while the new version is deployed:
Delete the existing job using:
kubectl delete job kong-migrations
Then patch the migration with the migrations up
command:
---
apiVersion: batch/v1
kind: Job
metadata:
name: kong-migrations
namespace: kong
spec:
template:
spec:
containers:
- name: kong-migrations
command: [ "/bin/sh", "-c", "kong migrations up" ]
restartPolicy: OnFailure
Apply the new updated manifests and wait for the job to complete.
Then delete the old kong-migrations job:
kubectl delete job kong-migrations
Now patch the migration with the migrations finish
command:
---
apiVersion: batch/v1
kind: Job
metadata:
name: kong-migrations
namespace: kong
spec:
template:
spec:
containers:
- name: kong-migrations
command: [ "/bin/sh", "-c", "kong migrations finish" ]
restartPolicy: OnFailure
Apply the new updated manifests and wait for the job to complete. All the Kong pods now should be running with the latest version.
Preview v2.8.1-rc6
Kong Add-on Module Release 2.8.1
Welcome to the latest release of kong
module of Kubernetes Fury Distribution
maintained by team
SIGHUP.
This is a minor release with the goal to update kong images and kong ingress controllers to the latest version available.
Component Images 🚢
Component | Supported Version | Previous Version |
---|---|---|
kong |
v2.8.1 |
v2.3.2 |
kong/kong-gateway |
v2.8.1.0 |
v2.4.1.1 |
kong/kubernetes-ingress-controller |
v2.3.1 |
v1.3.1 |
Update Guide for db-less deployment options 🦮
To update your kong cluster to the latest version, you simply need to apply the updated manifests.
There will be some downtime while the new version is deployed.
Update Guide for db deployment options 🦍
To update your kong cluster to the latest version you need to follow the following upgrade procedure, there will be some
downtime while the new version is deployed:
Delete the existing job using:
kubectl delete job kong-migrations
Then patch the migration with the migrations up
command:
---
apiVersion: batch/v1
kind: Job
metadata:
name: kong-migrations
namespace: kong
spec:
template:
spec:
containers:
- name: kong-migrations
command: [ "/bin/sh", "-c", "kong migrations up" ]
restartPolicy: OnFailure
Apply the new updated manifests and wait for the job to complete.
Then delete the old kong-migrations job:
kubectl delete job kong-migrations
Now patch the migration with the migrations finish
command:
---
apiVersion: batch/v1
kind: Job
metadata:
name: kong-migrations
namespace: kong
spec:
template:
spec:
containers:
- name: kong-migrations
command: [ "/bin/sh", "-c", "kong migrations finish" ]
restartPolicy: OnFailure
Apply the new updated manifests and wait for the job to complete. All the Kong pods now should be running with the latest version.
Release v2.0.0
Release notes
This release is a major release. We are adding all kind of Kong Architectures, opensource and Enterprise with examples.
Changelog
Second major release v2.0.0
- Added Katalog to deploy Kong with postgres databse
- Added Kong Enterprise katalog
- Added Kong Enterprise Hybrid katalog
- Added Kong Enterprise K8s katalog
See examples on how to deploy each architecture.
Preview v2.0.0-rc0
Release notes
This release is a major release. We are adding all kind of Kong Architectures, opensource and Enterprise with examples.
Changelog
Second major release v2.0.0
- Removed dependency from upstream
- Added Katalog to deploy Kong with postgres databse
- All the services are now type LoadBalancer
- Added Kong Enterprise katalog
- Added Kong Enterprise Hybrid katalog
- Added Kong Enterprise K8s katalog
See examples on how to deploy each architecture.
Preview v1.1.0-rc0
Kong Module version 1.1.0
SIGHUP team maintains this module updated and tested.
That is the main reason why we worked on this new release. With the Kubernetes 1.21 release, it became the perfect time
to start testing this module against this Kubernetes release.
Continue reading the Changelog to discover them:
Changelog
- Update Kong from version
v0.8.1
tov1.3.1
.- Updated example to make it working with the new version. Read the Breaking Change Section
- Moved container images to use our own registry.
- Kubernetes support:
- Deprecate Kubernetes 1.17 support.
- Kubernetes 1.20 is considered stable.
- Add tech-preview support to Kubernetes 1.21.
Upgrade path
To upgrade this module from v1.0.0
to v1.1.0
, you need to download this new version, then apply the
kustomize
project. No further action is required.
kustomize build katalog/kong | kubectl apply -f -
Braking changes
TL;DR
Move your annotation from:
configuration.konghq.com
->konghq.com/override
plugins.konghq.com
->konghq.com/plugins
configuration.konghq.com/protocols
->konghq.com/protocols
configuration.konghq.com/protocol
->konghq.com/protocol
configuration.konghq.com/client-cert
->konghq.com/client-cert
There are some breaking changes regarding the usage of KongIngress
resources in Services
and Ingress
.
If you were using the following annotation (as an example):
configuration.konghq.com: route-customization
You'll need to change to:
konghq.com/override: route-customization
We recommend reading the following links to better undertand how to migrate your kong annotations: