kubernetes-monitoring

Add following Contents to Cloud Providers - https://github.com/Tikam02/DevOps-Guide/tree/master/Cloud_providers

• Add basic concepts of following providers:
  • AWS
  • GCP
  • Azure
• Add tips & tricks
• Add commands

What happened:
kube-state-metrics panics and fails to start using config based on examples/standard directory, deployed to custom namespace

I0103 12:34:28.368172       1 main.go:108] Using default resources
I0103 12:34:28.368270       1 types.go:136] Using all namespace
I0103 12:34:28.368278       1 main.go:133] metric allow-denylisting: Excluding the following lists that were on de

It would be awesome if the metrics could include the node's topology.kubernetes.io/region & topology.kubernetes.io/zone (not sure what the non-AWS fields are called). That would help quickly identify patterns in the results. e.g., zone "a" is slower than zone "b" or that cross-zone traffic is what's causing a large spike in response times. Not sure if this is possible within the framework of this

Is your feature request related to a problem? Please describe.

The latest released BotKube image has a few vulnerabilities. The report can be seen at artifacthub: https://artifacthub.io/packages/helm/infracloudio/botkube?modal=security-report

Describe the solution you'd like

We should -

• Fix the image vulnerabilities
• And, add a CI check to catch such vulnerabilities early be

Same as #3319 for all Kubernetes components here the list (maybe not exhaustive):

• kube-scheduler
• kube-controller-manager
• kubelet
• kube-proxy