apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:58:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-12-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-12.ec2.internal uid: 1f5eef80-2d82-4d36-b1a9-8fbb93034083 resourceVersion: "18360" uid: c86f0289-edae-4062-81d4-c93b3a54ef87 spec: sourcePod: network-check-source-6f78d59f99-25288 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T22:05:35Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 861.851µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:19:35Z" - latency: 1.474534ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:18:35Z" - latency: 914.381µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:17:35Z" - latency: 949.811µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:16:35Z" - latency: 1.249278ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:15:35Z" - latency: 1.065586ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:14:35Z" - latency: 1.257477ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:13:35Z" - latency: 1.003389ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:12:35Z" - latency: 1.172358ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:11:35Z" - latency: 1.172507ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:10:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:58:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-12-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-12.ec2.internal uid: 1f5eef80-2d82-4d36-b1a9-8fbb93034083 resourceVersion: "19642" uid: 1e1de3f7-4581-4077-9fc1-715f8e1bad0f spec: sourcePod: network-check-source-6f78d59f99-25288 targetEndpoint: a1af969ac861446698145781d8090eb3-7ba38a36b6bfaf3c.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T22:04:35Z" message: 'load-balancer-api-external: tcp connection to a1af969ac861446698145781d8090eb3-7ba38a36b6bfaf3c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 14.27879ms message: 'load-balancer-api-external: tcp connection to a1af969ac861446698145781d8090eb3-7ba38a36b6bfaf3c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:22:35Z" - latency: 6.656623ms message: 'load-balancer-api-external: resolved host name a1af969ac861446698145781d8090eb3-7ba38a36b6bfaf3c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:22:35Z" - latency: 15.460303ms message: 'load-balancer-api-external: tcp connection to a1af969ac861446698145781d8090eb3-7ba38a36b6bfaf3c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:21:35Z" - latency: 7.199336ms message: 'load-balancer-api-external: resolved host name a1af969ac861446698145781d8090eb3-7ba38a36b6bfaf3c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:21:35Z" - latency: 17.554888ms message: 'load-balancer-api-external: tcp connection to a1af969ac861446698145781d8090eb3-7ba38a36b6bfaf3c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:20:35Z" - latency: 6.548174ms message: 'load-balancer-api-external: resolved host name a1af969ac861446698145781d8090eb3-7ba38a36b6bfaf3c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:20:35Z" - latency: 15.564945ms message: 'load-balancer-api-external: tcp connection to a1af969ac861446698145781d8090eb3-7ba38a36b6bfaf3c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:19:35Z" - latency: 8.219468ms message: 'load-balancer-api-external: resolved host name a1af969ac861446698145781d8090eb3-7ba38a36b6bfaf3c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:19:35Z" - latency: 17.719611ms message: 'load-balancer-api-external: tcp connection to a1af969ac861446698145781d8090eb3-7ba38a36b6bfaf3c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:18:35Z" - latency: 6.28736ms message: 'load-balancer-api-external: resolved host name a1af969ac861446698145781d8090eb3-7ba38a36b6bfaf3c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:18:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:58:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-12-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-12.ec2.internal uid: 1f5eef80-2d82-4d36-b1a9-8fbb93034083 resourceVersion: "19643" uid: c4c98e63-f42d-4983-bccf-253f0c397e5b spec: sourcePod: network-check-source-6f78d59f99-25288 targetEndpoint: a1af969ac861446698145781d8090eb3-7ba38a36b6bfaf3c.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T22:04:35Z" message: 'load-balancer-api-internal: tcp connection to a1af969ac861446698145781d8090eb3-7ba38a36b6bfaf3c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 17.045667ms message: 'load-balancer-api-internal: tcp connection to a1af969ac861446698145781d8090eb3-7ba38a36b6bfaf3c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:22:35Z" - latency: 6.684298ms message: 'load-balancer-api-internal: resolved host name a1af969ac861446698145781d8090eb3-7ba38a36b6bfaf3c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:22:35Z" - latency: 15.525159ms message: 'load-balancer-api-internal: tcp connection to a1af969ac861446698145781d8090eb3-7ba38a36b6bfaf3c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:21:35Z" - latency: 7.104946ms message: 'load-balancer-api-internal: resolved host name a1af969ac861446698145781d8090eb3-7ba38a36b6bfaf3c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:21:35Z" - latency: 15.614426ms message: 'load-balancer-api-internal: tcp connection to a1af969ac861446698145781d8090eb3-7ba38a36b6bfaf3c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:20:35Z" - latency: 6.604707ms message: 'load-balancer-api-internal: resolved host name a1af969ac861446698145781d8090eb3-7ba38a36b6bfaf3c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:20:35Z" - latency: 14.12575ms message: 'load-balancer-api-internal: tcp connection to a1af969ac861446698145781d8090eb3-7ba38a36b6bfaf3c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:19:35Z" - latency: 8.133882ms message: 'load-balancer-api-internal: resolved host name a1af969ac861446698145781d8090eb3-7ba38a36b6bfaf3c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:19:35Z" - latency: 18.152952ms message: 'load-balancer-api-internal: tcp connection to a1af969ac861446698145781d8090eb3-7ba38a36b6bfaf3c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:18:35Z" - latency: 6.356917ms message: 'load-balancer-api-internal: resolved host name a1af969ac861446698145781d8090eb3-7ba38a36b6bfaf3c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:18:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:58:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-12-to-network-check-target-ip-10-0-135-200 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-12.ec2.internal uid: 1f5eef80-2d82-4d36-b1a9-8fbb93034083 resourceVersion: "18359" uid: 1abc9df9-aa79-4bc2-a97f-6c714332562c spec: sourcePod: network-check-source-6f78d59f99-25288 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T22:05:35Z" message: 'network-check-target-ip-10-0-135-200: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.418473ms message: 'network-check-target-ip-10-0-135-200: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:19:35Z" - latency: 2.31442ms message: 'network-check-target-ip-10-0-135-200: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:18:35Z" - latency: 2.10129ms message: 'network-check-target-ip-10-0-135-200: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:17:35Z" - latency: 2.106012ms message: 'network-check-target-ip-10-0-135-200: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:16:35Z" - latency: 2.3166ms message: 'network-check-target-ip-10-0-135-200: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:15:35Z" - latency: 2.471647ms message: 'network-check-target-ip-10-0-135-200: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:14:35Z" - latency: 2.403545ms message: 'network-check-target-ip-10-0-135-200: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:13:35Z" - latency: 2.305276ms message: 'network-check-target-ip-10-0-135-200: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:12:35Z" - latency: 2.440176ms message: 'network-check-target-ip-10-0-135-200: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:11:35Z" - latency: 2.324019ms message: 'network-check-target-ip-10-0-135-200: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:10:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:58:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-12-to-network-check-target-ip-10-0-143-12 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-12.ec2.internal uid: 1f5eef80-2d82-4d36-b1a9-8fbb93034083 resourceVersion: "18357" uid: 8c52d129-a5f4-4ace-8f4f-689daef2ade9 spec: sourcePod: network-check-source-6f78d59f99-25288 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-30T22:05:35Z" message: 'network-check-target-ip-10-0-143-12: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 779.059µs message: 'network-check-target-ip-10-0-143-12: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:19:35Z" - latency: 1.007886ms message: 'network-check-target-ip-10-0-143-12: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:18:35Z" - latency: 778.729µs message: 'network-check-target-ip-10-0-143-12: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:17:35Z" - latency: 1.421406ms message: 'network-check-target-ip-10-0-143-12: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:16:35Z" - latency: 877.931µs message: 'network-check-target-ip-10-0-143-12: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:15:35Z" - latency: 1.313095ms message: 'network-check-target-ip-10-0-143-12: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:14:35Z" - latency: 1.376015ms message: 'network-check-target-ip-10-0-143-12: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:13:35Z" - latency: 787.103µs message: 'network-check-target-ip-10-0-143-12: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:12:35Z" - latency: 1.507568ms message: 'network-check-target-ip-10-0-143-12: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:11:35Z" - latency: 1.29147ms message: 'network-check-target-ip-10-0-143-12: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:10:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:58:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-12-to-network-check-target-ip-10-0-143-246 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-12.ec2.internal uid: 1f5eef80-2d82-4d36-b1a9-8fbb93034083 resourceVersion: "18358" uid: bcd6d71a-a828-4ff4-8805-e66ec8b48feb spec: sourcePod: network-check-source-6f78d59f99-25288 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-30T22:05:35Z" message: 'network-check-target-ip-10-0-143-246: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.939338ms message: 'network-check-target-ip-10-0-143-246: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:19:35Z" - latency: 1.850481ms message: 'network-check-target-ip-10-0-143-246: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:18:35Z" - latency: 1.706334ms message: 'network-check-target-ip-10-0-143-246: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:17:35Z" - latency: 1.939429ms message: 'network-check-target-ip-10-0-143-246: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:16:35Z" - latency: 2.002814ms message: 'network-check-target-ip-10-0-143-246: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:15:35Z" - latency: 2.183656ms message: 'network-check-target-ip-10-0-143-246: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:14:35Z" - latency: 1.730886ms message: 'network-check-target-ip-10-0-143-246: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:13:35Z" - latency: 2.079068ms message: 'network-check-target-ip-10-0-143-246: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:12:35Z" - latency: 1.987376ms message: 'network-check-target-ip-10-0-143-246: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:11:35Z" - latency: 1.980529ms message: 'network-check-target-ip-10-0-143-246: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:10:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:58:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-12-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-12.ec2.internal uid: 1f5eef80-2d82-4d36-b1a9-8fbb93034083 resourceVersion: "19641" uid: caf2ce91-6b1c-4fa0-b38b-cec5d45184e7 spec: sourcePod: network-check-source-6f78d59f99-25288 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T22:04:35Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 811.127µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:22:35Z" - latency: 1.911172ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:22:35Z" - latency: 761.186µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:21:35Z" - latency: 1.816853ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:21:35Z" - latency: 894.141µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:20:35Z" - latency: 1.777037ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:20:35Z" - latency: 1.046795ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:19:35Z" - latency: 1.780194ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:19:35Z" - latency: 854.053µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:18:35Z" - latency: 1.870068ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:18:35Z" kind: List metadata: resourceVersion: ""