zalando / zalando/postgres-operator
Postgres Operator UI does not reload Kubernetes tokens
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
Kubernetes now issues short lived tokens.
When the --service-account-extend-token-expiration flag is set to true (which seems to still be the default for many implementations), service account tokens are valid for one year, meaning the Postgres Operator UI pod is likely to get restarted/recreated before its token expires.
However, on AKS clusters running Kubernetes v1.30.0 and later, the --service-account-extend-token-expiration flag is set to false and service account tokens expire after one hour.
- Which image of the operator are you using? ghcr.io/zalando/postgres-operator-ui:v1.14.0
- Where do you run it? AKS
- Are you running Postgres Operator in production? yes (but not on AKS)
- Type of issue? Bug
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
The issue names no files, tests, or entry points. Start by locating the Postgres Operator UI's Kubernetes service-account token handling and reproduce the one-hour expiry behavior on AKS with Kubernetes v1.30 or later; done means the UI continues authenticating after its token expires.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, postgresql
- Domain
- authentication, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100