-
Notifications
You must be signed in to change notification settings - Fork 213
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add possibility to add extra Service Selector #4660
Comments
There is a labels Map for serverPod. Please take a look at this doc. |
Hello @sankarpn . what i'm looking for is to add a map to add extra label selector on the generated service, to only select a certain pod. |
@belfo, wouldn't this mean that the service no longer selected all of the members of the cluster? From your original description, it seems like you are intending that requests for one application would go to a certain subset of the members of the cluster while requests for other applications, presumably, would go to the remaining members. If my understanding is correct, then this sounds like two different clusters. If I'm incorrect, can you please help me understand your use case better? You can have multiple clusters and this pattern would help us because scaling a particular cluster makes more sense as does our preserving application uptime during some kind of rolling activity because the operator would know what servers have to stay up to preserve the uptime of a given application. |
Hello @rjeberhard , indeed the idea is to select only 1 managed server. to have an 'active / passive' design. |
Hello,
currently it's possible to add extra label / annotation to the cluster service created by the operator: https://github.com/oracle/weblogic-kubernetes-operator/blob/main/documentation/domains/Cluster.md#cluster-service
Would be possible to add the possibility to add extra Selector?
I need to differentiate the different running app inside the cluster, and use a custom label to identify the pod.
Regards
The text was updated successfully, but these errors were encountered: