[OPERATOR] PodDisruptionBudget is deployed even if ETCD has 1 replicas
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- kubernetes
- Domain
- devops, infrastructure
Research direction
Start with deploy/etcd/etcd-policy.yaml and inspect how the Operator renders this manifest from etcd.config.replicas. Reproduce the deployment with one replica and confirm the PodDisruptionBudget blocks node draining. Done means the PDB is absent for one replica while its existing behavior remains unchanged for higher replica counts.
Written by the indexing model from the issue text.
Description
- I have searched the issues of this repository and believe that this is not a duplicate.
Ⅰ. Issue Description
If we deploy Openserverless with etcd.config.replicas: 1, the Operator still deploys the PodDisruptionBudget (nuvolaris-etcd) resource and this prevents node drains.
Ⅱ. Describe what happened
PodDisruptionBudget (nuvolaris-etcd) resource prevents k8s node drains (and a manual change on PDB resource is required to make the drain go ahead)
Ⅲ. Describe what you expected to happen
PodDisruptionBudget (nuvolaris-etcd) should not be deployed if Openserverless is configured with etcd.config.replicas: 1.
Ⅳ. How to reproduce it (as minimally and precisely as possible)
- Deploy Openserverless with
etcd.config.replicas: 1 - Drain a master node
Minimal yet complete reproducer code (or URL to code):
Ⅴ. Anything else we need to know?
The issue is probabily related to this file:
https://github.com/apache/openserverless-operator/blob/main/deploy/etcd/etcd-policy.yaml
Maybe a condition should manage the deployment (or not) of manifest above.
Ⅵ. Environment:
- K8S Runtime and version: k3s v1.29.3+k3s1
- OPS CLI version: 0.1.0-2409121919.dev
- Dominant language
- Python
- Stars
- 576
- Forks
- 29
- Avg merge
- 51m
- Merged PRs (30d)
- 14
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.
More from apache/openserverless
-
help wanted
Difficulty 3/5 1-2 days Newbie friendliness 45/100
apache/openserverless#252 ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
apache/openserverless#215 ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 58/100
apache/openserverless#214 ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 72/100
apache/openserverless#213 ·
-
help wanted
Difficulty 5/5 Over a week Newbie friendliness 15/100
apache/openserverless#195 ·
All issues in apache/openserverless
Similar issues
-
essnmx good first issue
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
[Feature] 奇物选择添加优先级 Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
syfoud/Simulated_Scepter#174 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Giskard-AI/giskard-oss#2840 · 1 comment ·
-
A claim comment carrying the issue number is silently declined while the workflow reports success Openarea: repo bug perceived difficulty: 2
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
yeti-platform/yeti#1380 ·