Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ASM CLI upgrade from 1.22.4-0 to 1.23.2-2 breaks functionality #1634

Open
eric-aops opened this issue Oct 15, 2024 · 0 comments
Open

ASM CLI upgrade from 1.22.4-0 to 1.23.2-2 breaks functionality #1634

eric-aops opened this issue Oct 15, 2024 · 0 comments

Comments

@eric-aops
Copy link

Hi,

Apologies if this isn't the right place to post, would appreciate a redirect if it is.

I've done a lot of upgrades using asmcli already but this one has me stumped. I don't know what I'm missing but upgrading from 1.22.4-0 to 1.23.2-2 breaks the functionality within the cluster.

After running

./asmcli install --project_id das-cld-apps-dev --cluster_name apps-dev-gke01 --cluster_location asia-southeast1-a --output_dir /home/eric/asmupgrade --enable_gcp_components --ca mesh_ca --enable_all --co operator-overlay.yaml --verbose

and relabeling the namespace to use the new version 1.23.2-2 I restart an/all applications in said namespace and they all come back with the error that the health check fails as per below:

  Warning  Unhealthy  58s                 kubelet            Startup probe failed: Get "http://10.213.193.116:15021/healthz/ready": dial tcp 10.213.193.116:15021: connect: connection refused
  Warning  Unhealthy  43s (x15 over 56s)  kubelet            Startup probe failed: HTTP probe failed with statuscode: 503

Running on Server Version: v1.30.3-gke.1969002

Reverting to the previous version through namespace label and restart of apps solves it.

Thanks for any assistance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant