Closed Somnath-Pandey-Vested closed 3 days ago
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/reopen
/remove-lifecycle rotten
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
@k8s-triage-robot: Closing this issue, marking it as "Not Planned".
Describe the bug A concise description of what the bug is. I have injected the readiness gate at the namespace level. When i try to deploy the pod using helm the readiness gate is coming as 1/1 but when i execute the below command `kubectl get po invest-test-66db578799-gcfg5 -n readiness -o yaml | grep -B7 'type: target-health' path: namespace status: conditions:
when i do an upgrade of the same helm chart then the readiness gate is not coming up
kubectl get po -o wide -n readiness NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES invest-test-66db578799-z44xk 1/1 Running 0 4m51s 10.3.18.153 ip-10-3-18-70.ap-south-1.compute.internalExpected outcome A concise description of what you expected to happen. When the readiness gate is installed at namespace level all the upcoming pods should get the readiness gate. Environment
Additional Context: