apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T19:40:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-248-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-248.ec2.internal uid: b247a6a0-ac24-4d7a-a299-f82033a9a0e7 resourceVersion: "70637" uid: 2f771ee0-9446-4cc0-b6f2-60dbf113ac32 spec: sourcePod: network-check-source-7d88cb55d8-9jmzh targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-28T19:47:51Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.254334ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:29:51Z" - latency: 1.2903ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:28:51Z" - latency: 1.114315ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:27:51Z" - latency: 1.214856ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:26:51Z" - latency: 985.762µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:25:51Z" - latency: 917.503µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:24:51Z" - latency: 1.371261ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:23:51Z" - latency: 1.784489ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:22:51Z" - latency: 1.530264ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:21:51Z" - latency: 1.156746ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:20:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T19:40:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-248-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-248.ec2.internal uid: b247a6a0-ac24-4d7a-a299-f82033a9a0e7 resourceVersion: "69415" uid: fd932d5d-6082-4d5a-a795-1913e8c02560 spec: sourcePod: network-check-source-7d88cb55d8-9jmzh targetEndpoint: aa70b43f8638e4cd2a5183362e4ad7a1-bfeb7f87a842cbae.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T19:46:51Z" message: 'load-balancer-api-external: tcp connection to aa70b43f8638e4cd2a5183362e4ad7a1-bfeb7f87a842cbae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.645521ms message: 'load-balancer-api-external: tcp connection to aa70b43f8638e4cd2a5183362e4ad7a1-bfeb7f87a842cbae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:28:51Z" - latency: 7.131196ms message: 'load-balancer-api-external: resolved host name aa70b43f8638e4cd2a5183362e4ad7a1-bfeb7f87a842cbae.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T20:28:51Z" - latency: 6.251692ms message: 'load-balancer-api-external: tcp connection to aa70b43f8638e4cd2a5183362e4ad7a1-bfeb7f87a842cbae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:27:51Z" - latency: 7.020111ms message: 'load-balancer-api-external: resolved host name aa70b43f8638e4cd2a5183362e4ad7a1-bfeb7f87a842cbae.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T20:27:51Z" - latency: 4.576782ms message: 'load-balancer-api-external: tcp connection to aa70b43f8638e4cd2a5183362e4ad7a1-bfeb7f87a842cbae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:26:51Z" - latency: 7.644083ms message: 'load-balancer-api-external: resolved host name aa70b43f8638e4cd2a5183362e4ad7a1-bfeb7f87a842cbae.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T20:26:51Z" - latency: 5.429266ms message: 'load-balancer-api-external: tcp connection to aa70b43f8638e4cd2a5183362e4ad7a1-bfeb7f87a842cbae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:25:51Z" - latency: 6.24583ms message: 'load-balancer-api-external: resolved host name aa70b43f8638e4cd2a5183362e4ad7a1-bfeb7f87a842cbae.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T20:25:51Z" - latency: 7.49568ms message: 'load-balancer-api-external: tcp connection to aa70b43f8638e4cd2a5183362e4ad7a1-bfeb7f87a842cbae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:24:51Z" - latency: 7.403497ms message: 'load-balancer-api-external: resolved host name aa70b43f8638e4cd2a5183362e4ad7a1-bfeb7f87a842cbae.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T20:24:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T19:40:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-248-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-248.ec2.internal uid: b247a6a0-ac24-4d7a-a299-f82033a9a0e7 resourceVersion: "69416" uid: cab464ca-e50c-4ff2-b890-68d727888b42 spec: sourcePod: network-check-source-7d88cb55d8-9jmzh targetEndpoint: aa70b43f8638e4cd2a5183362e4ad7a1-bfeb7f87a842cbae.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T19:46:51Z" message: 'load-balancer-api-internal: tcp connection to aa70b43f8638e4cd2a5183362e4ad7a1-bfeb7f87a842cbae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 8.493426ms message: 'load-balancer-api-internal: tcp connection to aa70b43f8638e4cd2a5183362e4ad7a1-bfeb7f87a842cbae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:28:51Z" - latency: 6.935324ms message: 'load-balancer-api-internal: resolved host name aa70b43f8638e4cd2a5183362e4ad7a1-bfeb7f87a842cbae.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T20:28:51Z" - latency: 6.213739ms message: 'load-balancer-api-internal: tcp connection to aa70b43f8638e4cd2a5183362e4ad7a1-bfeb7f87a842cbae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:27:51Z" - latency: 7.076276ms message: 'load-balancer-api-internal: resolved host name aa70b43f8638e4cd2a5183362e4ad7a1-bfeb7f87a842cbae.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T20:27:51Z" - latency: 4.559719ms message: 'load-balancer-api-internal: tcp connection to aa70b43f8638e4cd2a5183362e4ad7a1-bfeb7f87a842cbae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:26:51Z" - latency: 7.624015ms message: 'load-balancer-api-internal: resolved host name aa70b43f8638e4cd2a5183362e4ad7a1-bfeb7f87a842cbae.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T20:26:51Z" - latency: 5.423279ms message: 'load-balancer-api-internal: tcp connection to aa70b43f8638e4cd2a5183362e4ad7a1-bfeb7f87a842cbae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:25:51Z" - latency: 6.31888ms message: 'load-balancer-api-internal: resolved host name aa70b43f8638e4cd2a5183362e4ad7a1-bfeb7f87a842cbae.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T20:25:51Z" - latency: 4.526077ms message: 'load-balancer-api-internal: tcp connection to aa70b43f8638e4cd2a5183362e4ad7a1-bfeb7f87a842cbae.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:24:51Z" - latency: 7.338027ms message: 'load-balancer-api-internal: resolved host name aa70b43f8638e4cd2a5183362e4ad7a1-bfeb7f87a842cbae.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T20:24:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T19:40:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-248-to-network-check-target-ip-10-0-132-248 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-248.ec2.internal uid: b247a6a0-ac24-4d7a-a299-f82033a9a0e7 resourceVersion: "70634" uid: 1c9e34ac-faeb-4e8a-bec4-cd8cab115b1b spec: sourcePod: network-check-source-7d88cb55d8-9jmzh targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-28T19:47:51Z" message: 'network-check-target-ip-10-0-132-248: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 956.396µs message: 'network-check-target-ip-10-0-132-248: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:29:51Z" - latency: 954.612µs message: 'network-check-target-ip-10-0-132-248: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:28:51Z" - latency: 1.589043ms message: 'network-check-target-ip-10-0-132-248: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:27:51Z" - latency: 978.835µs message: 'network-check-target-ip-10-0-132-248: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:26:51Z" - latency: 1.011071ms message: 'network-check-target-ip-10-0-132-248: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:25:51Z" - latency: 1.178486ms message: 'network-check-target-ip-10-0-132-248: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:24:51Z" - latency: 959.3µs message: 'network-check-target-ip-10-0-132-248: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:23:51Z" - latency: 834.128µs message: 'network-check-target-ip-10-0-132-248: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:22:51Z" - latency: 1.121838ms message: 'network-check-target-ip-10-0-132-248: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:21:51Z" - latency: 1.006181ms message: 'network-check-target-ip-10-0-132-248: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:20:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T19:40:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-248-to-network-check-target-ip-10-0-136-194 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-248.ec2.internal uid: b247a6a0-ac24-4d7a-a299-f82033a9a0e7 resourceVersion: "70636" uid: 37d9383f-d278-4898-9559-5d867fa3cfda spec: sourcePod: network-check-source-7d88cb55d8-9jmzh targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-28T19:47:51Z" message: 'network-check-target-ip-10-0-136-194: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.491718ms message: 'network-check-target-ip-10-0-136-194: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:29:51Z" - latency: 2.370395ms message: 'network-check-target-ip-10-0-136-194: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:28:51Z" - latency: 2.280377ms message: 'network-check-target-ip-10-0-136-194: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:27:51Z" - latency: 3.103067ms message: 'network-check-target-ip-10-0-136-194: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:26:51Z" - latency: 2.42645ms message: 'network-check-target-ip-10-0-136-194: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:25:51Z" - latency: 2.478448ms message: 'network-check-target-ip-10-0-136-194: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:24:51Z" - latency: 2.48731ms message: 'network-check-target-ip-10-0-136-194: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:23:51Z" - latency: 2.579876ms message: 'network-check-target-ip-10-0-136-194: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:22:51Z" - latency: 2.47546ms message: 'network-check-target-ip-10-0-136-194: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:21:51Z" - latency: 2.755934ms message: 'network-check-target-ip-10-0-136-194: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:20:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T19:40:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-248-to-network-check-target-ip-10-0-138-173 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-248.ec2.internal uid: b247a6a0-ac24-4d7a-a299-f82033a9a0e7 resourceVersion: "70635" uid: f0d00f95-5346-4c8a-acf4-477ee0290245 spec: sourcePod: network-check-source-7d88cb55d8-9jmzh targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-28T19:47:51Z" message: 'network-check-target-ip-10-0-138-173: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.087654ms message: 'network-check-target-ip-10-0-138-173: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:29:51Z" - latency: 2.022496ms message: 'network-check-target-ip-10-0-138-173: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:28:51Z" - latency: 2.641875ms message: 'network-check-target-ip-10-0-138-173: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:27:51Z" - latency: 2.455203ms message: 'network-check-target-ip-10-0-138-173: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:26:51Z" - latency: 2.145379ms message: 'network-check-target-ip-10-0-138-173: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:25:51Z" - latency: 2.262073ms message: 'network-check-target-ip-10-0-138-173: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:24:51Z" - latency: 2.181388ms message: 'network-check-target-ip-10-0-138-173: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:23:51Z" - latency: 2.55096ms message: 'network-check-target-ip-10-0-138-173: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:22:51Z" - latency: 2.483104ms message: 'network-check-target-ip-10-0-138-173: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:21:51Z" - latency: 2.721457ms message: 'network-check-target-ip-10-0-138-173: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:20:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T19:40:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-248-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-248.ec2.internal uid: b247a6a0-ac24-4d7a-a299-f82033a9a0e7 resourceVersion: "69414" uid: 4c473e74-211b-4714-9744-f36fb5e342b1 spec: sourcePod: network-check-source-7d88cb55d8-9jmzh targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-28T19:46:51Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.090453ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:28:51Z" - latency: 1.893661ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T20:28:51Z" - latency: 956.035µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:27:51Z" - latency: 1.746311ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T20:27:51Z" - latency: 1.364828ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:26:51Z" - latency: 1.865561ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T20:26:51Z" - latency: 907.68µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:25:51Z" - latency: 1.649418ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T20:25:51Z" - latency: 944.132µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T20:24:51Z" - latency: 2.231894ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T20:24:51Z" kind: List metadata: resourceVersion: ""