-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.19.0
-
None
-
Moderate
-
None
-
False
-
Description of problem:
When init containers are running with app containers.(an Istio sidecar container, which is automatically injected if the `label sidecar.istio.io/inject: 'true'` is added to the Pod), the init containers are not counted on pods list page, but they are counted by client with command "oc get pods".
Version-Release number of selected component (if applicable):
4.19.0-0.nightly-2025-03-13-234131
How reproducible:
Always
Steps to Reproduce:
1.Create sidecar enabled pods, refer to steps https://issues.redhat.com/browse/OCPBUGS-38543?focusedId=25642442&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-25642442
1). Install below operators. NAME DISPLAY VERSION REPLACES PHASE kiali-operator.v1.89.1 Kiali Operator 1.89.1 kiali-operator.v1.73.10 Succeeded servicemeshoperator.v2.6.1 Red Hat OpenShift Service Mesh 2.6.1-0 servicemeshoperator.v2.6.0 Succeeded 2). Create below namespaces istio-system httpd 3). Create SMCP apiVersion: maistra.io/v2 kind: ServiceMeshControlPlane metadata: name: basic namespace: istio-system spec: addons: grafana: enabled: true kiali: enabled: true prometheus: enabled: true gateways: openshiftRoute: enabled: false policy: type: Istiod profiles: - default runtime: components: pilot: container: env: ENABLE_NATIVE_SIDECARS: 'true' telemetry: type: Istiod tracing: type: None version: v2.6 4). Create SMMR apiVersion: maistra.io/v1 kind: ServiceMeshMemberRoll metadata: name: default namespace: istio-system spec: members: - httpd 5). Deploy an application with sidecar enabled "sidecar.istio.io/inject: 'true'" apiVersion: apps/v1 kind: Deployment metadata: labels: app: httpd name: httpd namespace: httpd spec: replicas: 1 selector: matchLabels: app: httpd template: metadata: labels: app: httpd sidecar.istio.io/inject: 'true' spec: containers: - image: registry.access.redhat.com/rhscl/httpd-24-rhel7 name: httpd ports: - containerPort: 8080
2.Check the httpd pod's ready info on pods list and also with 'oc get pods'.
Actual results:
2. On console the pod's container is '1/1' for 'Ready', but in client , it shows '2/2' for 'Ready' status.
Expected results:
2. On console pods list, should include init containers in readiness count if ready and started is true. Console should keep consistent with the CLI.
Additional info: