The controller performs the same function in both DB-backed and DB-less modes, and is recommended for Kubernetes deployments of either. The exact interaction with the admin API changes, but that’s a transparent implementation detail.
DB-less mode is considered production-ready; which issue are you referring to? I wasn’t able to find anything that looked relevant in a search. Bugs do crop up with either mode-- please report an issue if you find something that looks bugged and isn’t already reported.
https://github.com/Kong/kubernetes-ingress-controller/issues/735 may affect you here if you use a custom Ingress class–that problem generally affects any resource that shouldn’t require an Ingress class (in the case of a credential, because it’s loaded via its attached KongConsumer, which does require
ingress.class annotations when using non-default classes (
kong or no class annotation are accepted if you do not override the default). We are working on a fix for that, but if you’re affected in the meantime you should be able to work around it by adding an
ingress.class annotation to the credential Secret. That issue will affect either mode, however, as it’s a bug in the controller.
Killing the controller containers (execing into running containers and running
kill 1) should also work, without disrupting traffic, as it will force a restart of the controller container and the new instance will see the latest credential. However, the annotation workaround is better, as it doesn’t require intervention after the initial change to add it, whereas you’d need to restart after each change to the credential value with the
The ServiceAccount issue could be an issue with Helm 2 that we’re not aware of (check the output of
helm template to see if it’s being rendered properly, or could be due to some old resource that wasn’t properly deleted. Trying to find that problem resource should fix the issue in the latter case, though it’s probably easier to choose a new name for the account to get that fixed quickly, and then search for the offending old config later at your convenience.