feat: Create support an external addons #2701
Closed
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.
Description
In this new functionality the idea is
we have the possibility to install external/additional addons, that is, the addons that are not installable by the
aws_eks_addon
resource.Motivation and Context
Currently there are components/addons that are ideal for a functional installation of an EKS Cluster, at least to have a good functioning and that it is possible to implement applications without great complexities.
We have examples of addons that fulfill this role: Cluster Autoscaler, Metric Server, AWS Load Balancer Controller, etc.
In this way, the creation of additional/external addons opens the possibility of implementing several others (currently we contemplate only Cluster Autoscaler).
Breaking Changes
NDA
How Has This Been Tested?
examples/*
to demonstrate and validate my change(s)examples/*
projectspre-commit run -a
on my pull requestMentions
@snifbr - Great technical support and amazing conversartion <3