Bump kas to v14.3.3 on gprd for v14.3 release
Production Change
Change Summary
Follow up for gitlab-com/gl-infra/k8s-workloads/gitlab-com!1231 (merged), gitlab-com/gl-infra/k8s-workloads/gitlab-com!1237 (merged), gitlab-com/gl-infra/k8s-workloads/gitlab-com!1249 (merged) to bump kas
to v14.3.3 on gprd for %14.3 release.
Change Details
- Services Impacted - ServiceKAS
- Change Technician - @devin
- Change Reviewer - @devin
- Time tracking - ~37 minutes
- Downtime Component - 0
Detailed steps for the change
Pre-Change Steps - steps to be completed before execution of the change
Estimated Time to Complete (mins) - 1
-
Set label changein-progress on this issue
Change Steps - steps to take to execute the change
Estimated Time to Complete (mins) - 1
Post-Change Steps - steps to take to verify the change
Estimated Time to Complete (mins) - 30
-
Monitor the dashboard for any abnormal behavior
Rollback
Rollback steps - steps to be taken in the event of a need to rollback this change
Estimated Time to Complete (mins) - 5
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: More/bigger than usual error spikes. Some spikes are possible (#5561 (closed)), mostly due to gitlab-org/cluster-integration/gitlab-agent#157 (closed), which is not fixed yet. However, this version should generate significantly fewer errors.
Summary of infrastructure changes
-
Does this change introduce new compute instances? - No -
Does this change re-size any existing compute instances? - No -
Does this change introduce any additional usage of tooling like Elastic Search, CDNs, Cloudflare, etc? - No
Changes checklist
-
This issue has a criticality label (e.g. C1, C2, C3, C4) and a change-type label (e.g. changeunscheduled, changescheduled) based on the Change Management Criticalities. -
This issue has the change technician as the assignee. -
Pre-Change, Change, Post-Change, and Rollback steps and have been filled out and reviewed. -
This Change Issue is linked to the appropriate Issue and/or Epic -
Necessary approvals have been completed based on the Change Management Workflow. -
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. -
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.