-
|
Expected behavior: Current behavior: the teleport server logs are generating an obscene amount of enteries Bug details:
|
Beta Was this translation helpful? Give feedback.
Answered by
ethannws
Jun 5, 2024
Replies: 3 comments 3 replies
-
|
the TKG cluster is tanzu kubernetes running on Vsphere 8 with NSX-T networking |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Hi @ethannws - I've converted your question to a discussion where you might get more eyes from the community. If you are a Teleport customer you're also welcome to open a support ticket. This is very likely a configuration error, but you haven't shared much info on your configuration. If you can add that I'm sure someone will have suggestions for you. |
Beta Was this translation helpful? Give feedback.
3 replies
-
|
my teleport config is basic just followed the quick start single node version: v3
discovery: cant see anything in here referencing the kubernetes config i just used the add resource kubernetes option and followed the steps prod-cluster-values.yaml roles: kube,app,discovery then installed with the below helm install teleport-agent teleport/teleport-kube-agent -f prod-cluster-values.yaml --version 15.4.0 --namespace teleport and using the sso:[email protected] group to authenticate Cluster Role Binding apiVersion: rbac.authorization.k8s.io/v1
Role apiVersion: rbac.authorization.k8s.io/v1
as mentioned I can auth via tsh and use kubectl and it even records my actions when i use octant to access the pods i think this is related to the teleport proxy some how.... but its hard to make head nor tail when its generating that many logs Any advice on any more information required etc please let me know thank you |
Beta Was this translation helpful? Give feedback.
-
|
just changed the role permissions on the teleport-agent role to have more access and this has now popped up in the pod logs, teleport so as normal might be DNS :L |
Beta Was this translation helpful? Give feedback.
-
|
i think i have found the issue. for some reason teleport is trying to use the default dns suffix for kubenetes which is cluster.local tkg does not use this base domain it uses the below - i wonder if its possible to change the base domain for the proxy/agent? cat /etc/resolv.conf |
Beta Was this translation helpful? Give feedback.
-
|
issue was that TKG does not use cluster.local as a domain, updated kube-dns as per below in case anybody else gets this. im getting cert errors now on some services but thats not related to this. apiVersion: v1 |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
ethannws
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
issue was that TKG does not use cluster.local as a domain, updated kube-dns as per below in case anybody else gets this. im getting cert errors now on some services but thats not related to this.
apiVersion: v1
data:
Corefile: |
.:53 {
errors
health {
lameduck 5s
}
ready
kubernetes cluster.local tanzukubernetescluster.local in-addr.arpa ip6.arpa {
pods insecure
fallthrough in-addr.arpa ip6.arpa
ttl 30
}
prometheus :9153
forward . /etc/resolv.conf {
max_concurrent 1000
}
cache 30
loop
reload
loadbalance
}
kind: ConfigMap
metadata:
creationTimestamp: "2024-05-29T20:29:29Z"
name: coredns
namespace: kube-system
resourceVersion: "2346516"
uid: