zalando / zalando/postgres-operator
"spec.teamId: Required value", even when Teams API is disabled
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
- Which image of the operator are you using? registry.opensource.zalan.do/acid/postgres-operator:v1.10.1
- Where do you run it - cloud or metal? Kubernetes or OpenShift? cloud - Azure AKS
- Are you running Postgres Operator in production? no
- Type of issue? question
Hi,
I have the postgres-operator installed using a Helm chart:
repoURL: https://opensource.zalando.com/postgres-operator/charts/postgres-operator
chart: postgres-operator
targetRevision: 1.10.1
helm:
values: |
configLoadBalancer:
db_hosted_zone: ##MY_HOSTED_ZONE##
master_dns_name_format: "{cluster}.{hostedzone}"
configTeamsApi:
enable_teams_api: false
As you can see, we disable the Teams API. However, when I try to deploy a PostgreSQL database server, and I don't specify a team like:
apiVersion: acid.zalan.do/v1
kind: postgresql
metadata:
name: {{ .Values.server.name }}
namespace: {{ .Release.Namespace }}
spec:
...
teamId: "acid" <----
...
... I'm getting follow error during deployment:
"spec.teamId: Required value"
Is it possible the field teamId is always required, even if the Teams API is disabled?
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 with the Helm values for configTeamsApi and the PostgreSQL resource validation that produces "spec.teamId: Required value". Reproduce the deployment using the shown operator version with Teams API disabled and compare the behavior with and without teamId; done means the validation matches the documented Teams API configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, helm, kubernetes, postgresql
- Domain
- databases, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100