2024-04-16 to 2024-04-18: Add Wiz Sensor to Prod Cluster (gitlab-3okls & gprd-us-east1-b)
Production Change
Change Summary
Wiz Runtime Sensor Readiness Review
Change Summary
A lightweight eBPF-based agent name Wiz Runtime Sensor would be deployed to the environment. This agent hooks eBPF probes and detects malicious actions on the workload.
Making it a c3 change as the service has CPU and Memory limits defined, it would be OOM killed if more resources are being utilized.
We do not have more security-related insights for the Kubernetes clusters and workloads. Recently we have tested the Wiz Runtime Sensor, which gives us more visibility into the suspicious actions under the Kubernetes environment.
It is already deployed in the Pre
environment. We can review the MR that is deployed in Pre
.
Deployed in a Staging
environment, related change management issue
Deployed in the ops-central
cluster, related change management issue
Deployed in the ops-gitlab-gke
cluster, related change management issue
Change Details
-
Services Impacted -
gitlab-3okls
&gprd-us-east1-b
clusters -
Change Technician -
@ugovindia
- Change Reviewer - @pguinoiseau
- Time tracking - 30 minutes
- Downtime Component - none
Set Maintenance Mode in GitLab
If your change involves scheduled maintenance, add a step to set and unset maintenance mode per our runbooks. This will make sure SLA calculations adjust for the maintenance period.
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 the MR for gitlab-3okls
cluster (16th April) -
Merge the MR for gprd-us-east1-b
cluster (18th April) -
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) - 30 minutes
-
Revert the MR for gitlab-3okls
cluster -
Revert the MR for gprd-us-east1-b
cluster -
Set label changeaborted /label ~change::aborted
Monitoring
Key metrics to observe
- Metric: Node Schedule Waiting Time
-
Location:
Once Wiz Sensor is enabled, we will start getting the graphs in the dashboard
Additionally, we would monitor the
node_schedstat_waiting_seconds_total
as there was a spike earlier when we did it for the staging earlierAlso the Thanos queries listed here would assist with the monitoring
-
What changes to this metric should prompt a rollback:
If
node_schedstat_waiting_seconds_total
is too high, we will go ahead and revert the update.
-
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.
- The change window has been agreed with Release Managers in advance of the change. If the change is planned for APAC hours, this issue has an agreed pre-change approval.
- The labels blocks deployments and/or blocks feature-flags are applied as necessary.
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.
- The change execution window respects the Production Change Lock periods.
- For C1 and C2 change issues, the change event is added to the GitLab Production calendar.
- 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.) - For C1 and C2 change issues, the SRE on-call provided approval with the eoc_approved label on the issue.
- For C1 and C2 change issues, the Infrastructure Manager provided approval with the manager_approved label on the issue.
- Release managers have been informed prior to any C1, C2, or blocks deployments 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.