-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.13, 4.12, 4.11, 4.10, 4.14, 4.15, 4.16, 4.17, 4.18, 4.19
-
None
-
Rejected
-
False
-
-
-
Description of problem:
bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2073304 Description of problem: When using unauthorized sysctl in a deployment, replicaSet controller continuously creating pods in SysctlForbidden state
Version-Release number of selected component (if applicable):
How reproducible:
Create a deployment using unsecured and not allowed sysctl
Steps to Reproduce:
1. 2. 3.
Actual results:
replicatSet creates pod in SysctlForbidden state in loop
Expected results:
replicatSet should create only 10 pods in SysctlForbidden state and failed without creating new pods
Additional info:
- Kube issue exists already https://github.com/kubernetes/kubernetes/issues/72593 - The following workarounds can partially mitigate the problem: https://bugzilla.redhat.com/show_bug.cgi?id=2073304#c3
- is related to
-
OCPBUGS-42257 DaemonSet is reporting incorrect number of ready pods, causing pod flooding on specific OpenShift Container Platform 4 - Node
- New
- relates to
-
OCPBUGS-16379 When a pod template in a deployment is specified with a matching `nodename` and a never-matching `nodeSelector` an unlimited number of pods are created
- New