github-actions[bot]
commented
1 month ago This issue has been automatically marked as stale because it has been open 60 days with no activity. Remove stale label or comment or this issue will be closed in 10 days
Describe the feature
Many EKS Blueprint AddOns build using local YAML or config files. This allows build systems that are sandboxed to properly compile CDK code using these AddOns.
For some reason, the AWS Secrets Store CSI Driver AddOn, references a file over the web here. Because of this, any build system that requires builds to occur in a sandboxed environment cannot build CDK code which imports this AddOn.
Use Case
We have a hard requirement to build our CDK code in a sandboxed environment, and therefore would also require that this AddOns is built using local files only. It is very common for importing dependencies to happen "up-front" to prevent builds from depending on downloads at build time, which is less deterministic. Importing AddOn YAML or config files as dependencies that are built directly into EKS Blueprints will ensure it works in offline build systems and will also ensure stability of EKS Blueprints itself by effectively "freezing" versions of AddOns at a known working configuration.
Proposed Solution
No response
Other Information
No response
Acknowledgements
CDK version used
2.115.0
EKS Blueprints Version
1.13.1
Node.js Version
^14.18.13
Environment details (OS name and version, etc.)
AL2 for deploying CDK, bottlerocket hosts within the EKS cluster.