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
Consumers created via Kong Administrative API are deleted #105
Comments
Hello @nHurD, Thank you for opening this issue. Currently, all the entities in Kong are managed by the Ingress Controller, meaning any entity which doesn't have an associated object in k8s object store, will be remove by the ingress controller. You can currently create Having said that, in future, consumers and other entities in Kong created manually will not be deleted by Ingress Controller. This is currently not possible as the entities created by Ingress Controller and those created directly via Admin API of Kong cannot be differentiated, making the syncing of entities from k8s to Kong a challenge. This will solved once Kong includes a feature to tag or label entities. |
@hbagdi Can I ask another question? Can Kong Ingress Controller sync entities from K8s to Kong automatically now? Do I have to create Kong entities by yaml manually? Actually I want to add services to K8s manually and Ingress Controller can sync these resources to Kong automatically. |
Sure :)
That is primarily what this controller does. You create resources (like services, ingress rules) in k8s and the ingress controller syncs all those resources to Kong.
Yes, you'll need to create the entities in k8s. You can automate it, it doesn't have to be manually. Please refer to our getting started guide for a better understanding. |
Hello Is there any news about this issue? It has been closed but being bound to statically, YML-declared consumers is still problematic in production use cases For instance, we may have a service that calls the kong API in order to create kong consumers dynamically (upon app user creation for instance). This behavior cannot work using kong-ingress-controller because the periodic sync will delete all of these entries What kind of workaround would you suggest? Would calling the Kunernetes API from the user creation code in order to create a KongConsumer entry be considered a good practice? |
I totally get this point and this is an issue that we are going to solve in the next couple of releases.
This is the only work around that exists to get around this problem (Kong Enterprise users can use workspace feature to get around this problem). How are we going to solve this in the upcoming releases? We developed tagging feature in Kong 1.1 specifically to solve this problem. In the future releases of the Ingress Controller, all the entities created by the Ingress Controller will be tagged and it won't manage all entities in Kong. Please stay tuned and follow #246 for updates! |
NOTE: GitHub issues are reserved for bug reports only.
For anything else, please join the conversation
in Kong Nation https://discuss.konghq.com/c/kubernetes.
Summary
Consumers that are created using the administrative API are deleted after a period of time.
Kong Ingress controller version 0.1.0
Kubernetes version
Client Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.2", GitCommit:"bb9ffb1654d4a729bb4cec18ff088eacc153c239", GitTreeState:"clean", BuildDate:"2018-08-08T16:31:10Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.3", GitCommit:"2bba0127d85d5a46ab4b778548be28623b32d0b0", GitTreeState:"clean", BuildDate:"2018-05-21T09:05:37Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Environment
uname -a
): 4.4.121-k8sWhat happened
Consumers that were created via a direct integration to the Kong admin interface are removed after a couple of minutes
Expected behvaior
Consumers created from the administrative interface to not be removed
Steps To Reproduce
The text was updated successfully, but these errors were encountered: