Cluster upgrade is stuck for more than 20 days

[hariprasadiit]

Hello,

I requested cluster, beta, upgrade to 1.32 more than 20 days back and the cluster is stuck showing upgrading. PVC resize events return 403 error now.

Please help resolve this issue asap

[hsinghal-pf9]

Hi @hariprasadiit , thanks for reaching out. Could you please share your cloudspace name and organization name.
Accordingly, we can look into it.

[hariprasadiit]

Hi @hsinghal-pf9

Org: Vizmo
Cloudspace: beta

[vjha-pf9]

Hello @hariprasadiit Thanks for your patience. The cluster upgrade issue has now been resolved. Please let us know if you’re facing any other problems.

[hariprasadiit]

Hello @vjha-pf9
Thanks for the update. Now there's another issue. for some reason, LB is not forwarding traffic to the cluster. I don't any issues with Nginx ingress deployed, inside the cluster all the services are accessible as well as over Cloudflare tunnel. Through LB, all the services are timing out

[hariprasadiit]

also, new load balancers are stuck in pending state without public IP

[hariprasadiit]

@vjha-pf9 @hsinghal-pf9 could you please support with this issue? the cluster is unusable now

[vjha-pf9]

Hello @hariprasadiit I’ve fixed this issue. Could you please check and confirm? I can see your service has been allocated the LB IPv4 address 50.56.5.209.

[hariprasadiit]

@vjha-pf9 Thanks for the help.
We're trying to upgrade our cluster to 1.35. I initiated upgrade to 1.33, 3 hours back. seems the cluster is stuck again showing upgrading. Do we need to reach out to you when we would like to upgrade our cluster to next version? or is this an issue with out cluster?

[hariprasadiit]

Hi @vjha-pf9
This issue is back now.
Cloudspace: coder

[vjha-pf9]

seems like you have deleted the cloudspace coder

[hariprasadiit]

Coder is available, it's in UK region

[vjha-pf9]

Cluster is now healthy and running with version 1.34.9. The upgrade took a bit longer than usual.