nfs-ganesha-server-and-external-provisioner
nfs-ganesha-server-and-external-provisioner copied to clipboard
failed to provision volume with StorageClass "nfs": error getting NFS server IP for volume
When I create pvc use nfs sc and I got an error .
It's my config:
# Default values for nfs-provisioner.
# This is a YAML-formatted file.
# Declare variables to be passed into your templates.
replicaCount: 3
# imagePullSecrets:
image:
repository: leaderjs/nfs-provisioner
tag: v3.0.0
# digest:
pullPolicy: IfNotPresent
# For a list of available arguments
# Please see https://github.com/kubernetes-incubator/external-storage/blob/HEAD/nfs/docs/deployment.md#arguments
extraArgs: {}
# device-based-fsids: false
# grace-period: 0
service:
type: ClusterIP
nfsPort: 2049
nlockmgrPort: 32803
mountdPort: 20048
rquotadPort: 875
rpcbindPort: 111
statdPort: 662
# nfsNodePort:
# nlockmgrNodePort:
# mountdNodePort:
# rquotadNodePort:
# rpcbindNodePort:
# statdNodePort:
# clusterIP:
externalIPs: []
persistence:
enabled: true
## Persistent Volume Storage Class
## If defined, storageClassName: <storageClass>
## If set to "-", storageClassName: "", which disables dynamic provisioning
## If undefined (the default) or set to null, no storageClassName spec is
## set, choosing the default provisioner. (gp2 on AWS, standard on
## GKE, AWS & OpenStack)
##
storageClass: "local-path"
accessMode: ReadWriteOnce
size: 5Gi
## For creating the StorageClass automatically:
storageClass:
create: true
## Set a provisioner name. If unset, a name will be generated.
# provisionerName:
## Set StorageClass as the default StorageClass
## Ignored if storageClass.create is false
defaultClass: false
## Set a StorageClass name
## Ignored if storageClass.create is false
name: nfs
# set to null to prevent expansion
allowVolumeExpansion: true
## StorageClass parameters
parameters: {}
mountOptions:
- vers=3
## ReclaimPolicy field of the class, which can be either Delete or Retain
reclaimPolicy: Delete
## For RBAC support:
rbac:
create: true
## Ignored if rbac.create is true
##
serviceAccountName: default
## For creating the PriorityClass automatically:
priorityClass:
## Enable creation of a PriorityClass resource for this nfs-server-provisioner instance
create: false
## Set a PriorityClass name to override the default name
name: ""
## PriorityClass value. The higher the value, the higher the scheduling priority
value: 5
resources: {}
# limits:
# cpu: 100m
# memory: 128Mi
# requests:
# cpu: 100m
# memory: 128Mi
nodeSelector: {}
I got error
failed to provision volume with StorageClass "nfs": error getting NFS server IP for volume: service SERVICE_NAME=nfs-ser-27ft24-nfs-server-provisioner is not valid; check that it has for ports map[{111 TCP}:true {111 UDP}:true {662 TCP}:true {662 UDP}:true {875 TCP}:true {875 UDP}:true {2049 TCP}:true {2049 UDP}:true {20048 TCP}:true {20048 UDP}:true {32803 TCP}:true {32803 UDP}:true] exactly one endpoint, this pod's IP POD_IP=10.100.160.74
failed to provision volume with StorageClass "nfs": error getting NFS server IP for volume: service SERVICE_NAME=nfs-ser-27ft24-nfs-server-provisioner is not valid; check that it has for ports map[{111 TCP}:true {111 UDP}:true {662 TCP}:true {662 UDP}:true {875 TCP}:true {875 UDP}:true {2049 TCP}:true {2049 UDP}:true {20048 TCP}:true {20048 UDP}:true {32803 TCP}:true {32803 UDP}:true] exactly one endpoint, this pod's IP POD_IP=10.100.68.163
failed to provision volume with StorageClass "nfs": error getting NFS server IP for volume: service SERVICE_NAME=nfs-ser-27ft24-nfs-server-provisioner is not valid; check that it has for ports map[{111 TCP}:true {111 UDP}:true {662 TCP}:true {662 UDP}:true {875 TCP}:true {875 UDP}:true {2049 TCP}:true {2049 UDP}:true {20048 TCP}:true {20048 UDP}:true {32803 TCP}:true {32803 UDP}:true] exactly one endpoint, this pod's IP POD_IP=10.100.85.9
if I set replicaCount is 1, that's fine
How can I fix this?