create deployment kubevpn-traffic-manager pending

[kilawang]

Hi

I download v 2.2.9 kubevpn client
and connect my GKE cluster
But the status always pending create deployment

Than I check deployment status , always 0 pod
It looks like the pod cannot be created

I use Macbook pro
Cluster Version is 1.27.12-gke.1115000
Clinet is Kubevpn v2.2.9

[wencaiwulue]

@kilawang can you show apiserver log? maybe pod is blocked by some webhook.

[kilawang]

@wencaiwulue Thank you for your suggestion. I checked the GKE log.
There is a message that the quota is insufficient.

But I don’t know what quota settings are needed
I tried adjusting the nodes from 3 to 6 but the problem is still not solved so it shouldn't be a resource issue

[wencaiwulue]

Got it you can use this command to remove priorityClassName from deploy

kubectl patch deployment kubevpn-traffic-manager
 -p '{"spec":{"template":{"spec":{"priorityClassName":null}}}}'

[kilawang]

@wencaiwulue Thank you, It's work
Pod has been created

[wencaiwulue]

@wencaiwulue Thank you for your suggestion. I checked the GKE log. There is a message that the quota is insufficient.

But I don’t know what quota settings are needed I tried adjusting the nodes from 3 to 6 but the problem is still not solved so it shouldn't be a resource issue

You can try to edit resourcequota, increase quota

kubectl describe resourcequota 

[kilawang]

@wencaiwulue
Hello, I would like to confirm whether the option to remove this setting parameter can be added in future updates to the settings, or whether it can be listed as optional. Thank you.

Because we currently manage about 19 clusters, and they all need to be manually patched during installation.
This seems unavoidable on GKE

[wencaiwulue]

@wencaiwulue Hello, I would like to confirm whether the option to remove this setting parameter can be added in future updates to the settings, or whether it can be listed as optional. Thank you.

Because we currently manage about 19 clusters, and they all need to be manually patched during installation. This seems unavoidable on GKE

Yes，i will remove this setting parameter in v2.2.10. do worry about it

[wencaiwulue]

@kilawang already released v2.2.10, you can use command kubevpn upgrade to have a try ~

[kilawang]

@wencaiwulue Thank you, I upgrade and try it,It's work very well