Override k8s version for k3d
General MR
Summary
This allows for overriding the K3S tag in K3D to be able to use a different K8S version. This is occasionally something required when trying to reproduce an error or even test on a future version of K8S (K3D determines which version of K3S they want to use).
Relevant logs/screenshots
N/A
Merge request reports
Activity
added statusdoing label
requested review from @echuang, @kevin.wilder, @LynnStill, @micah.nagel, @ryan.j.garcia, @ronwebb, @ryan.thompson.44, and @rob.ferguson
assigned to @danny-radiusmethod
added kinddocs label
added 5 commits
-
ac9cceed...e7a20588 - 4 commits from branch
master
- e4e3902a - override k8s version for k3d
-
ac9cceed...e7a20588 - 4 commits from branch
- Resolved by Micah Nagel
When adding a new env variable configuration option we should update the script documentation
docs/developer/aws-k3d-script.md
in the "To use a different AWS profile, VPC, or AMI" section.
added 1 commit
- f4903e52 - updating instructions with new image tag feature
removed statusdoing label
added statusreview label
added 6 commits
-
f4903e52...a939d458 - 4 commits from branch
master
- a0bd1a40 - override k8s version for k3d
- 1ee633a7 - updating instructions with new image tag feature
-
f4903e52...a939d458 - 4 commits from branch
- Automatically resolved by Danny Gershman
- Automatically resolved by Danny Gershman
- Automatically resolved by Danny Gershman
- Resolved by Micah Nagel
- Resolved by Micah Nagel
mentioned in commit e25f28d3
mentioned in issue #1480 (closed)
#1480 (closed) was opened to deal with the K8S / Kubectl version parity issue you raised.
Edited by Danny Gershman