headless service, why? #1924
Unanswered
str11ngfello
asked this question in
Q&A
Replies: 1 comment 1 reply
-
@str11ngfello You are likely using a persistent volume in your deployment, right? So it's deployed as StatefulSet which requires a headless service as described here: https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#limitations PS: Slack channel is over here: https://slack.loft.sh/ |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm not sure if there's a discord server for the devspace community (or slack group?) so I thought a discussion might be fine.
I understand devspace is creating a "-headless" service for each of my services. But, I don't really know what I'd use it for. If I move my team over to devspace, which is my goal, they will be like, why do all of our 20 services have 20 headless versions. Can someone tell me why it's doing this by default and perhaps a way to disable this functionality if it's not necessary?
Thank you!
Beta Was this translation helpful? Give feedback.
All reactions