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.

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

deploy: drop custom-server-block and use status_listen #634

Merged
merged 1 commit into from
May 1, 2020

Conversation

hbagdi
Copy link
Member

@hbagdi hbagdi commented May 1, 2020

Until Kong 1.4, there didn't exist a way to health-check kong and expose
metrics without also exposing the admin api of kong.
In kong 1.4, a new server KONG_STATUS_LISTEN was added which provides
these capabilities.

This commit removes the reliance on the custom server block that was
provided via a ConfigMap.
With 0.9, the next version of controller, the minimum version of kong
should be 1.4, hence this breaking change.

The error logs have been modified as well to include proxy error logs as
well.

@hbagdi hbagdi requested a review from rainest May 1, 2020 18:32
@hbagdi
Copy link
Member Author

hbagdi commented May 1, 2020

This should be merged after #633

Comment on lines +49 to +50
# - name: KONG_PROXY_ACCESS_LOG
# - value: /dev/stdout
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Was commenting these intentional? It looks like this is unrelated.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, this is intentional.
Users when they are getting started can use this to log proxy access logs quickly.

deploy/manifests/base/kong-ingress-dbless.yaml Outdated Show resolved Hide resolved
Until Kong 1.4, there didn't exist a way to health-check kong and expose
metrics without also exposing the admin api of kong.
In kong 1.4, a new server KONG_STATUS_LISTEN was added which provides
these capabilities.

This commit removes the reliance on the custom server block that was
provided via a ConfigMap.
With 0.9, the next version of controller, the minimum version of kong
should be 1.4, hence this breaking change.

The error logs have been modified as well to include proxy error logs as
well.
@rainest rainest self-requested a review May 1, 2020 23:16
@hbagdi hbagdi merged commit eb67373 into next May 1, 2020
@hbagdi hbagdi deleted the deploy/status-listen branch May 1, 2020 23:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants