apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:19:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-197-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-197.ec2.internal uid: a85f41e7-5887-4b01-9bca-274e3ed43294 resourceVersion: "53041" uid: 4ac9d49b-cca2-4a9b-a306-a71362898eaa spec: sourcePod: network-check-source-7d88cb55d8-mtxj5 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-28T17:27:00Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 972.942µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:44:00Z" - latency: 895.871µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:43:00Z" - latency: 1.064312ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:42:00Z" - latency: 932.229µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:41:00Z" - latency: 1.152967ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:40:00Z" - latency: 1.354022ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:39:00Z" - latency: 835.559µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:38:00Z" - latency: 893.034µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:37:00Z" - latency: 948.036µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:36:00Z" - latency: 779.695µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:35:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:19:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-197-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-197.ec2.internal uid: a85f41e7-5887-4b01-9bca-274e3ed43294 resourceVersion: "53043" uid: 44565f45-3f3c-4899-a0fa-7b07582fb373 spec: sourcePod: network-check-source-7d88cb55d8-mtxj5 targetEndpoint: a28f5e1c3c827467183f8311ce767d94-c7b7e6e52eff7196.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T17:26:00Z" message: 'load-balancer-api-external: tcp connection to a28f5e1c3c827467183f8311ce767d94-c7b7e6e52eff7196.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.750299ms message: 'load-balancer-api-external: tcp connection to a28f5e1c3c827467183f8311ce767d94-c7b7e6e52eff7196.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:44:00Z" - latency: 7.942771ms message: 'load-balancer-api-external: resolved host name a28f5e1c3c827467183f8311ce767d94-c7b7e6e52eff7196.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:44:00Z" - latency: 5.123916ms message: 'load-balancer-api-external: tcp connection to a28f5e1c3c827467183f8311ce767d94-c7b7e6e52eff7196.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:43:00Z" - latency: 8.66369ms message: 'load-balancer-api-external: resolved host name a28f5e1c3c827467183f8311ce767d94-c7b7e6e52eff7196.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:43:00Z" - latency: 4.827771ms message: 'load-balancer-api-external: tcp connection to a28f5e1c3c827467183f8311ce767d94-c7b7e6e52eff7196.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:42:00Z" - latency: 9.728919ms message: 'load-balancer-api-external: resolved host name a28f5e1c3c827467183f8311ce767d94-c7b7e6e52eff7196.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:42:00Z" - latency: 5.19188ms message: 'load-balancer-api-external: tcp connection to a28f5e1c3c827467183f8311ce767d94-c7b7e6e52eff7196.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:41:00Z" - latency: 8.308346ms message: 'load-balancer-api-external: resolved host name a28f5e1c3c827467183f8311ce767d94-c7b7e6e52eff7196.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:41:00Z" - latency: 5.37095ms message: 'load-balancer-api-external: tcp connection to a28f5e1c3c827467183f8311ce767d94-c7b7e6e52eff7196.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:40:00Z" - latency: 8.443738ms message: 'load-balancer-api-external: resolved host name a28f5e1c3c827467183f8311ce767d94-c7b7e6e52eff7196.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:40:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:19:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-197-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-197.ec2.internal uid: a85f41e7-5887-4b01-9bca-274e3ed43294 resourceVersion: "53042" uid: 1fb0e36c-c22b-4668-8df0-0109b21fc990 spec: sourcePod: network-check-source-7d88cb55d8-mtxj5 targetEndpoint: a28f5e1c3c827467183f8311ce767d94-c7b7e6e52eff7196.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T17:26:00Z" message: 'load-balancer-api-internal: tcp connection to a28f5e1c3c827467183f8311ce767d94-c7b7e6e52eff7196.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.713825ms message: 'load-balancer-api-internal: tcp connection to a28f5e1c3c827467183f8311ce767d94-c7b7e6e52eff7196.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:44:00Z" - latency: 8.001047ms message: 'load-balancer-api-internal: resolved host name a28f5e1c3c827467183f8311ce767d94-c7b7e6e52eff7196.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:44:00Z" - latency: 4.414003ms message: 'load-balancer-api-internal: tcp connection to a28f5e1c3c827467183f8311ce767d94-c7b7e6e52eff7196.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:43:00Z" - latency: 8.687872ms message: 'load-balancer-api-internal: resolved host name a28f5e1c3c827467183f8311ce767d94-c7b7e6e52eff7196.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:43:00Z" - latency: 4.812922ms message: 'load-balancer-api-internal: tcp connection to a28f5e1c3c827467183f8311ce767d94-c7b7e6e52eff7196.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:42:00Z" - latency: 9.704275ms message: 'load-balancer-api-internal: resolved host name a28f5e1c3c827467183f8311ce767d94-c7b7e6e52eff7196.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:42:00Z" - latency: 5.135578ms message: 'load-balancer-api-internal: tcp connection to a28f5e1c3c827467183f8311ce767d94-c7b7e6e52eff7196.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:41:00Z" - latency: 8.337745ms message: 'load-balancer-api-internal: resolved host name a28f5e1c3c827467183f8311ce767d94-c7b7e6e52eff7196.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:41:00Z" - latency: 4.895764ms message: 'load-balancer-api-internal: tcp connection to a28f5e1c3c827467183f8311ce767d94-c7b7e6e52eff7196.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:40:00Z" - latency: 8.511881ms message: 'load-balancer-api-internal: resolved host name a28f5e1c3c827467183f8311ce767d94-c7b7e6e52eff7196.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T18:40:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:19:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-197-to-network-check-target-ip-10-0-132-11 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-197.ec2.internal uid: a85f41e7-5887-4b01-9bca-274e3ed43294 resourceVersion: "53037" uid: 5276c5d1-62a0-4149-bd58-4501f5e876f1 spec: sourcePod: network-check-source-7d88cb55d8-mtxj5 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-28T17:27:00Z" message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.186225ms message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:44:00Z" - latency: 2.630794ms message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:43:00Z" - latency: 2.263434ms message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:42:00Z" - latency: 2.321481ms message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:41:00Z" - latency: 2.325038ms message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:40:00Z" - latency: 2.30231ms message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:39:00Z" - latency: 2.067909ms message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:38:00Z" - latency: 1.951563ms message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:37:00Z" - latency: 2.04057ms message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:36:00Z" - latency: 2.085305ms message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:35:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:19:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-197-to-network-check-target-ip-10-0-138-92 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-197.ec2.internal uid: a85f41e7-5887-4b01-9bca-274e3ed43294 resourceVersion: "53039" uid: ca57ec93-2786-4b4a-9b55-74cf87ec12cf spec: sourcePod: network-check-source-7d88cb55d8-mtxj5 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-28T17:27:00Z" message: 'network-check-target-ip-10-0-138-92: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.650411ms message: 'network-check-target-ip-10-0-138-92: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:44:00Z" - latency: 1.770856ms message: 'network-check-target-ip-10-0-138-92: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:43:00Z" - latency: 2.139629ms message: 'network-check-target-ip-10-0-138-92: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:42:00Z" - latency: 2.292223ms message: 'network-check-target-ip-10-0-138-92: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:41:00Z" - latency: 2.374886ms message: 'network-check-target-ip-10-0-138-92: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:40:00Z" - latency: 2.705632ms message: 'network-check-target-ip-10-0-138-92: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:39:00Z" - latency: 1.493995ms message: 'network-check-target-ip-10-0-138-92: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:38:00Z" - latency: 1.843034ms message: 'network-check-target-ip-10-0-138-92: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:37:00Z" - latency: 1.81303ms message: 'network-check-target-ip-10-0-138-92: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:36:00Z" - latency: 1.841928ms message: 'network-check-target-ip-10-0-138-92: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:35:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:19:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-197-to-network-check-target-ip-10-0-142-197 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-197.ec2.internal uid: a85f41e7-5887-4b01-9bca-274e3ed43294 resourceVersion: "53038" uid: d735165e-5c94-4dfa-81a8-633dd7a9da99 spec: sourcePod: network-check-source-7d88cb55d8-mtxj5 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-28T17:27:00Z" message: 'network-check-target-ip-10-0-142-197: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 706.097µs message: 'network-check-target-ip-10-0-142-197: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:44:00Z" - latency: 816.599µs message: 'network-check-target-ip-10-0-142-197: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:43:00Z" - latency: 937.015µs message: 'network-check-target-ip-10-0-142-197: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:42:00Z" - latency: 1.662683ms message: 'network-check-target-ip-10-0-142-197: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:41:00Z" - latency: 1.373025ms message: 'network-check-target-ip-10-0-142-197: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:40:00Z" - latency: 1.355273ms message: 'network-check-target-ip-10-0-142-197: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:39:00Z" - latency: 1.2483ms message: 'network-check-target-ip-10-0-142-197: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:38:00Z" - latency: 877.41µs message: 'network-check-target-ip-10-0-142-197: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:37:00Z" - latency: 1.310227ms message: 'network-check-target-ip-10-0-142-197: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:36:00Z" - latency: 960.917µs message: 'network-check-target-ip-10-0-142-197: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:35:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T17:19:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-197-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-197.ec2.internal uid: a85f41e7-5887-4b01-9bca-274e3ed43294 resourceVersion: "53040" uid: b1de26ea-e002-4fc1-bcc6-ef92ef93ff68 spec: sourcePod: network-check-source-7d88cb55d8-mtxj5 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-28T17:26:00Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 832.147µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:44:00Z" - latency: 2.004894ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T18:44:00Z" - latency: 1.216024ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:43:00Z" - latency: 1.785517ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T18:43:00Z" - latency: 771.746µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:42:00Z" - latency: 1.71384ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T18:42:00Z" - latency: 1.171401ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:41:00Z" - latency: 1.926609ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T18:41:00Z" - latency: 772.85µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T18:40:00Z" - latency: 1.843632ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T18:40:00Z" kind: List metadata: resourceVersion: ""