Feat/eso deploy - #17
Open
Eaglewings966 wants to merge 9 commits into
Open
Eaglewings966 wants to merge 9 commits into
Eaglewings966 wants to merge 9 commits into
Conversation
…k31-ecr-setup :wq ing with '#' will be ignored, and an empty message aborts
- Added Terraform configuration for kube-prometheus-stack Helm deployment - Configured Prometheus for metrics collection - Configured Grafana for visualization - Added Alertmanager for alerting - Monitoring namespace created in dev-test-eks cluster
Deploy kube-prometheus-stack for cluster monitoring
Feat/bank23 eks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This PR implements the deployment of the External Secrets Operator (ESO) to the dev-test-eks cluster. It includes configuration for syncing AWS Secrets Manager secrets into Kubernetes using a SecretStore and ExternalSecret manifest.
Due to IRSA setup challenges and CloudFormation failures, a temporary workaround using static AWS credentials stored in a Kubernetes secret (aws-credentials) was applied to enable ESO to sync secrets.