-
Notifications
You must be signed in to change notification settings - Fork 36
Create one Kubernetes Service per job #367
Comments
Can you elaborate on why this is happening? It looks like we could create up to three services per role right now: If the headless tag goes away, does that mean we'll always create three services for each StatefulSet, since the Edit: Three services for each public role, two for non-public. |
Also, it looks like we could determine if a service should be public or not with the |
Right now in our helm templates we have a StatefulSet per role, and that is linked to service via a
I don't see a way to link the newly named service For example, with our new |
I've been struggling to find a fix for addressing individual pods with this setup. We need to access pods for things like this: https://github.com/cloudfoundry/cf-syslog-drain-release/blob/develop/jobs/scheduler/templates/environment.sh.erb#L8 According to the Kube docs (and my testing), in order to get a hostname for a pod, the StatefulSet's Also note that a service must have ports associated with it. I initially hoped I could make a dummy service with just the instance group name, but I need ports to go along with it. What I'm looking at now is collecting all of the ports for the jobs inside the instance group, and making a service out of that. If you have any other ideas, please let me know. |
headless
tag from fissileUse the following rule to determine the service name (which in turn determines the hostname):
Ports must be exposed like this:
The text was updated successfully, but these errors were encountered: