terraform-aws-eks-blueprints
terraform-aws-eks-blueprints copied to clipboard
fix: Updating to make namespace creation optional
What does this PR do?
Changes behavior of kube-prometheus-stack
to conditionally create a namespace based on parameter set in helm_config. This will allow the chart to be deployed to a pre-existing namespace.
Motivation
- Resolves #1056
More
- [x] Yes, I have tested the PR using my local account setup (Provide any test evidence report under Additional Notes)
- [ ] Yes, I have added a new example under examples to support my PR
- [ ] Yes, I have created another PR for add-ons under add-ons repo (if applicable)
- [ ] Yes, I have updated the docs for this feature
- [x] Yes, I ran
pre-commit run -a
with this PR
Note: Not all the PRs require a new example and/or doc page. In general:
- Use an existing example when possible to demonstrate a new addons usage
- A new docs page under
docs/add-ons/*
is required for new a new addon
For Moderators
- [ ] E2E Test successfully complete before merge?
@bryantbiggs could moved
be used here do handle pre-existing installations ?
@bryantbiggs could moved be used here do handle pre-existing installations ?
yes, but we would need to increase the minimum supported version for Terraform to v1.1+ which is again a breaking change
roger! thanks for clearing that up
@bryantbiggs Is there a roadmap item to move to version 5 of the module with breaking changes?
This PR has been automatically marked as stale because it has been open 30 days with no activity. Remove stale label or comment or this PR will be closed in 10 days
This is still a needed feature. When is the next breaking change?
This PR has been automatically marked as stale because it has been open 30 days with no activity. Remove stale label or comment or this PR will be closed in 10 days
thank you for the PR - this will be resolved in the new addons module https://github.com/aws-ia/terraform-aws-eks-blueprints-addons