Set up K8S monitoring for dev
cluster
#325
Merged
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.
Context
Set up stack to monitor the K8S cluster, worker nodes and extra K8S metrics. Add pod monitor for indexer instance.
Proposed Changes
Install
kube-prometheus
stack which gives us:Set up monitoring for pods belonging to the
indexer
running in dev cluster.This PR also creates an AWS managed prometheus along with necessary roles to interact with it. But the
remote_write
is not hooked up because, the version of operator installed does not supportSigV4
authentication. K8S cluster needs to be upgraded for us to install a newer version, and that will be done in future PRs. For now, this PR installs a grafana instance accessible locally via port forwarding that lets us make progress while we figure out how to hook up things to PL grafana.Unrelated to context: while at it, give Kyle access to interact with encrypted secrets like the rest of the team.
Tests
Deployed manually for testing.
Revert Strategy
git revert
thenterraform apply