This repository has been archived by the owner on Dec 15, 2021. It is now read-only.
Add Kong as supported Ingress Controller. Minor fixes. #687
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
andresmgot
changed the title
|
LGTM. HTTP trigger is getting better and interesting. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue Ref: #645
Description:
This PR includes Kong as a supported Ingress controller and fixes the annotations for the existing Nginx Ingress controller. Since version 0.9 for the Nginx ingress annotation should contain the prefix
nginx.. See:https://github.com/kubernetes/ingress-nginx/blob/master/docs/examples/auth/basic/README.md
It also removes and old version of an Nginx controller that was present in the repository and it includes extensive documentation of how to enable Kong plugins with Kubeless functions.
TODOs: