Please enable JavaScript.
Coggle requires JavaScript to display documents.
Anthos Release process - Coggle Diagram
Anthos Release process
Process
Cluster Failover
deployment pattern
Dev
Deploy to failover in dev
Cool off period for tenants
to test and confirm
Remove old cluster
Confirm all is working
Prod
Notify new version available
on failover
To be decided
Comms process
Release notes
Jira
Email to tenants
Impactful vs non-impactful
Define GIt process
Observability
Report on which tenant is using each release
Service Agreement
Tenants have a responsibility to keep up to date
Agree at Customer forum
Runbook
Decide if breaking change
Follow respective release process
Blue/Green approach
Customer impacting
Agent changes
ALB
Istio
External DNS
Validate if breaking change
Inform tenants / create note to
label as breaking change
External Secrets
Anthos Canges
GKE
Tags
Create SNOW CR
Create jira 'release' grouping all
stories that are included.
Share via confluence/jira dashabord
Rolling update
No impact on app team,
no redeploy required
Datadog
Dome9
Crowdstrike
Release docs & process
Technical release
process to be defined
Create branch etc
Push change to Prod
Monitor to confirm
change is successful
Mention at customer forum
Send email to tenants with link to 'release' page
Automate creation of standard template SNOW (wait for greenfield?)
Create jira documenting change
with correct 'release label
Create confluence page or jira
dashboard listing each change
Cloudhealth
Kuberhealthy
Flux
Blue/Green Process for breaking changes
Regular cadence
Comms to tenant
Dev first & receive feedback from tenant
Batch of several breaking changes
Document impact of each change in jira
Next time :red_flag:
Define blue/green process & cadence
Do/define a trial run of a release