apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T21:18:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-162-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-162.ec2.internal uid: 73af8e03-858b-4062-8da8-2337fb339326 resourceVersion: "32361" uid: fbeeb8e8-9cb6-450f-ab25-f4b9907e14b6 spec: sourcePod: network-check-source-7d88cb55d8-bsshq targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-24T21:25:19Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.061901ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:00:18Z" - latency: 817.318µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:59:18Z" - latency: 811.81µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:58:18Z" - latency: 1.258581ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:57:18Z" - latency: 1.439887ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:56:18Z" - latency: 947.04µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:55:18Z" - latency: 1.095706ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:54:18Z" - latency: 1.227244ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:53:18Z" - latency: 841.756µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:52:18Z" - latency: 1.876312ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:51:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T21:18:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-162-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-162.ec2.internal uid: 73af8e03-858b-4062-8da8-2337fb339326 resourceVersion: "32362" uid: 7a4514b5-958a-4a4f-8e72-f870e6736be9 spec: sourcePod: network-check-source-7d88cb55d8-bsshq targetEndpoint: aeb644a7545db4aaf9659df7e21b08df-add824740814004d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-24T21:24:19Z" message: 'load-balancer-api-external: tcp connection to aeb644a7545db4aaf9659df7e21b08df-add824740814004d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.885788ms message: 'load-balancer-api-external: tcp connection to aeb644a7545db4aaf9659df7e21b08df-add824740814004d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:00:19Z" - latency: 10.641741ms message: 'load-balancer-api-external: resolved host name aeb644a7545db4aaf9659df7e21b08df-add824740814004d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T22:00:18Z" - latency: 4.594196ms message: 'load-balancer-api-external: tcp connection to aeb644a7545db4aaf9659df7e21b08df-add824740814004d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:59:19Z" - latency: 9.458982ms message: 'load-balancer-api-external: resolved host name aeb644a7545db4aaf9659df7e21b08df-add824740814004d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T21:59:18Z" - latency: 4.690391ms message: 'load-balancer-api-external: tcp connection to aeb644a7545db4aaf9659df7e21b08df-add824740814004d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:58:19Z" - latency: 9.832097ms message: 'load-balancer-api-external: resolved host name aeb644a7545db4aaf9659df7e21b08df-add824740814004d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T21:58:18Z" - latency: 4.501811ms message: 'load-balancer-api-external: tcp connection to aeb644a7545db4aaf9659df7e21b08df-add824740814004d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:57:19Z" - latency: 9.73967ms message: 'load-balancer-api-external: resolved host name aeb644a7545db4aaf9659df7e21b08df-add824740814004d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T21:57:18Z" - latency: 5.860513ms message: 'load-balancer-api-external: tcp connection to aeb644a7545db4aaf9659df7e21b08df-add824740814004d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:56:19Z" - latency: 11.801536ms message: 'load-balancer-api-external: resolved host name aeb644a7545db4aaf9659df7e21b08df-add824740814004d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T21:56:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T21:18:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-162-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-162.ec2.internal uid: 73af8e03-858b-4062-8da8-2337fb339326 resourceVersion: "32363" uid: dc5e600e-42b8-4cf5-9bde-3c7d7285d8a2 spec: sourcePod: network-check-source-7d88cb55d8-bsshq targetEndpoint: aeb644a7545db4aaf9659df7e21b08df-add824740814004d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-24T21:24:19Z" message: 'load-balancer-api-internal: tcp connection to aeb644a7545db4aaf9659df7e21b08df-add824740814004d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 7.067904ms message: 'load-balancer-api-internal: tcp connection to aeb644a7545db4aaf9659df7e21b08df-add824740814004d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:00:19Z" - latency: 10.514071ms message: 'load-balancer-api-internal: resolved host name aeb644a7545db4aaf9659df7e21b08df-add824740814004d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T22:00:18Z" - latency: 4.53962ms message: 'load-balancer-api-internal: tcp connection to aeb644a7545db4aaf9659df7e21b08df-add824740814004d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:59:19Z" - latency: 9.526863ms message: 'load-balancer-api-internal: resolved host name aeb644a7545db4aaf9659df7e21b08df-add824740814004d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T21:59:18Z" - latency: 4.683536ms message: 'load-balancer-api-internal: tcp connection to aeb644a7545db4aaf9659df7e21b08df-add824740814004d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:58:19Z" - latency: 9.710294ms message: 'load-balancer-api-internal: resolved host name aeb644a7545db4aaf9659df7e21b08df-add824740814004d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T21:58:18Z" - latency: 4.508594ms message: 'load-balancer-api-internal: tcp connection to aeb644a7545db4aaf9659df7e21b08df-add824740814004d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:57:19Z" - latency: 9.784116ms message: 'load-balancer-api-internal: resolved host name aeb644a7545db4aaf9659df7e21b08df-add824740814004d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T21:57:18Z" - latency: 5.904781ms message: 'load-balancer-api-internal: tcp connection to aeb644a7545db4aaf9659df7e21b08df-add824740814004d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:56:19Z" - latency: 11.645763ms message: 'load-balancer-api-internal: resolved host name aeb644a7545db4aaf9659df7e21b08df-add824740814004d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T21:56:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T21:18:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-162-to-network-check-target-ip-10-0-128-63 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-162.ec2.internal uid: 73af8e03-858b-4062-8da8-2337fb339326 resourceVersion: "32358" uid: b1adbe23-1f11-4704-86a4-fa482ddaf80b spec: sourcePod: network-check-source-7d88cb55d8-bsshq targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-24T21:25:19Z" message: 'network-check-target-ip-10-0-128-63: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.210173ms message: 'network-check-target-ip-10-0-128-63: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:00:18Z" - latency: 2.267363ms message: 'network-check-target-ip-10-0-128-63: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:59:18Z" - latency: 2.100039ms message: 'network-check-target-ip-10-0-128-63: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:58:18Z" - latency: 2.137133ms message: 'network-check-target-ip-10-0-128-63: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:57:18Z" - latency: 2.741378ms message: 'network-check-target-ip-10-0-128-63: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:56:18Z" - latency: 2.07954ms message: 'network-check-target-ip-10-0-128-63: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:55:18Z" - latency: 2.41228ms message: 'network-check-target-ip-10-0-128-63: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:54:18Z" - latency: 2.202613ms message: 'network-check-target-ip-10-0-128-63: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:53:18Z" - latency: 2.217346ms message: 'network-check-target-ip-10-0-128-63: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:52:18Z" - latency: 2.526557ms message: 'network-check-target-ip-10-0-128-63: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:51:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T21:18:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-162-to-network-check-target-ip-10-0-137-226 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-162.ec2.internal uid: 73af8e03-858b-4062-8da8-2337fb339326 resourceVersion: "32359" uid: 92bb32ae-2e70-498f-aeaf-ccb561d3ecce spec: sourcePod: network-check-source-7d88cb55d8-bsshq targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-24T21:25:19Z" message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.461955ms message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:00:18Z" - latency: 2.292709ms message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:59:18Z" - latency: 2.141927ms message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:58:18Z" - latency: 2.164888ms message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:57:18Z" - latency: 2.881027ms message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:56:18Z" - latency: 1.874479ms message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:55:18Z" - latency: 2.115105ms message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:54:18Z" - latency: 2.352456ms message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:53:18Z" - latency: 2.413501ms message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:52:18Z" - latency: 2.50482ms message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:51:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T21:18:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-162-to-network-check-target-ip-10-0-140-162 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-162.ec2.internal uid: 73af8e03-858b-4062-8da8-2337fb339326 resourceVersion: "32357" uid: 4ca9e82b-f902-4c5e-91d3-cf178837242b spec: sourcePod: network-check-source-7d88cb55d8-bsshq targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-24T21:25:18Z" message: 'network-check-target-ip-10-0-140-162: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.49752ms message: 'network-check-target-ip-10-0-140-162: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:00:18Z" - latency: 1.023551ms message: 'network-check-target-ip-10-0-140-162: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:59:18Z" - latency: 1.20314ms message: 'network-check-target-ip-10-0-140-162: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:58:18Z" - latency: 919.896µs message: 'network-check-target-ip-10-0-140-162: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:57:18Z" - latency: 1.92074ms message: 'network-check-target-ip-10-0-140-162: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:56:18Z" - latency: 790.536µs message: 'network-check-target-ip-10-0-140-162: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:55:18Z" - latency: 864.075µs message: 'network-check-target-ip-10-0-140-162: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:54:18Z" - latency: 858.957µs message: 'network-check-target-ip-10-0-140-162: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:53:18Z" - latency: 833.23µs message: 'network-check-target-ip-10-0-140-162: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:52:18Z" - latency: 1.004807ms message: 'network-check-target-ip-10-0-140-162: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:51:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T21:18:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-162-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-162.ec2.internal uid: 73af8e03-858b-4062-8da8-2337fb339326 resourceVersion: "32360" uid: 857b0881-acbe-4f3f-ab72-9ac854c768c3 spec: sourcePod: network-check-source-7d88cb55d8-bsshq targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-24T21:24:19Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.058005ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:00:19Z" - latency: 2.112721ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T22:00:18Z" - latency: 874.4µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:59:19Z" - latency: 2.552396ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T21:59:18Z" - latency: 921.973µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:58:19Z" - latency: 2.203947ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T21:58:18Z" - latency: 839.291µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:57:19Z" - latency: 1.842785ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T21:57:18Z" - latency: 1.035686ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:56:19Z" - latency: 2.890066ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T21:56:18Z" kind: List metadata: resourceVersion: ""