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

feat: exclude controller to admin comms from mesh #913

Merged
merged 1 commit into from
Oct 24, 2023
Merged

feat: exclude controller to admin comms from mesh #913

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
9 changes: 9 additions & 0 deletions charts/ingress/CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,14 @@
# Changelog

## Unreleased

### Improvements

- Controller Pods now include annotations to exempt the gateway admin API port
from Kuma and Istio mesh interception. Controller to admin API configuration
uses its own mTLS configuration, which is not compatible with mesh mTLS.
[#913](https://github.com/Kong/charts/pull/913)

## 0.7.0

- Bumped dependency `kong/kong` minimum to `2.28.1`. Review the [kong chart
Expand Down
8 changes: 8 additions & 0 deletions charts/ingress/values.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,14 @@ controller:
enabled: true
generateAdminApiService: true

podAnnotations:
kuma.io/gateway: enabled
# This port must match your Kong admin API port. 8444 is the default.
# If you set gateway.admin.tls.containerPort, change these annotations
# to use that value.
traffic.kuma.io/exclude-outbound-ports: "8444"
traffic.sidecar.istio.io/excludeOutboundPorts: "8444"

gateway:
enabled: true
deployment:
Expand Down
Loading