pingcap / pingcap/tidb-operator
Can't change tiproxy service type
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 540
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 18
Description
Bug Report
What version of Kubernetes are you using?
v1.26.6
What version of TiDB Operator are you using?
v1.6.0
What did you do?
add spec.tiproxy.service.type = LoadBalancer in TidbCluster
What did you expect to see?
service type change to LoadBalancer
What did you see instead?
The request is invalid: patch: Invalid value: "...": strict decoding error: unknown field "spec.tiproxy.service"
part of my TidbCluster file:
spec:
....
tiproxy:
baseImage: pingcap/tiproxy
version: main
imagePullPolicy: Always
replicas: 3
service:
type: LoadBalancer
config: {}
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the TidbCluster CRD schema and TiProxy reconciliation path to see where the tiproxy fields are defined and how its Service is created. Verify the accepted manifest against the Kubernetes API and confirm that applying it changes the TiProxy Service type to LoadBalancer.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100