Open ben851 opened 1 year ago
Waiting on the evicted pods investigation before pursuing with this, as upgrading would destroy/recreate all pods and lose investigation traces.
Staging at 1.26, prod needs to be upgraded
Potentially upgrading production today or tomorrow.
Blocked until we deploy the DNS propagation.
Upon further inspection, staging was only at 1.25. Submitted PR for staging and prod to 1.26.
K8s in staging up to 1.26 smoke test is smoking, logs are logging.
K8s 1.26 in prod
1.27 working in scratch, will PR next week
PR for staging created
Steve will QA this morning
QA'd everything looks good in staging
Moving from "Done" to "Prioritized" since we haven't pushed to prod yet.
K8s 1.27 release to production this morning. We are up to date!
Description
As a developer/operator of GC Notify, I would like my infrastructure to be up to date with EKS versions so that we are never racing against the clock to upgrade our systems before their versions are deprecated.
WHY are we building?
Being several versions ahead of the minimum version will allow us to stay ahead of security patching, features, and prevent situations where we need to upgrade our cluster extremely quickly.
WHAT are we building?
Upgrade the scratch, staging, and production K8s clusters to
VALUE created by our solution
More secure, better reliability, the elimination of tech debt.
Acceptance Criteria
QA Steps