Travis Raines
Travis Raines
Minor note to self: I briefly thought this was mooted by the fix for https://github.com/Kong/kubernetes-ingress-controller/issues/2868, but it isn't, as this concerns the admission webhook, not the controllers. We do still...
For migration, jq can parse existing credential secrets and print a list of commands to update them: ``` kubectl get secret -A -ojson | jq -r '.items[] | select(.data.kongCredType !=...
Closed pending feedback from legal.
> Dumb question. What do we use those tokens for? Very belated response since I only saw it when I got the closure notification today: the service account that KIC...
@piotrwielgolaski-tomtom do you know what's actually causing the reconcile by reference to fail and require a second pass? Offhand I'd expect that approach _should_ work, since we shouldn't need Secrets...
Helm's CRD management system means that you need to manage them via another tool after the initial install, so I don't see much that a chart would provide beyond a...
Do you see any difference when using [the latest nightly](https://hub.docker.com/r/kong/nightly-ingress-controller/tags?page=1&ordering=last_updated) when your Secrets have the `konghq.com/credential` label (instead of the `kongCredType` field)? Other than the known (if not fully explained)...
The annotation requires 3.0 yes, and the simplified Secret loading behavior has not been released yet, hence why it requires a nightly image. Currently released versions relied on tracking references...
What's the actual conformance test that fails? Is it actually failing because the upstream traffic is sent over grpcs instead of grpc. or just because the gate is disabled? If...
@randmonkey hmm, that's annoying, I guess there's no way to tell backports from the commit data. The echo manifest lacks the `ingress.kubernetes.io/service-upstream: "true"` Service annotation necessary to trigger this. Not...