Update kas to v15.0.0 in gprd
Production Change
Change Summary
Update KAS to v15.0.0 by merging gitlab-com/gl-infra/k8s-workloads/gitlab-com!1793 (merged).
Tested CI/CD tunnel on gstg in https://staging.gitlab.com/hfyngvason-dev/agent-test/-/jobs/41010210. The presence of agent-test-configmap
also demonstrates gitops is working.
Change Details
- Services Impacted - ServiceKAS
- Change Technician - @ggillies
- Change Reviewer - @ggillies
- Time tracking - 33 minutes
- Downtime Component - None
Detailed steps for the change
Change Steps - steps to take to execute the change
Estimated Time to Complete (mins) - 30 minutes
-
Set label changein-progress /label ~change::in-progress
-
Merge gitlab-com/gl-infra/k8s-workloads/gitlab-com!1793 (merged) -
Monitor the KAS service dashboard for anomalies -
Set label changecomplete /label ~change::complete
Rollback
Rollback steps - steps to be taken in the event of a need to rollback this change
Estimated Time to Complete (mins) - 1 minute
-
Revert gitlab-com/gl-infra/k8s-workloads/gitlab-com!1793 (merged) -
Set label changeaborted /label ~change::aborted
Monitoring
Key metrics to observe
-
Metric: kas Service Error Ratio
- Location: https://dashboards.gitlab.net/d/kas-main/kas-overview
- What changes to this metric should prompt a rollback: Error rate above the SLI threshold for over 1 minute. No errors are expected because of this rollout.
-
Metric: kas Service RPS - Requests per Second
- Location: https://dashboards.gitlab.net/d/kas-main/kas-overview
- What changes to this metric should prompt a rollback: If RPS drops to 0 and doesn't recover, then something about the change is (very) bad.
Change Reviewer checklist
-
Check if the following applies: - The scheduled day and time of execution of the change is appropriate.
- The change plan is technically accurate.
- The change plan includes estimated timing values based on previous testing.
- The change plan includes a viable rollback plan.
- The specified metrics/monitoring dashboards provide sufficient visibility for the change.
-
Check if the following applies: - The complexity of the plan is appropriate for the corresponding risk of the change. (i.e. the plan contains clear details).
- The change plan includes success measures for all steps/milestones during the execution.
- The change adequately minimizes risk within the environment/service.
- The performance implications of executing the change are well-understood and documented.
- The specified metrics/monitoring dashboards provide sufficient visibility for the change.
- If not, is it possible (or necessary) to make changes to observability platforms for added visibility?
- The change has a primary and secondary SRE with knowledge of the details available during the change window.
Change Technician checklist
-
Check if all items below are complete: - The change plan is technically accurate.
- This Change Issue is linked to the appropriate Issue and/or Epic
- Change has been tested in staging and results noted in a comment on this issue.
- A dry-run has been conducted and results noted in a comment on this issue.
- For C1 and C2 change issues, the SRE on-call has been informed prior to change being rolled out. (In #production channel, mention
@sre-oncall
and this issue and await their acknowledgement.) - Release managers have been informed (If needed! Cases include DB change) prior to change being rolled out. (In #production channel, mention
@release-managers
and this issue and await their acknowledgment.) - There are currently no active incidents that are severity1 or severity2
- If the change involves doing maintenance on a database host, an appropriate silence targeting the host(s) should be added for the duration of the change.
Edited by Graeme Gillies