Add support to create new base toolkit image, to package up commonly use tools such as awscli, jq etc. #554
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #, if available:
Description of changes:
In this PR, we add support to create a new github workflow that helps generate new container images per latest version of k8s.
It is a helper workflow that packages up commonly used tools for creating / interacting with EKS clusters, such as jq, awscli, kubectl etc.
Heavily inspired by: https://github.com/alpine-docker/k8s/tree/master
But modernized to rely on github actions, instead of CircleCI.
This change would provide us greater control over the base image so we can release changes on-demand.
Testing
Local repository packages contain latest released images per k8s version:
https://github.com/dheeraj-coding/kubernetes-iteration-toolkit/pkgs/container/eks-toolkit-base
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.