eks-prow-build-cluster: create simple monitoring stack

[pkprzekwas]

This PR brings simple monitoring setup for Prow EKS cluster. At some point we will replace it with sth more sophisticated (like kube-prometheus). For now, in order to debug migration of prow jobs, this is hopefully enough.

PR contains:

• dedicated monitoring namespace
• prometheus operator
• single prometheus instance (if we want to access its metrics externally we can consider switching this instance into agent mode and pushing metics to AWS Managed Prometheus instance)
• kube-state-metrics
• node-exporter
• cadvisor
• internal grafana instance (meaning that's it not exposed neither secured)

/assign @ameukam @upodroid @xmudrii
This stack has been already deployed to prow-build-cluster. Part of #4686

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: pkprzekwas / name: pprzekwas (c93edaa)

[k8s-ci-robot]

Welcome @pkprzekwas!

It looks like this is your first PR to kubernetes/k8s.io 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/k8s.io has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @pkprzekwas. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[xmudrii]

/ok-to-test

[pkprzekwas]

On top of that I've tested the AWS native Container Insights. Installation is trivial but it requires modifying terraform script in order to extend permissions of instance profiles. At the moment any modifications to EKS terraform script are blocked by #4989. Once it's merged, Container Insights can be enabled in a separate PR.

[xmudrii]

Overall this looks pretty good to me. I left some questions and comments, most of them should be just nits.

[xmudrii]

Should we expose this Grafana instance publicly? If yes, let's create a follow up issue to track that.

[pkprzekwas]

I wasn't sure if this is something that we want to maintain in a longer term. IMO we can expose it for now till we haven't figured which monitoring solution works the best for both GCP and AWS clusters.

I wonder if there were other things we want to expose over time, in which case ingress-controller would be handy.

[xmudrii]

Looks great to me!
/lgtm
/approve
/assign @ameukam
for approval

[ameukam]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ameukam, pkprzekwas, xmudrii

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• infra/aws/OWNERS [ameukam]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment