This message was deleted.
# k3s
a
This message was deleted.
s
Is the database inside kubernetes or outside kubernetes? For a database outside of kubernetes and being accessed from a deployment inside kubernetes you only need a simple service or type
ExternalName
.
Copy code
apiVersion: v1
kind: Service
metadata:
  name: mysql
spec:
  type: ExternalName
  externalName: mysql001.lan
c
it's outside, just running on docker
it's working now. but I'm still not able to ping the k8s cluster ip from inside k3s. however the actual address replies ping correctly When the pod access db, it does it at a slow pace.
s
When the pod access db, it does it at a slow pace.
That is interesting. I had recently added an
Ingress
, using Traefik in my K3s (v1.23.8+k3s1) cluster, which was to a
Service
that was just an
ExternalName
to a web server I have elsewhere in a private subnet - this was just to add TLS security to this web service and publicly expose it. The public end runs terribly slowly, often with 10 second pauses between HTTPS calls. I haven't had time to investigate further, but it is an interesting coincidence that you are experiencing slow access to external systems using an
ExternalName
type of
Service
.
c
so my case is not the only one! all the external services are slow. can't ping them. but they are 🥱 😴 working. my colleague decided to try setup the same using microk8s to see if the result is similar or different