-
Notifications
You must be signed in to change notification settings - Fork 588
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kubectl exec and logs not working. #36
Comments
@sangeethah In DO hostnames are not resolvable so kubeapi will not be able to reach the node by hostname, it will cause exec/logs to fail, to solve this you can just specify the following extra arguments for kubeapi service:
|
rke version v0.0.4-dev Steps to reproduce the problem: used the following extra_args for kube-api service:
Create a cluster using hosts from Digitial Ocean provider. |
Reopening this issue to support the case where when the advertised_hostname provided is not resolvable there should be no need for user to manually override the default order for kube-api service by providing kubelet-preferred-address-types |
rke version v0.0.6-dev Following configurations works fine:
nodes get registered with the "hostname_override" value. There was no extra parameters that were set for kubeapi service:
|
rke version v0.0.3-dev
Steps to reproduce the problem:
Create a cluster using hosts from Digitial Ocean provider.
Create user pods.
kubectl exec and logs do not work.
The text was updated successfully, but these errors were encountered: