This message was deleted.
# supports
Slackbot
06/30/2022, 5:15 PMThis message was deleted.
✅ 1
p
Prashant Shahi
06/30/2022, 5:17 PMHey Blake!
Did you follow the upgrade guide below?
https://signoz.io/docs/operate/kubernetes/#upgrade
b
Blake Romano
06/30/2022, 5:19 PMWe deploy helm charts through a spinnaker pipeline
Blake Romano
06/30/2022, 5:19 PMSo it automatically grabbed the new helm chart with the helm upgrade command such
Blake Romano
06/30/2022, 5:20 PMI can grab the deployment for otel if you want
Blake Romano
06/30/2022, 5:20 PMconfig map etc;
Blake Romano
06/30/2022, 5:24 PMI think it actually self resolved after a bit
Blake Romano
06/30/2022, 5:24 PMIt restarted a few times then started stabilizing
p
Prashant Shahi
06/30/2022, 5:25 PMOh, I see! Thanks for the report.
Prashant Shahi
06/30/2022, 5:26 PM@Srikanth Chekuri @Vishal Sharma we should investigate this to handle it better.
Prashant Shahi
06/30/2022, 5:27 PM@Blake Romano It is likely caused by intermediate state with part of the SigNoz cluster being ready, while rest are not up properly... which is eventually resolved.
Prashant Shahi
06/30/2022, 5:28 PMAlso to be noted that for 0.9, we should run the migration scripts:
https://signoz.io/docs/operate/migration/upgrade-0.9/
b
Blake Romano
06/30/2022, 5:29 PMMakes sense. I probably should have read that before lol
p
Prashant Shahi
06/30/2022, 5:33 PMno worries.. You can run the scripts anytime after upgrading.. xD
we have taken that into consideration ;)
b
Blake Romano
06/30/2022, 5:33 PMhaha I appreciate you looking out for us reckless folks 😉
p
Prashant Shahi
06/30/2022, 5:35 PMbeen there; done that;
😂
😛 2
8 Views