apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T15:07:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-228-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-228.ec2.internal uid: 041b890f-a004-4e98-8d72-66a8c17ebaba resourceVersion: "56691" uid: c56be3bf-c592-4729-be5d-d3014d2fc7dd spec: sourcePod: network-check-source-7bc5b6bf85-h2psq targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-22T15:14:50Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.37588ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:42:50Z" - latency: 1.035206ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:41:50Z" - latency: 1.112224ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:40:50Z" - latency: 1.437011ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:39:50Z" - latency: 998.549µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:38:50Z" - latency: 1.277546ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:37:50Z" - latency: 1.094344ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:36:50Z" - latency: 965.526µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:35:50Z" - latency: 999.105µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:34:50Z" - latency: 889.682µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:33:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T15:07:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-228-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-228.ec2.internal uid: 041b890f-a004-4e98-8d72-66a8c17ebaba resourceVersion: "57754" uid: 2a3d7984-17b9-4b49-ab6e-a89cdb9ef523 spec: sourcePod: network-check-source-7bc5b6bf85-h2psq targetEndpoint: a3b85a957b2584a8e8e9a94bfc9a353a-9010bd7ed233ad09.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-22T15:13:50Z" message: 'load-balancer-api-external: tcp connection to a3b85a957b2584a8e8e9a94bfc9a353a-9010bd7ed233ad09.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.683048ms message: 'load-balancer-api-external: tcp connection to a3b85a957b2584a8e8e9a94bfc9a353a-9010bd7ed233ad09.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:43:50Z" - latency: 6.54237ms message: 'load-balancer-api-external: resolved host name a3b85a957b2584a8e8e9a94bfc9a353a-9010bd7ed233ad09.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T15:43:50Z" - latency: 5.090165ms message: 'load-balancer-api-external: tcp connection to a3b85a957b2584a8e8e9a94bfc9a353a-9010bd7ed233ad09.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:42:50Z" - latency: 7.442355ms message: 'load-balancer-api-external: resolved host name a3b85a957b2584a8e8e9a94bfc9a353a-9010bd7ed233ad09.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T15:42:50Z" - latency: 6.040444ms message: 'load-balancer-api-external: tcp connection to a3b85a957b2584a8e8e9a94bfc9a353a-9010bd7ed233ad09.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:41:50Z" - latency: 6.88763ms message: 'load-balancer-api-external: resolved host name a3b85a957b2584a8e8e9a94bfc9a353a-9010bd7ed233ad09.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T15:41:50Z" - latency: 5.198472ms message: 'load-balancer-api-external: tcp connection to a3b85a957b2584a8e8e9a94bfc9a353a-9010bd7ed233ad09.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:40:50Z" - latency: 6.000707ms message: 'load-balancer-api-external: resolved host name a3b85a957b2584a8e8e9a94bfc9a353a-9010bd7ed233ad09.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T15:40:50Z" - latency: 4.294255ms message: 'load-balancer-api-external: tcp connection to a3b85a957b2584a8e8e9a94bfc9a353a-9010bd7ed233ad09.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:39:50Z" - latency: 7.667833ms message: 'load-balancer-api-external: resolved host name a3b85a957b2584a8e8e9a94bfc9a353a-9010bd7ed233ad09.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T15:39:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T15:07:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-228-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-228.ec2.internal uid: 041b890f-a004-4e98-8d72-66a8c17ebaba resourceVersion: "57753" uid: afd42f25-2fa1-42a5-a7cf-972fd2e23a03 spec: sourcePod: network-check-source-7bc5b6bf85-h2psq targetEndpoint: a3b85a957b2584a8e8e9a94bfc9a353a-9010bd7ed233ad09.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-22T15:13:50Z" message: 'load-balancer-api-internal: tcp connection to a3b85a957b2584a8e8e9a94bfc9a353a-9010bd7ed233ad09.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.70921ms message: 'load-balancer-api-internal: tcp connection to a3b85a957b2584a8e8e9a94bfc9a353a-9010bd7ed233ad09.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:43:50Z" - latency: 6.405117ms message: 'load-balancer-api-internal: resolved host name a3b85a957b2584a8e8e9a94bfc9a353a-9010bd7ed233ad09.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T15:43:50Z" - latency: 8.500816ms message: 'load-balancer-api-internal: tcp connection to a3b85a957b2584a8e8e9a94bfc9a353a-9010bd7ed233ad09.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:42:50Z" - latency: 7.511498ms message: 'load-balancer-api-internal: resolved host name a3b85a957b2584a8e8e9a94bfc9a353a-9010bd7ed233ad09.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T15:42:50Z" - latency: 5.965621ms message: 'load-balancer-api-internal: tcp connection to a3b85a957b2584a8e8e9a94bfc9a353a-9010bd7ed233ad09.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:41:50Z" - latency: 6.775537ms message: 'load-balancer-api-internal: resolved host name a3b85a957b2584a8e8e9a94bfc9a353a-9010bd7ed233ad09.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T15:41:50Z" - latency: 5.234575ms message: 'load-balancer-api-internal: tcp connection to a3b85a957b2584a8e8e9a94bfc9a353a-9010bd7ed233ad09.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:40:50Z" - latency: 5.892886ms message: 'load-balancer-api-internal: resolved host name a3b85a957b2584a8e8e9a94bfc9a353a-9010bd7ed233ad09.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T15:40:50Z" - latency: 4.238958ms message: 'load-balancer-api-internal: tcp connection to a3b85a957b2584a8e8e9a94bfc9a353a-9010bd7ed233ad09.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:39:50Z" - latency: 7.652627ms message: 'load-balancer-api-internal: resolved host name a3b85a957b2584a8e8e9a94bfc9a353a-9010bd7ed233ad09.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T15:39:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T15:07:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-228-to-network-check-target-ip-10-0-128-22 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-228.ec2.internal uid: 041b890f-a004-4e98-8d72-66a8c17ebaba resourceVersion: "56690" uid: 100c4c8b-7c06-4243-9626-075f454cea5c spec: sourcePod: network-check-source-7bc5b6bf85-h2psq targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-22T15:14:50Z" message: 'network-check-target-ip-10-0-128-22: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.376267ms message: 'network-check-target-ip-10-0-128-22: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:42:50Z" - latency: 2.16497ms message: 'network-check-target-ip-10-0-128-22: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:41:50Z" - latency: 2.118796ms message: 'network-check-target-ip-10-0-128-22: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:40:50Z" - latency: 2.158091ms message: 'network-check-target-ip-10-0-128-22: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:39:50Z" - latency: 2.135722ms message: 'network-check-target-ip-10-0-128-22: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:38:50Z" - latency: 2.1784ms message: 'network-check-target-ip-10-0-128-22: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:37:50Z" - latency: 2.227978ms message: 'network-check-target-ip-10-0-128-22: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:36:50Z" - latency: 2.181356ms message: 'network-check-target-ip-10-0-128-22: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:35:50Z" - latency: 2.387008ms message: 'network-check-target-ip-10-0-128-22: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:34:50Z" - latency: 1.704691ms message: 'network-check-target-ip-10-0-128-22: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:33:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T15:07:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-228-to-network-check-target-ip-10-0-132-228 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-228.ec2.internal uid: 041b890f-a004-4e98-8d72-66a8c17ebaba resourceVersion: "56688" uid: a0472c9f-1093-4dae-a37d-d03384e78eb8 spec: sourcePod: network-check-source-7bc5b6bf85-h2psq targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-22T15:14:50Z" message: 'network-check-target-ip-10-0-132-228: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 925.602µs message: 'network-check-target-ip-10-0-132-228: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:42:50Z" - latency: 849.288µs message: 'network-check-target-ip-10-0-132-228: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:41:50Z" - latency: 1.356162ms message: 'network-check-target-ip-10-0-132-228: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:40:50Z" - latency: 831.421µs message: 'network-check-target-ip-10-0-132-228: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:39:50Z" - latency: 1.006221ms message: 'network-check-target-ip-10-0-132-228: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:38:50Z" - latency: 1.008854ms message: 'network-check-target-ip-10-0-132-228: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:37:50Z" - latency: 826.334µs message: 'network-check-target-ip-10-0-132-228: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:36:50Z" - latency: 1.14192ms message: 'network-check-target-ip-10-0-132-228: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:35:50Z" - latency: 1.181833ms message: 'network-check-target-ip-10-0-132-228: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:34:50Z" - latency: 813.39µs message: 'network-check-target-ip-10-0-132-228: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:33:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T15:07:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-228-to-network-check-target-ip-10-0-142-80 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-228.ec2.internal uid: 041b890f-a004-4e98-8d72-66a8c17ebaba resourceVersion: "56689" uid: 7e0cc906-974b-4ad7-bc8c-5fbcc4b92fd5 spec: sourcePod: network-check-source-7bc5b6bf85-h2psq targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-22T15:14:50Z" message: 'network-check-target-ip-10-0-142-80: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.351871ms message: 'network-check-target-ip-10-0-142-80: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:42:50Z" - latency: 1.770363ms message: 'network-check-target-ip-10-0-142-80: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:41:50Z" - latency: 2.119661ms message: 'network-check-target-ip-10-0-142-80: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:40:50Z" - latency: 1.87396ms message: 'network-check-target-ip-10-0-142-80: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:39:50Z" - latency: 1.737886ms message: 'network-check-target-ip-10-0-142-80: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:38:50Z" - latency: 1.940125ms message: 'network-check-target-ip-10-0-142-80: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:37:50Z" - latency: 2.034389ms message: 'network-check-target-ip-10-0-142-80: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:36:50Z" - latency: 2.012693ms message: 'network-check-target-ip-10-0-142-80: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:35:50Z" - latency: 1.872635ms message: 'network-check-target-ip-10-0-142-80: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:34:50Z" - latency: 2.008746ms message: 'network-check-target-ip-10-0-142-80: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:33:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T15:07:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-228-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-228.ec2.internal uid: 041b890f-a004-4e98-8d72-66a8c17ebaba resourceVersion: "57752" uid: ec3d4c9d-b15a-4b50-9d7a-5251c6db55d0 spec: sourcePod: network-check-source-7bc5b6bf85-h2psq targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-22T15:13:50Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.341693ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:43:50Z" - latency: 1.929142ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T15:43:50Z" - latency: 1.055735ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:42:50Z" - latency: 2.026314ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T15:42:50Z" - latency: 906.397µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:41:50Z" - latency: 1.718385ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T15:41:50Z" - latency: 1.054323ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:40:50Z" - latency: 1.543738ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T15:40:50Z" - latency: 969.928µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T15:39:50Z" - latency: 1.825068ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T15:39:50Z" kind: List metadata: resourceVersion: ""