apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-29T21:45:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-134-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-134.ec2.internal uid: cba6fdf3-f793-4295-ab65-947aad936c21 resourceVersion: "175343" uid: 9b521852-51f4-4246-86ee-660ed90e0d76 spec: sourcePod: network-check-source-6f78d59f99-zc52n targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-29T21:52:36Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 883.359µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:48:36Z" - latency: 1.203172ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:47:36Z" - latency: 2.015669ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:46:36Z" - latency: 1.744654ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:45:36Z" - latency: 1.440739ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:44:36Z" - latency: 3.235209ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:43:36Z" - latency: 2.716314ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:42:36Z" - latency: 1.579738ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:41:36Z" - latency: 1.755299ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:40:36Z" - latency: 1.167204ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:39:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-29T21:45:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-134-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-134.ec2.internal uid: cba6fdf3-f793-4295-ab65-947aad936c21 resourceVersion: "167543" uid: 889b595e-8d2f-4a95-a779-e6fac1e2cfbe spec: sourcePod: network-check-source-6f78d59f99-zc52n targetEndpoint: a43366d352a4e4a2d9a605445fbedc72-d2a13ea726718ca9.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-29T21:51:36Z" message: 'load-balancer-api-external: tcp connection to a43366d352a4e4a2d9a605445fbedc72-d2a13ea726718ca9.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 19.077143ms message: 'load-balancer-api-external: tcp connection to a43366d352a4e4a2d9a605445fbedc72-d2a13ea726718ca9.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:45:36Z" - latency: 8.504451ms message: 'load-balancer-api-external: resolved host name a43366d352a4e4a2d9a605445fbedc72-d2a13ea726718ca9.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-29T22:45:36Z" - latency: 16.81953ms message: 'load-balancer-api-external: tcp connection to a43366d352a4e4a2d9a605445fbedc72-d2a13ea726718ca9.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:44:36Z" - latency: 6.848743ms message: 'load-balancer-api-external: resolved host name a43366d352a4e4a2d9a605445fbedc72-d2a13ea726718ca9.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-29T22:44:36Z" - latency: 17.538234ms message: 'load-balancer-api-external: tcp connection to a43366d352a4e4a2d9a605445fbedc72-d2a13ea726718ca9.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:43:36Z" - latency: 10.865644ms message: 'load-balancer-api-external: resolved host name a43366d352a4e4a2d9a605445fbedc72-d2a13ea726718ca9.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-29T22:43:36Z" - latency: 19.943866ms message: 'load-balancer-api-external: tcp connection to a43366d352a4e4a2d9a605445fbedc72-d2a13ea726718ca9.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:42:36Z" - latency: 9.136538ms message: 'load-balancer-api-external: resolved host name a43366d352a4e4a2d9a605445fbedc72-d2a13ea726718ca9.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-29T22:42:36Z" - latency: 17.757319ms message: 'load-balancer-api-external: tcp connection to a43366d352a4e4a2d9a605445fbedc72-d2a13ea726718ca9.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:41:36Z" - latency: 7.765235ms message: 'load-balancer-api-external: resolved host name a43366d352a4e4a2d9a605445fbedc72-d2a13ea726718ca9.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-29T22:41:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-29T21:45:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-134-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-134.ec2.internal uid: cba6fdf3-f793-4295-ab65-947aad936c21 resourceVersion: "167544" uid: 2a95e10c-5300-47fe-885c-c435502f1020 spec: sourcePod: network-check-source-6f78d59f99-zc52n targetEndpoint: a43366d352a4e4a2d9a605445fbedc72-d2a13ea726718ca9.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-29T21:51:36Z" message: 'load-balancer-api-internal: tcp connection to a43366d352a4e4a2d9a605445fbedc72-d2a13ea726718ca9.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 23.497191ms message: 'load-balancer-api-internal: tcp connection to a43366d352a4e4a2d9a605445fbedc72-d2a13ea726718ca9.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:45:36Z" - latency: 8.58866ms message: 'load-balancer-api-internal: resolved host name a43366d352a4e4a2d9a605445fbedc72-d2a13ea726718ca9.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-29T22:45:36Z" - latency: 25.838166ms message: 'load-balancer-api-internal: tcp connection to a43366d352a4e4a2d9a605445fbedc72-d2a13ea726718ca9.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:44:36Z" - latency: 6.884613ms message: 'load-balancer-api-internal: resolved host name a43366d352a4e4a2d9a605445fbedc72-d2a13ea726718ca9.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-29T22:44:36Z" - latency: 14.989245ms message: 'load-balancer-api-internal: tcp connection to a43366d352a4e4a2d9a605445fbedc72-d2a13ea726718ca9.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:43:36Z" - latency: 11.182301ms message: 'load-balancer-api-internal: resolved host name a43366d352a4e4a2d9a605445fbedc72-d2a13ea726718ca9.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-29T22:43:36Z" - latency: 18.690489ms message: 'load-balancer-api-internal: tcp connection to a43366d352a4e4a2d9a605445fbedc72-d2a13ea726718ca9.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:42:36Z" - latency: 9.095018ms message: 'load-balancer-api-internal: resolved host name a43366d352a4e4a2d9a605445fbedc72-d2a13ea726718ca9.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-29T22:42:36Z" - latency: 18.895336ms message: 'load-balancer-api-internal: tcp connection to a43366d352a4e4a2d9a605445fbedc72-d2a13ea726718ca9.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:41:36Z" - latency: 7.831965ms message: 'load-balancer-api-internal: resolved host name a43366d352a4e4a2d9a605445fbedc72-d2a13ea726718ca9.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-29T22:41:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-29T21:45:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-134-to-network-check-target-ip-10-0-128-100 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-134.ec2.internal uid: cba6fdf3-f793-4295-ab65-947aad936c21 resourceVersion: "175339" uid: 3d948346-2699-4600-9d1e-04411754a7f5 spec: sourcePod: network-check-source-6f78d59f99-zc52n targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-29T21:52:36Z" message: 'network-check-target-ip-10-0-128-100: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.949848ms message: 'network-check-target-ip-10-0-128-100: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:48:36Z" - latency: 2.231242ms message: 'network-check-target-ip-10-0-128-100: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:47:36Z" - latency: 2.562607ms message: 'network-check-target-ip-10-0-128-100: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:46:36Z" - latency: 2.40016ms message: 'network-check-target-ip-10-0-128-100: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:45:36Z" - latency: 2.12362ms message: 'network-check-target-ip-10-0-128-100: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:44:36Z" - latency: 4.275919ms message: 'network-check-target-ip-10-0-128-100: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:43:36Z" - latency: 2.880754ms message: 'network-check-target-ip-10-0-128-100: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:42:36Z" - latency: 2.163346ms message: 'network-check-target-ip-10-0-128-100: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:41:36Z" - latency: 2.289644ms message: 'network-check-target-ip-10-0-128-100: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:40:36Z" - latency: 2.701763ms message: 'network-check-target-ip-10-0-128-100: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:39:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-29T21:45:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-134-to-network-check-target-ip-10-0-130-134 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-134.ec2.internal uid: cba6fdf3-f793-4295-ab65-947aad936c21 resourceVersion: "175338" uid: 715452e2-0462-413a-9075-e9e9adc55dc2 spec: sourcePod: network-check-source-6f78d59f99-zc52n targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-29T21:52:36Z" message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 965.572µs message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:48:36Z" - latency: 1.18232ms message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:47:36Z" - latency: 2.502459ms message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:46:36Z" - latency: 1.125252ms message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:45:36Z" - latency: 960.807µs message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:44:36Z" - latency: 4.562284ms message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:43:36Z" - latency: 1.04874ms message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:42:36Z" - latency: 2.022232ms message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:41:36Z" - latency: 2.382008ms message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:40:36Z" - latency: 1.215597ms message: 'network-check-target-ip-10-0-130-134: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:39:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-29T21:45:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-134-to-network-check-target-ip-10-0-141-100 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-134.ec2.internal uid: cba6fdf3-f793-4295-ab65-947aad936c21 resourceVersion: "175340" uid: 839f2eb7-102b-4003-841f-ac077301e144 spec: sourcePod: network-check-source-6f78d59f99-zc52n targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-29T21:52:36Z" message: 'network-check-target-ip-10-0-141-100: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.545082ms message: 'network-check-target-ip-10-0-141-100: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:48:36Z" - latency: 2.552622ms message: 'network-check-target-ip-10-0-141-100: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:47:36Z" - latency: 2.132553ms message: 'network-check-target-ip-10-0-141-100: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:46:36Z" - latency: 2.697ms message: 'network-check-target-ip-10-0-141-100: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:45:36Z" - latency: 2.118478ms message: 'network-check-target-ip-10-0-141-100: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:44:36Z" - latency: 4.410589ms message: 'network-check-target-ip-10-0-141-100: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:43:36Z" - latency: 2.220945ms message: 'network-check-target-ip-10-0-141-100: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:42:36Z" - latency: 2.98697ms message: 'network-check-target-ip-10-0-141-100: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:41:36Z" - latency: 2.663122ms message: 'network-check-target-ip-10-0-141-100: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:40:36Z" - latency: 2.666897ms message: 'network-check-target-ip-10-0-141-100: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:39:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-29T21:45:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-134-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-134.ec2.internal uid: cba6fdf3-f793-4295-ab65-947aad936c21 resourceVersion: "167539" uid: 81106d0f-7d3d-4b6f-ba1e-7f06f7cd88bb spec: sourcePod: network-check-source-6f78d59f99-zc52n targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-29T21:51:36Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 905.348µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:45:36Z" - latency: 2.663983ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-29T22:45:36Z" - latency: 1.219575ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:44:36Z" - latency: 2.102746ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-29T22:44:36Z" - latency: 938.924µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:43:36Z" - latency: 4.352488ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-29T22:43:36Z" - latency: 1.230221ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:42:36Z" - latency: 2.67972ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-29T22:42:36Z" - latency: 1.027999ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-29T22:41:36Z" - latency: 2.89274ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-29T22:41:36Z" kind: List metadata: resourceVersion: ""