HOODAW for Components Container Images

[sj-williams]

Background

Currently we are manually tracking container image versions for all of our components in this runbook.

The process of reviewing this is covered by one of our automatically generated k8s upgrade tickets, an example of this ticket here. However this task is quite time consuming; not all of the components stipulate any cluster compatibility requirements or publish a matrix, and in some cases (ie Prometheus) require a lot of digging into the various dependencies / sub charts for release update information / changelogs.

We should figure out which of these components do publish these and find a way to either:

• integrate them into our HOODAW reporting
• define some clearer guidelines around how we address the task of keeping them up to date

Proposed user journey

Approach

Which part of the user docs does this impact

Communicate changes

• [ ] post for #cloud-platform-update
• [ ] Weeknotes item
• [ ] Show the Thing/P&A All Hands/User CoP
• [ ] Announcements channel

Questions / Assumptions

Definition of done

• [ ] readme has been updated
• [ ] user docs have been updated
• [ ] another team member has reviewed
• [ ] smoke tests are green
• [ ] prepare demo for the team

Reference

How to write good user stories