Skip to content

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

Open
@vliska

Description

@vliska

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions