Shane Utt

Results 578 comments of Shane Utt

The team has decided that we'll hold on this issue for now as we try to make some architectural changes to the KIC which will ultimately make implementing this easier.

> So does this mean, in future, kong would be able to support mTLS communication between kong service?? In this particular case: This covers mTLS between the Kubernete Ingress Controller...

Several weeks ago we [started some work on this](https://github.com/Kong/kubernetes-ingress-controller/blob/b65a21b8f19d2c8d22dbba5e99bcf0bee61d8492/railgun/keps/0001-single-kic-multi-gateway.md) but it was not finished due to a desire by the maintainers to wait until [KIC 2.0](https://github.com/Kong/kubernetes-ingress-controller/milestone/12) which will bring a...

As stated before we're still considering the potential synergy with a future KIC operator, but we're also now considering the synergy of this improvement with the advent of `Gateway` support....

Relevant to the mTLS portion of this, flags have been added as part of #1958 to provide client certs for mTLS with the Kong Gateway. The remaining portion of the...

> Hi, > > Within this KEP https://github.com/Kong/kubernetes-ingress-controller/blob/main/keps/0001-single-controller-multi-proxy.md, will the support of the hybrid mode with the dbless feature is an option ? With hybrid mode you don't generally need...

> @shaneutt thanks for you reply, and what we are hoping for is to run the hybrid mode with the dbless feature (with one ingress controller instance, one or two...

Just wanted to check in on this one because its so old: seems like it's still relevant though?

> Its something we'd like to see sooner rather that later. Is there any opposition outside contribution on this? We're happy to collaborate on design, direction and do the leg...

Thanks @esatterwhite for creating a KEP for this, which is now merged in a `provisional` state for us to continue iterating on: https://github.com/Kong/kubernetes-ingress-controller/blob/main/keps/0010-dynamic-plugin-configuration.md At this time I've discussed this effort...