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.

Sign up for GitHub

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

Jump to bottom

ExternalName Service - all pods wrongly are assigned to it in the UI #113

Open

vliska opened this issue Jul 25, 2024 · 1 comment · May be fixed by #142

vliska commented Jul 25, 2024 •

edited

Loading

Following service (that has actually zero pod in the namespace, it's just DNS entry causes UI to have a LOT of pods under it.

apiVersion: v1
kind: Service
metadata:
  name: reverse-proxy
  namespace: <ns>
spec:
  externalName: <some service in other namespace>
  type: ExternalName

Is it possible that it takes ALL pods if it does not find selector?

version: v0.4.2

The text was updated successfully, but these errors were encountered:

georgek mentioned this issue

ExternalName services showing all pods #136

Closed

ruifung commented Dec 16, 2024

Seems like it, it's not just ExternalName services. Any selectorless service (for example, using endpoints) also shows all pods.

holysoles linked a pull request

that will close this issue

fix: services without selector return all cluster pods #142

Open

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment