Client pod is always pending

I just using helm to install a consul instance in azure kubenetes, it defaully setup 4 client pods, however, they are always in pending status.
Here’s the config.yml I use(tried to change config values lot of times):
global:
name: consul
datacenter: hashidc1
logLevel: “error”

ui:
enabled: true
service:
type: ClusterIP
#loadBalancerSourceRanges:
#- 42.159.215.97
#nodePort:
# - http: 31120
# - https: 31121

#connectInject:

enabled: true

client:
enabled: true
grpc: true
affinity: null

nodeAffinity:

requiredDuringSchedulingIgnoredDuringExecution:

nodeSelectorTerms:

- matchExpressions:

- key: node-role.kubernetes.io/master

operator: DoesNotExist

#server:

replicas: 3

bootstrapExpect: 5

disruptionBudget:

enabled: true

maxUnavailable: 1

some error messages:
“0/4 nodes are available: 1 node(s) didn’t have free ports for the requested pod ports, 3 node(s) didn’t match Pod’s node affinity.”
" pod didn’t trigger scale-up: 1 node(s) didn’t match Pod’s node affinity"

Can anyone help? Thank you!

Hey @zhangjj_583

It looks like some required ports are taken up already. Do you have something else deployed that would take up consul’s ports?