-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create a second Node Group on EKS to host Prometheus #2979
Labels
Comments
sablumiah
changed the title
Create a second Node Group on EKS for host Prometheus
Create a second Node Group on EKS to host Prometheus
Jun 17, 2021
until we do this, we'll only be able to cope with say 5 environments, or we'll hit Prometheus's resource limit |
vijay-veeranki
added a commit
to ministryofjustice/cloud-platform-infrastructure
that referenced
this issue
Aug 25, 2021
vijay-veeranki
added a commit
to ministryofjustice/cloud-platform-infrastructure
that referenced
this issue
Aug 26, 2021
* Create a second Node Group with 2 nodes on EKS for monitoring * Update max_capacity as 3 for monitoring_ng * Moved cluster related locals to cluster.tf * Moved locals to cluster.tf * Moved userdata to templates This is related to: ministryofjustice/cloud-platform#2979 Co-authored-by: Alejandro Garrido Mota <[email protected]>
2nd node group created, running the Prometheus instance for EKS it is applied to both Live and manager cluster. This change, needs live-1 monitoring tag updated to use the latest monitoring module, will raise a separate ticket for it. |
Issue created for kops |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What:
We need to add a second node group on EKS to be used exclusively by prometheus due to the application using up a lot/most of the resources of a given node and causing issues for other pods on the node.
Why:
We do this on the current KOPS cluster and found it resolves the above issues
https://github.com/ministryofjustice/cloud-platform-infrastructure/blob/68278816d7192b545416e70bbf48d5373bcdf45a/terraform/aws-accounts/cloud-platform-aws/vpc/kops/main.tf#L78
Definition of Done:
The text was updated successfully, but these errors were encountered: