You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rob Edward wrote: To round out the narrative we use when it comes to progressive rollout and SLI/SLO (well error budget) monitoring adding visibility in Ops Suite to support and monitor the rollout etc. Although it sounds like Cloud Deploy will expose something like this in a few months.
My idea:
can do that, just need to abstract the YAML in script 15 with 22/78% into a separate parametric yaml (maybe under templates/ )?
Once done, I could do a 17.sh script which does some timing like:
sleep 1
cat template | sed s/MYPERCENTAGE/10/g | kubectl apply
sleep 5
cat template | sed s/MYPERCENTAGE/50/g | kubectl apply
sleep 5
cat template | sed s/MYPERCENTAGE/90/g | kubectl apply
sleep 5
cat template | sed s/MYPERCENTAGE/100/g | kubectl apply
just an idea..
The text was updated successfully, but these errors were encountered:
Rob Edward wrote: To round out the narrative we use when it comes to progressive rollout and SLI/SLO (well error budget) monitoring adding visibility in Ops Suite to support and monitor the rollout etc. Although it sounds like Cloud Deploy will expose something like this in a few months.
My idea:
templates/
)?just an idea..
The text was updated successfully, but these errors were encountered: