CNCF playground deployment now reconciles its canonical manifest
cncf-playground-deploy-meshery.yamlgithub.sha before setting the release image and checking rollout status.Previously, the workflow updated only the image, leaving the live pod without PROVIDER=Meshery, so users landed on the provider chooser. At the next release deployment, PROVIDER=Meshery is applied and Meshery is pre-selected; out-of-band cluster edits are overwritten, and the workflow fails if the pod cannot come up.
Show release-note lines
- [CI] Reconcile playground Deployment env from manifest on every release @leecalcote (#19748)github.com/meshery/meshery/releases/tag/v1.0.34