How do I disable kubernetes auto-discovery?

[PeterGrace]

When I added my EKS cluster to the teleport instance I neglected to notice it having "auto-discovery" enabled. Due to the workload in this cluster, I now have hundreds of services listed that I didn't intend to create!

I tried editing the configmap on the destination cluster and re-starting the teleport agent, however when it came back up the configmap was reverted to 'enabled: true'

If possible, can you link me where in the public docs this is answered? I feel like there's not a lot of discoverable documentation on managing resources after they are created.

Thanks!

[stevenGravy]

When you configure the roles in the values.yaml update to only kube. Be default it includes kube,app,discovery.

roles: kube

[PeterGrace]

@stevenGravy

  $   kubectl exec -ti deployment/teleport-auth -- tctl get discovery_config
[]

Using your hint here about discovery_config I see there's a page about configuring application discovery which seems to indicate I should be able to edit the configmap to turn it off, but as I mention when I edit it, it reverted back to enabled: true within a few seconds.

[stevenGravy]

If you did a individual add I would just remove that kubeagent install in the namespace.

[PeterGrace]

If you did a individual add I would just remove that kubeagent install in the namespace.

I don't want to remove access to the cluster, I just want to disable autodiscovery. Is this not possible?

[stevenGravy]

You should be able to set the Teleport config to turn off discovery and app service. You have to edit in the kube agent config map.

[PeterGrace]

Thanks @stevenGravy, It was, as you said, that roles setting in the helm values. I had forgotten that I'd added the teleport agent to our argocd instance (it was a long day yesterday) and so every time I tried to edit the configmap, argocd was changing it back.