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

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

Open
vliska opened this issue Jul 25, 2024 · 0 comments
Open

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

vliska opened this issue Jul 25, 2024 · 0 comments

Comments

@vliska
Copy link

vliska commented Jul 25, 2024

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

image

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

version: v0.4.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant