Skip to content
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

feat: Add prometheus-adapter port 6443 to recommended sec groups #2399

Conversation

adinhodovic
Copy link
Contributor

@adinhodovic adinhodovic commented Jan 16, 2023

Description

I wonder if kubernetes-sigs/prometheus-adapter can be added to the default recommended security groups.

When deployed with kube-prometheus/kube-prometheus-stack/helm/manifests it uses port 6443.

Thinking if metrics-server could be added by default so can prometheus-adapter.

Motivation and Context

To have the Kubernetes aggregated API v1beta1.metrics.k8s.io/default available by default if using the prom-adapter.

Breaking Changes

None

How Has This Been Tested?

  • [] I have updated at least one of the examples/* to demonstrate and validate my change(s)
  • [] I have tested and validated these changes using one or more of the provided examples/* projects

adinhodovic and others added 2 commits January 16, 2023 12:41
I wonder if [kubernetes-sigs/prometheus-adapter](https://github.com/kubernetes-sigs/prometheus-adapter) can be added to the default recommended security groups.

When deployed with kube-prometheus/kube-prometheus-stack/helm/manifests it uses port 6443.

Thinking if metrics-server could be added by default so can prometheus-adapter
@bryantbiggs bryantbiggs merged commit 059dc0c into terraform-aws-modules:master Jan 28, 2023
antonbabenko pushed a commit that referenced this pull request Jan 28, 2023
## [19.6.0](v19.5.1...v19.6.0) (2023-01-28)

### Features

* Add prometheus-adapter port 6443 to recommended sec groups ([#2399](#2399)) ([059dc0c](059dc0c))
@antonbabenko
Copy link
Member

This PR is included in version 19.6.0 🎉

@b-a-t
Copy link

b-a-t commented Feb 2, 2023

I used to add precisely the same rule for KEDA, another metrics server(among other things). not sure if it's worth mentioning in the comments(and docs?) that it's not only prometheus-adaptor but also KEDA which are both covered by the same ingress rule.
Why is Kubernetes unable to get metrics from KEDA? | Amazon Elastic Kubernetes Service (EKS)

b-a-t added a commit to b-a-t/keda-docs that referenced this pull request Feb 2, 2023
terraform-aws-modules/terraform-aws-eks#2399 eliminated the need of adding additional rule to security groups.

Signed-off-by: Timur Bakeyev <timur@bat.consulting>
JorTurFer pushed a commit to kedacore/keda-docs that referenced this pull request Feb 2, 2023
terraform-aws-modules/terraform-aws-eks#2399 eliminated the need of adding additional rule to security groups.

Signed-off-by: Timur Bakeyev <timur@bat.consulting>
@bryantbiggs
Copy link
Member

yes, that would be great to add a note on if you want to submit a PR

@github-actions
Copy link

github-actions bot commented Mar 5, 2023

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 5, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants