a2c1d153da
to the API server configuration. This solves the problem where if you have non-resolvable node names, and try to scale the server by adding new nodes, kubectl commands start to fail for newly added nodes, giving a TCP timeout error when trying to resolve the node hostname against a public DNS. |
||
---|---|---|
.. | ||
manifests | ||
kubectl-kubeconfig.yaml.j2 | ||
namespace.j2 |