@kubernetes/sig-network-misc @kubernetes/sig-storage-misc
Would this conversation be better on stackoverflow and/or slack?
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.![]()
Closed #58792.
Hi all,
is this problem solved?? I have different set-up (running a local cluster instead of GKE) but with the same NFS configuration. I obtain the same error and it is not solved by specifying the internal DNS service name.
Any help would indeed very appreciated.
Thanks
@paolasoto88 I solved the problem by just upgrading kubectl of my GKE cluster from the version 1.7.11-gke.1 to 1.8.6-gke.0 at that time and the DNS name will be enough
--- apiVersion: v1 kind: Service metadata: name: nfs-server namespace: $namespace spec: ports: - name: nfs port: 2049 - name: mountd port: 20048 - name: rpcbind port: 111 selector: role: nfs-server --- apiVersion: v1 kind: PersistentVolume metadata: name: nfs namespace: $namespace spec: capacity: storage: ${volume}Gi accessModes: - ReadWriteMany nfs: server: nfs-server.$namespace.svc.cluster.local path: "/"
ubuntu@selfportal-ubuntu:~/tezosk8s$ kubectl version Client Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.1", GitCommit:"4ed3216f3ec431b140b1d899130a69fc671678f4", GitTreeState:"clean", BuildDate:"2018-10-05T16:46:06Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{Major:"1", Minor:"10+", GitVersion:"v1.10.9-gke.5", GitCommit:"d776b4deeb3655fa4b8f4e8e7e4651d00c5f4a98", GitTreeState:"clean", BuildDate:"2018-11-08T20:33:00Z", GoVersion:"go1.9.3b4", Compiler:"gc", Platform:"linux/amd64"}
Output: mount.nfs: Failed to resolve server nfs-service.default.svc.cluster.local: Name or service not known
Am I doing something wrong? Cuz this doesn't work for 1.10 still :(
P.S. $namespace is $volume is replaced with actual values, I'm scripting in BASH.
@paolasoto88
Were you able to solve the problem?
Why is that nodes on gke don't resolve to kube dns? that's so unreasonable. I face the same problem.
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.![]()
(Note that this is cloud provider specific, so likely doesn't make to open the issue again the Kubernetes repo).
cc: @mark-church: what is a good place for people to track GKE/GCP-related K8S issues?