We have a use case where we're provisioning a separate AWS NLB for konnectivity connections to live alongside the AWS NLB for TCP kube-apiserver pods. We do this facilitate some local automation. Currently the konnectivity parameters are loaded from extraArgs and then overridden by hard-coded defaults.
We have a use case where we're provisioning a separate AWS NLB for konnectivity connections to live alongside the AWS NLB for TCP kube-apiserver pods. We do this facilitate some local automation. Currently the konnectivity parameters are loaded from
extraArgs
and then overridden by hard-coded defaults.