apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T00:42:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-107-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-107.us-east-2.compute.internal uid: 575cd8a2-9626-4a5f-b5cc-ca9f9774bb4e resourceVersion: "236599" uid: 1cf592e9-a19d-47e3-bebd-5436d3fa4a97 spec: sourcePod: network-check-source-6f78d59f99-z5f9s targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-03T00:49:27Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.196119ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T02:06:27Z" - latency: 13.633795ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T02:05:27Z" - latency: 964.792µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T02:04:27Z" - latency: 1.079743ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T02:03:27Z" - latency: 1.231238ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T02:02:27Z" - latency: 1.392541ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T02:01:27Z" - latency: 1.273709ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T02:00:27Z" - latency: 1.6709ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:59:27Z" - latency: 1.201636ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:58:27Z" - latency: 1.175635ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:57:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T00:42:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-107-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-107.us-east-2.compute.internal uid: 575cd8a2-9626-4a5f-b5cc-ca9f9774bb4e resourceVersion: "236600" uid: 8be3deba-2b31-4bfd-81fd-b57398add0b5 spec: sourcePod: network-check-source-6f78d59f99-z5f9s targetEndpoint: a5a811d24c7c444d185befcbe55e66ce-56158406077f4c60.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T00:48:27Z" message: 'load-balancer-api-external: tcp connection to a5a811d24c7c444d185befcbe55e66ce-56158406077f4c60.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.852652ms message: 'load-balancer-api-external: tcp connection to a5a811d24c7c444d185befcbe55e66ce-56158406077f4c60.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T02:06:27Z" - latency: 8.157068ms message: 'load-balancer-api-external: resolved host name a5a811d24c7c444d185befcbe55e66ce-56158406077f4c60.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T02:06:27Z" - latency: 7.199036ms message: 'load-balancer-api-external: tcp connection to a5a811d24c7c444d185befcbe55e66ce-56158406077f4c60.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T02:05:27Z" - latency: 36.963044ms message: 'load-balancer-api-external: resolved host name a5a811d24c7c444d185befcbe55e66ce-56158406077f4c60.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T02:05:27Z" - latency: 4.976924ms message: 'load-balancer-api-external: tcp connection to a5a811d24c7c444d185befcbe55e66ce-56158406077f4c60.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T02:04:27Z" - latency: 9.977402ms message: 'load-balancer-api-external: resolved host name a5a811d24c7c444d185befcbe55e66ce-56158406077f4c60.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T02:04:27Z" - latency: 5.165181ms message: 'load-balancer-api-external: tcp connection to a5a811d24c7c444d185befcbe55e66ce-56158406077f4c60.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T02:03:27Z" - latency: 8.373515ms message: 'load-balancer-api-external: resolved host name a5a811d24c7c444d185befcbe55e66ce-56158406077f4c60.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T02:03:27Z" - latency: 5.281514ms message: 'load-balancer-api-external: tcp connection to a5a811d24c7c444d185befcbe55e66ce-56158406077f4c60.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T02:02:27Z" - latency: 9.338647ms message: 'load-balancer-api-external: resolved host name a5a811d24c7c444d185befcbe55e66ce-56158406077f4c60.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T02:02:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T00:42:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-107-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-107.us-east-2.compute.internal uid: 575cd8a2-9626-4a5f-b5cc-ca9f9774bb4e resourceVersion: "236601" uid: 714b5703-6f5b-4b00-83a4-a8e26c34c298 spec: sourcePod: network-check-source-6f78d59f99-z5f9s targetEndpoint: a5a811d24c7c444d185befcbe55e66ce-56158406077f4c60.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T00:48:27Z" message: 'load-balancer-api-internal: tcp connection to a5a811d24c7c444d185befcbe55e66ce-56158406077f4c60.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.836741ms message: 'load-balancer-api-internal: tcp connection to a5a811d24c7c444d185befcbe55e66ce-56158406077f4c60.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T02:06:27Z" - latency: 8.072917ms message: 'load-balancer-api-internal: resolved host name a5a811d24c7c444d185befcbe55e66ce-56158406077f4c60.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T02:06:27Z" - latency: 10.409137ms message: 'load-balancer-api-internal: tcp connection to a5a811d24c7c444d185befcbe55e66ce-56158406077f4c60.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T02:05:27Z" - latency: 37.612626ms message: 'load-balancer-api-internal: resolved host name a5a811d24c7c444d185befcbe55e66ce-56158406077f4c60.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T02:05:27Z" - latency: 4.970706ms message: 'load-balancer-api-internal: tcp connection to a5a811d24c7c444d185befcbe55e66ce-56158406077f4c60.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T02:04:27Z" - latency: 9.932856ms message: 'load-balancer-api-internal: resolved host name a5a811d24c7c444d185befcbe55e66ce-56158406077f4c60.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T02:04:27Z" - latency: 5.136017ms message: 'load-balancer-api-internal: tcp connection to a5a811d24c7c444d185befcbe55e66ce-56158406077f4c60.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T02:03:27Z" - latency: 8.411481ms message: 'load-balancer-api-internal: resolved host name a5a811d24c7c444d185befcbe55e66ce-56158406077f4c60.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T02:03:27Z" - latency: 5.262898ms message: 'load-balancer-api-internal: tcp connection to a5a811d24c7c444d185befcbe55e66ce-56158406077f4c60.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T02:02:27Z" - latency: 9.271439ms message: 'load-balancer-api-internal: resolved host name a5a811d24c7c444d185befcbe55e66ce-56158406077f4c60.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T02:02:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T00:42:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-107-to-network-check-target-ip-10-0-133-217 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-107.us-east-2.compute.internal uid: 575cd8a2-9626-4a5f-b5cc-ca9f9774bb4e resourceVersion: "236596" uid: d11f7fe7-6971-4cf7-904e-e4dee0227079 spec: sourcePod: network-check-source-6f78d59f99-z5f9s targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-03T00:49:27Z" message: 'network-check-target-ip-10-0-133-217: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.164927ms message: 'network-check-target-ip-10-0-133-217: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T02:06:27Z" - latency: 14.282099ms message: 'network-check-target-ip-10-0-133-217: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T02:05:27Z" - latency: 2.186904ms message: 'network-check-target-ip-10-0-133-217: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T02:04:27Z" - latency: 2.392819ms message: 'network-check-target-ip-10-0-133-217: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T02:03:27Z" - latency: 2.119098ms message: 'network-check-target-ip-10-0-133-217: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T02:02:27Z" - latency: 2.545708ms message: 'network-check-target-ip-10-0-133-217: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T02:01:27Z" - latency: 2.432488ms message: 'network-check-target-ip-10-0-133-217: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T02:00:27Z" - latency: 2.146267ms message: 'network-check-target-ip-10-0-133-217: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:59:27Z" - latency: 2.316906ms message: 'network-check-target-ip-10-0-133-217: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:58:27Z" - latency: 2.119946ms message: 'network-check-target-ip-10-0-133-217: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:57:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T00:42:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-107-to-network-check-target-ip-10-0-136-112 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-107.us-east-2.compute.internal uid: 575cd8a2-9626-4a5f-b5cc-ca9f9774bb4e resourceVersion: "236597" uid: f54368e3-ab55-4631-abe0-73b7d11ed9ab spec: sourcePod: network-check-source-6f78d59f99-z5f9s targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-03T00:49:27Z" message: 'network-check-target-ip-10-0-136-112: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.720768ms message: 'network-check-target-ip-10-0-136-112: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T02:06:27Z" - latency: 13.756849ms message: 'network-check-target-ip-10-0-136-112: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T02:05:27Z" - latency: 2.385238ms message: 'network-check-target-ip-10-0-136-112: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T02:04:27Z" - latency: 2.405521ms message: 'network-check-target-ip-10-0-136-112: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T02:03:27Z" - latency: 2.265561ms message: 'network-check-target-ip-10-0-136-112: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T02:02:27Z" - latency: 2.419305ms message: 'network-check-target-ip-10-0-136-112: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T02:01:27Z" - latency: 2.426766ms message: 'network-check-target-ip-10-0-136-112: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T02:00:27Z" - latency: 2.325447ms message: 'network-check-target-ip-10-0-136-112: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:59:27Z" - latency: 2.293328ms message: 'network-check-target-ip-10-0-136-112: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:58:27Z" - latency: 2.299806ms message: 'network-check-target-ip-10-0-136-112: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:57:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T00:42:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-107-to-network-check-target-ip-10-0-140-107 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-107.us-east-2.compute.internal uid: 575cd8a2-9626-4a5f-b5cc-ca9f9774bb4e resourceVersion: "236595" uid: 3ebad645-6edc-4f0e-91e7-0364ca8a20d3 spec: sourcePod: network-check-source-6f78d59f99-z5f9s targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-03T00:49:27Z" message: 'network-check-target-ip-10-0-140-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.144875ms message: 'network-check-target-ip-10-0-140-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T02:06:27Z" - latency: 12.89301ms message: 'network-check-target-ip-10-0-140-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T02:05:27Z" - latency: 1.115478ms message: 'network-check-target-ip-10-0-140-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T02:04:27Z" - latency: 1.128682ms message: 'network-check-target-ip-10-0-140-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T02:03:27Z" - latency: 1.284428ms message: 'network-check-target-ip-10-0-140-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T02:02:27Z" - latency: 1.728605ms message: 'network-check-target-ip-10-0-140-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T02:01:27Z" - latency: 1.139535ms message: 'network-check-target-ip-10-0-140-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T02:00:27Z" - latency: 1.710502ms message: 'network-check-target-ip-10-0-140-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:59:27Z" - latency: 1.237865ms message: 'network-check-target-ip-10-0-140-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:58:27Z" - latency: 1.06031ms message: 'network-check-target-ip-10-0-140-107: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T01:57:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T00:42:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-107-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-107.us-east-2.compute.internal uid: 575cd8a2-9626-4a5f-b5cc-ca9f9774bb4e resourceVersion: "236598" uid: 28e99476-1648-4f74-a696-ed667d293050 spec: sourcePod: network-check-source-6f78d59f99-z5f9s targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-03T00:48:27Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.485454ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T02:06:27Z" - latency: 2.109342ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T02:06:27Z" - latency: 3.874043ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T02:05:27Z" - latency: 18.344126ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T02:05:27Z" - latency: 872.727µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T02:04:27Z" - latency: 2.478075ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T02:04:27Z" - latency: 1.011574ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T02:03:27Z" - latency: 1.882304ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T02:03:27Z" - latency: 818.809µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T02:02:27Z" - latency: 2.28013ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T02:02:27Z" kind: List metadata: resourceVersion: ""