-
Notifications
You must be signed in to change notification settings - Fork 28
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
lookup 10.96.0.1:tcp: no such host #120
lookup 10.96.0.1:tcp: no such host #120
Comments
I found the problem in csi-driver/vendor/k8s.io/client-go/rest/config.go Lines 516 to 536 in 35836e0
my variables are
|
All right, this is because I have
service in the same namespace |
I am not really a network guy, so I am missing the problem. Is there something we can do in the CSI driver? Looks like the env variable is read in the default go-client, I don't really want to mess with that. What else can we do? |
I fixed this by adding |
Fixes kubevirt/csi-driver#120 (comment) <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Introduced a new configuration option to disable service links for various Kubernetes deployments, enhancing service resolution control for the following: - Kafka - Cluster Autoscaler - CSI Controller - Cloud Controller Manager - RabbitMQ <!-- end of auto-generated comment: release notes by coderabbit.ai --> Signed-off-by: Andrei Kvapil <[email protected]>
Fixes kubevirt/csi-driver#120 (comment) <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Introduced a new configuration option to disable service links for various Kubernetes deployments, enhancing service resolution control for the following: - Kafka - Cluster Autoscaler - CSI Controller - Cloud Controller Manager - RabbitMQ <!-- end of auto-generated comment: release notes by coderabbit.ai --> Signed-off-by: Andrei Kvapil <[email protected]>
What happened:
CSI-driver can't start
What you expected to happen:
CSI-driver is running
How to reproduce it (as minimally and precisely as possible):
Additional context:
logs:
Environment:
virtctl version
): N/Akubectl version
): N/Auname -a
): N/AThe text was updated successfully, but these errors were encountered: