dragonflydb / dragonflydb/dragonfly-operator

Service selector incorrect for single instance

Open
#357 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
357
Forks
111
PR merge metrics
No merged PRs in 30d

Description

When we set replicas: 1 in the Dragonfly Custom Resource, it turns out that the pod is lacking the `role: master` label.

As a workaround, we can explicitly set that label in the CR spec, but the service selector should not require `role: master` label being present when replicas == 1.

Contributor guide

Open the contributing guide

Research direction

No file or test is named. Start by tracing the Go reconciliation path that builds the Service selector for a Dragonfly Custom Resource with replicas: 1; verify how the selector relates to pod labels. Done means the single-instance Service selects the pod without requiring role: master, while the workaround is no longer needed.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
infrastructure
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.