apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T07:54:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-123-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-123.us-east-2.compute.internal uid: 8d70e49a-1600-4b9c-b7a3-8f26cdb53f8f resourceVersion: "140338" uid: 63b65923-bad4-411e-9836-8e4c66a2d576 spec: sourcePod: network-check-source-6f78d59f99-fshz5 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-03T08:01:57Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.236983ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:43:57Z" - latency: 1.315281ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:42:57Z" - latency: 868.27µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:41:57Z" - latency: 853.352µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:40:57Z" - latency: 974.932µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:39:57Z" - latency: 1.472603ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:38:57Z" - latency: 971.16µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:37:57Z" - latency: 1.217826ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:36:57Z" - latency: 1.027869ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:35:57Z" - latency: 1.357789ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:34:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T07:54:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-123-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-123.us-east-2.compute.internal uid: 8d70e49a-1600-4b9c-b7a3-8f26cdb53f8f resourceVersion: "138658" uid: c5d23dab-2ce2-4a0a-8e4b-6b4635e2b635 spec: sourcePod: network-check-source-6f78d59f99-fshz5 targetEndpoint: a3799af8e2aa840c78fe57a30f80a07d-1484b8eda46e58c2.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T08:00:57Z" message: 'load-balancer-api-external: tcp connection to a3799af8e2aa840c78fe57a30f80a07d-1484b8eda46e58c2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.497105ms message: 'load-balancer-api-external: tcp connection to a3799af8e2aa840c78fe57a30f80a07d-1484b8eda46e58c2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:42:57Z" - latency: 6.802333ms message: 'load-balancer-api-external: resolved host name a3799af8e2aa840c78fe57a30f80a07d-1484b8eda46e58c2.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T08:42:57Z" - latency: 7.356729ms message: 'load-balancer-api-external: tcp connection to a3799af8e2aa840c78fe57a30f80a07d-1484b8eda46e58c2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:41:57Z" - latency: 6.799228ms message: 'load-balancer-api-external: resolved host name a3799af8e2aa840c78fe57a30f80a07d-1484b8eda46e58c2.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T08:41:57Z" - latency: 7.388726ms message: 'load-balancer-api-external: tcp connection to a3799af8e2aa840c78fe57a30f80a07d-1484b8eda46e58c2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:40:57Z" - latency: 8.180041ms message: 'load-balancer-api-external: resolved host name a3799af8e2aa840c78fe57a30f80a07d-1484b8eda46e58c2.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T08:40:57Z" - latency: 5.80609ms message: 'load-balancer-api-external: tcp connection to a3799af8e2aa840c78fe57a30f80a07d-1484b8eda46e58c2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:39:57Z" - latency: 6.721869ms message: 'load-balancer-api-external: resolved host name a3799af8e2aa840c78fe57a30f80a07d-1484b8eda46e58c2.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T08:39:57Z" - latency: 5.466597ms message: 'load-balancer-api-external: tcp connection to a3799af8e2aa840c78fe57a30f80a07d-1484b8eda46e58c2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:38:57Z" - latency: 6.569391ms message: 'load-balancer-api-external: resolved host name a3799af8e2aa840c78fe57a30f80a07d-1484b8eda46e58c2.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T08:38:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T07:54:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-123-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-123.us-east-2.compute.internal uid: 8d70e49a-1600-4b9c-b7a3-8f26cdb53f8f resourceVersion: "138659" uid: 1173958e-33d9-4a7a-b2be-1aca4f3f57a3 spec: sourcePod: network-check-source-6f78d59f99-fshz5 targetEndpoint: a3799af8e2aa840c78fe57a30f80a07d-1484b8eda46e58c2.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T08:00:57Z" message: 'load-balancer-api-internal: tcp connection to a3799af8e2aa840c78fe57a30f80a07d-1484b8eda46e58c2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.513252ms message: 'load-balancer-api-internal: tcp connection to a3799af8e2aa840c78fe57a30f80a07d-1484b8eda46e58c2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:42:57Z" - latency: 6.781334ms message: 'load-balancer-api-internal: resolved host name a3799af8e2aa840c78fe57a30f80a07d-1484b8eda46e58c2.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T08:42:57Z" - latency: 6.795876ms message: 'load-balancer-api-internal: tcp connection to a3799af8e2aa840c78fe57a30f80a07d-1484b8eda46e58c2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:41:57Z" - latency: 6.835648ms message: 'load-balancer-api-internal: resolved host name a3799af8e2aa840c78fe57a30f80a07d-1484b8eda46e58c2.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T08:41:57Z" - latency: 7.499944ms message: 'load-balancer-api-internal: tcp connection to a3799af8e2aa840c78fe57a30f80a07d-1484b8eda46e58c2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:40:57Z" - latency: 8.096122ms message: 'load-balancer-api-internal: resolved host name a3799af8e2aa840c78fe57a30f80a07d-1484b8eda46e58c2.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T08:40:57Z" - latency: 5.799548ms message: 'load-balancer-api-internal: tcp connection to a3799af8e2aa840c78fe57a30f80a07d-1484b8eda46e58c2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:39:57Z" - latency: 6.768979ms message: 'load-balancer-api-internal: resolved host name a3799af8e2aa840c78fe57a30f80a07d-1484b8eda46e58c2.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T08:39:57Z" - latency: 5.690309ms message: 'load-balancer-api-internal: tcp connection to a3799af8e2aa840c78fe57a30f80a07d-1484b8eda46e58c2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:38:57Z" - latency: 6.509146ms message: 'load-balancer-api-internal: resolved host name a3799af8e2aa840c78fe57a30f80a07d-1484b8eda46e58c2.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T08:38:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T07:54:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-123-to-network-check-target-ip-10-0-140-123 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-123.us-east-2.compute.internal uid: 8d70e49a-1600-4b9c-b7a3-8f26cdb53f8f resourceVersion: "140336" uid: f1b02461-803b-4f02-a0ab-f7870e0ede87 spec: sourcePod: network-check-source-6f78d59f99-fshz5 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-03T08:01:57Z" message: 'network-check-target-ip-10-0-140-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.126597ms message: 'network-check-target-ip-10-0-140-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:43:57Z" - latency: 994.339µs message: 'network-check-target-ip-10-0-140-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:42:57Z" - latency: 1.151324ms message: 'network-check-target-ip-10-0-140-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:41:57Z" - latency: 1.248645ms message: 'network-check-target-ip-10-0-140-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:40:57Z" - latency: 943.538µs message: 'network-check-target-ip-10-0-140-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:39:57Z" - latency: 966.983µs message: 'network-check-target-ip-10-0-140-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:38:57Z" - latency: 1.357614ms message: 'network-check-target-ip-10-0-140-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:37:57Z" - latency: 789.572µs message: 'network-check-target-ip-10-0-140-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:36:57Z" - latency: 1.234866ms message: 'network-check-target-ip-10-0-140-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:35:57Z" - latency: 1.599971ms message: 'network-check-target-ip-10-0-140-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:34:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T07:54:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-123-to-network-check-target-ip-10-0-140-232 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-123.us-east-2.compute.internal uid: 8d70e49a-1600-4b9c-b7a3-8f26cdb53f8f resourceVersion: "140337" uid: 7171a596-ce32-4f46-b704-457d5b44a60c spec: sourcePod: network-check-source-6f78d59f99-fshz5 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-03T08:01:57Z" message: 'network-check-target-ip-10-0-140-232: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.278442ms message: 'network-check-target-ip-10-0-140-232: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:43:57Z" - latency: 2.334953ms message: 'network-check-target-ip-10-0-140-232: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:42:57Z" - latency: 2.239025ms message: 'network-check-target-ip-10-0-140-232: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:41:57Z" - latency: 2.201458ms message: 'network-check-target-ip-10-0-140-232: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:40:57Z" - latency: 2.285425ms message: 'network-check-target-ip-10-0-140-232: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:39:57Z" - latency: 2.20823ms message: 'network-check-target-ip-10-0-140-232: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:38:57Z" - latency: 2.290638ms message: 'network-check-target-ip-10-0-140-232: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:37:57Z" - latency: 2.31284ms message: 'network-check-target-ip-10-0-140-232: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:36:57Z" - latency: 2.141265ms message: 'network-check-target-ip-10-0-140-232: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:35:57Z" - latency: 2.326335ms message: 'network-check-target-ip-10-0-140-232: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:34:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T07:54:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-123-to-network-check-target-ip-10-0-143-47 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-123.us-east-2.compute.internal uid: 8d70e49a-1600-4b9c-b7a3-8f26cdb53f8f resourceVersion: "140358" uid: cdb15b64-44df-4205-8358-117260209396 spec: sourcePod: network-check-source-6f78d59f99-fshz5 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-03T08:01:59Z" message: 'network-check-target-ip-10-0-143-47: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.015779ms message: 'network-check-target-ip-10-0-143-47: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:43:59Z" - latency: 2.463079ms message: 'network-check-target-ip-10-0-143-47: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:42:59Z" - latency: 693.045µs message: 'network-check-target-ip-10-0-143-47: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:41:59Z" - latency: 2.540705ms message: 'network-check-target-ip-10-0-143-47: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:40:59Z" - latency: 2.503382ms message: 'network-check-target-ip-10-0-143-47: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:39:59Z" - latency: 855.52µs message: 'network-check-target-ip-10-0-143-47: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:38:59Z" - latency: 1.153445ms message: 'network-check-target-ip-10-0-143-47: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:37:59Z" - latency: 2.637671ms message: 'network-check-target-ip-10-0-143-47: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:36:59Z" - latency: 929.146µs message: 'network-check-target-ip-10-0-143-47: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:35:59Z" - latency: 2.592653ms message: 'network-check-target-ip-10-0-143-47: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:34:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T07:54:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-123-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-123.us-east-2.compute.internal uid: 8d70e49a-1600-4b9c-b7a3-8f26cdb53f8f resourceVersion: "138656" uid: 4feb9379-e314-46d3-ad5f-5e5e19e5c901 spec: sourcePod: network-check-source-6f78d59f99-fshz5 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-03T08:00:57Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.094381ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:42:57Z" - latency: 1.83226ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T08:42:57Z" - latency: 2.364839ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:41:57Z" - latency: 1.898094ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T08:41:57Z" - latency: 969.277µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:40:57Z" - latency: 1.695909ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T08:40:57Z" - latency: 1.252184ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:39:57Z" - latency: 1.834631ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T08:39:57Z" - latency: 1.813577ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T08:38:57Z" - latency: 1.810214ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T08:38:57Z" kind: List metadata: resourceVersion: ""