lock cdk-addons to commits instead of branches
Bug #1877667 reported by
Kevin W Monroe
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| CDK Addons |
Fix Released
|
Undecided
|
Kevin W Monroe | ||
Bug Description
Post 1.18, we noticed that some of the images referenced in cdk-addons were updated outside of our control (e.g.: we track kube-state-metrics on the release-1.9 branch; CK 1.18.0 went out with k-s-m 1.9.5, yet 1.9.6 is the latest on that branch).
To fix this, we're locking all cdk-addons to a specific commit that coincides with our release cycle. We'll update these as-needed throughout the release.
Revision history for this message
| Kevin W Monroe (kwmonroe) wrote | #1 |
| Changed in cdk-addons: | |
| assignee: | nobody → Kevin W Monroe (kwmonroe) |
| status: | New → Fix Committed |
| milestone: | none → 1.18+ck1 |
Revision history for this message
| Kevin W Monroe (kwmonroe) wrote | #2 |
| Changed in cdk-addons: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
PR: https:/