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

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

Merged
merged 1 commit into from
May 1, 2020
Merged

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

merged 1 commit into from
May 1, 2020

Commits on May 1, 2020

  1. deploy: drop custom-server-block and use status_listen 

    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 committed May 1, 2020
    Configuration menu
    Copy the full SHA
    8cd2781 View commit details
    Browse the repository at this point in the history