apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T14:10:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-64-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-64.ec2.internal uid: 3599e800-89a5-4835-8cb5-a68e84258046 resourceVersion: "54570" uid: a8798ff0-69a9-40f0-9a34-c52314d7bdcb spec: sourcePod: network-check-source-869dcfcdcd-2ftqc targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-10T14:17:39Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 812.761µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:45:39Z" - latency: 957.351µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:44:39Z" - latency: 1.166889ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:43:39Z" - latency: 1.384606ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:42:39Z" - latency: 1.15081ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:41:39Z" - latency: 1.117122ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:40:39Z" - latency: 1.156072ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:39:39Z" - latency: 1.186196ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:38:39Z" - latency: 859.519µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:37:39Z" - latency: 931.248µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:36:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T14:10:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-64-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-64.ec2.internal uid: 3599e800-89a5-4835-8cb5-a68e84258046 resourceVersion: "55732" uid: f8a897d2-1ebe-4a49-83ac-f32fcdaa228f spec: sourcePod: network-check-source-869dcfcdcd-2ftqc targetEndpoint: a538a881eb47f41d0a04fd0760ca2ce7-cf3a7e48ab415dcd.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T14:16:39Z" message: 'load-balancer-api-external: tcp connection to a538a881eb47f41d0a04fd0760ca2ce7-cf3a7e48ab415dcd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.167394ms message: 'load-balancer-api-external: tcp connection to a538a881eb47f41d0a04fd0760ca2ce7-cf3a7e48ab415dcd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:46:39Z" - latency: 6.588272ms message: 'load-balancer-api-external: resolved host name a538a881eb47f41d0a04fd0760ca2ce7-cf3a7e48ab415dcd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T14:46:39Z" - latency: 4.210175ms message: 'load-balancer-api-external: tcp connection to a538a881eb47f41d0a04fd0760ca2ce7-cf3a7e48ab415dcd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:45:39Z" - latency: 7.313924ms message: 'load-balancer-api-external: resolved host name a538a881eb47f41d0a04fd0760ca2ce7-cf3a7e48ab415dcd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T14:45:39Z" - latency: 4.246053ms message: 'load-balancer-api-external: tcp connection to a538a881eb47f41d0a04fd0760ca2ce7-cf3a7e48ab415dcd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:44:39Z" - latency: 5.651423ms message: 'load-balancer-api-external: resolved host name a538a881eb47f41d0a04fd0760ca2ce7-cf3a7e48ab415dcd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T14:44:39Z" - latency: 4.055927ms message: 'load-balancer-api-external: tcp connection to a538a881eb47f41d0a04fd0760ca2ce7-cf3a7e48ab415dcd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:43:39Z" - latency: 7.34942ms message: 'load-balancer-api-external: resolved host name a538a881eb47f41d0a04fd0760ca2ce7-cf3a7e48ab415dcd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T14:43:39Z" - latency: 4.540472ms message: 'load-balancer-api-external: tcp connection to a538a881eb47f41d0a04fd0760ca2ce7-cf3a7e48ab415dcd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:42:39Z" - latency: 6.54601ms message: 'load-balancer-api-external: resolved host name a538a881eb47f41d0a04fd0760ca2ce7-cf3a7e48ab415dcd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T14:42:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T14:10:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-64-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-64.ec2.internal uid: 3599e800-89a5-4835-8cb5-a68e84258046 resourceVersion: "55734" uid: eae0e78c-ff4c-444c-af25-0d8cfc5b486d spec: sourcePod: network-check-source-869dcfcdcd-2ftqc targetEndpoint: a538a881eb47f41d0a04fd0760ca2ce7-cf3a7e48ab415dcd.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T14:16:39Z" message: 'load-balancer-api-internal: tcp connection to a538a881eb47f41d0a04fd0760ca2ce7-cf3a7e48ab415dcd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.903676ms message: 'load-balancer-api-internal: tcp connection to a538a881eb47f41d0a04fd0760ca2ce7-cf3a7e48ab415dcd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:46:39Z" - latency: 6.652088ms message: 'load-balancer-api-internal: resolved host name a538a881eb47f41d0a04fd0760ca2ce7-cf3a7e48ab415dcd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T14:46:39Z" - latency: 4.214063ms message: 'load-balancer-api-internal: tcp connection to a538a881eb47f41d0a04fd0760ca2ce7-cf3a7e48ab415dcd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:45:39Z" - latency: 7.41404ms message: 'load-balancer-api-internal: resolved host name a538a881eb47f41d0a04fd0760ca2ce7-cf3a7e48ab415dcd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T14:45:39Z" - latency: 4.205872ms message: 'load-balancer-api-internal: tcp connection to a538a881eb47f41d0a04fd0760ca2ce7-cf3a7e48ab415dcd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:44:39Z" - latency: 5.688356ms message: 'load-balancer-api-internal: resolved host name a538a881eb47f41d0a04fd0760ca2ce7-cf3a7e48ab415dcd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T14:44:39Z" - latency: 4.087346ms message: 'load-balancer-api-internal: tcp connection to a538a881eb47f41d0a04fd0760ca2ce7-cf3a7e48ab415dcd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:43:39Z" - latency: 7.319188ms message: 'load-balancer-api-internal: resolved host name a538a881eb47f41d0a04fd0760ca2ce7-cf3a7e48ab415dcd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T14:43:39Z" - latency: 4.600834ms message: 'load-balancer-api-internal: tcp connection to a538a881eb47f41d0a04fd0760ca2ce7-cf3a7e48ab415dcd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:42:39Z" - latency: 6.5509ms message: 'load-balancer-api-internal: resolved host name a538a881eb47f41d0a04fd0760ca2ce7-cf3a7e48ab415dcd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T14:42:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T14:10:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-64-to-network-check-target-ip-10-0-135-64 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-64.ec2.internal uid: 3599e800-89a5-4835-8cb5-a68e84258046 resourceVersion: "54568" uid: ab3c8d37-3fd3-4788-beab-200f6e2deef2 spec: sourcePod: network-check-source-869dcfcdcd-2ftqc targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-10T14:17:39Z" message: 'network-check-target-ip-10-0-135-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 959.551µs message: 'network-check-target-ip-10-0-135-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:45:39Z" - latency: 979.215µs message: 'network-check-target-ip-10-0-135-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:44:39Z" - latency: 1.422362ms message: 'network-check-target-ip-10-0-135-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:43:39Z" - latency: 1.544871ms message: 'network-check-target-ip-10-0-135-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:42:39Z" - latency: 1.611508ms message: 'network-check-target-ip-10-0-135-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:41:39Z" - latency: 1.018002ms message: 'network-check-target-ip-10-0-135-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:40:39Z" - latency: 952.206µs message: 'network-check-target-ip-10-0-135-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:39:39Z" - latency: 1.470431ms message: 'network-check-target-ip-10-0-135-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:38:39Z" - latency: 873.015µs message: 'network-check-target-ip-10-0-135-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:37:39Z" - latency: 996.013µs message: 'network-check-target-ip-10-0-135-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:36:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T14:10:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-64-to-network-check-target-ip-10-0-142-2 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-64.ec2.internal uid: 3599e800-89a5-4835-8cb5-a68e84258046 resourceVersion: "54567" uid: 8e41a4f2-ae88-4d4a-a107-fe724e039f15 spec: sourcePod: network-check-source-869dcfcdcd-2ftqc targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-10T14:17:39Z" message: 'network-check-target-ip-10-0-142-2: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.968239ms message: 'network-check-target-ip-10-0-142-2: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:45:39Z" - latency: 2.262646ms message: 'network-check-target-ip-10-0-142-2: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:44:39Z" - latency: 2.1412ms message: 'network-check-target-ip-10-0-142-2: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:43:39Z" - latency: 2.243412ms message: 'network-check-target-ip-10-0-142-2: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:42:39Z" - latency: 2.981312ms message: 'network-check-target-ip-10-0-142-2: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:41:39Z" - latency: 2.710961ms message: 'network-check-target-ip-10-0-142-2: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:40:39Z" - latency: 2.350561ms message: 'network-check-target-ip-10-0-142-2: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:39:39Z" - latency: 2.606975ms message: 'network-check-target-ip-10-0-142-2: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:38:39Z" - latency: 2.36606ms message: 'network-check-target-ip-10-0-142-2: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:37:39Z" - latency: 2.082414ms message: 'network-check-target-ip-10-0-142-2: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:36:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T14:10:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-64-to-network-check-target-ip-10-0-143-123 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-64.ec2.internal uid: 3599e800-89a5-4835-8cb5-a68e84258046 resourceVersion: "54569" uid: eac1240f-4093-4b71-9263-1f2f8168162b spec: sourcePod: network-check-source-869dcfcdcd-2ftqc targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-10T14:17:39Z" message: 'network-check-target-ip-10-0-143-123: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.908111ms message: 'network-check-target-ip-10-0-143-123: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:45:39Z" - latency: 2.176251ms message: 'network-check-target-ip-10-0-143-123: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:44:39Z" - latency: 2.191119ms message: 'network-check-target-ip-10-0-143-123: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:43:39Z" - latency: 2.012984ms message: 'network-check-target-ip-10-0-143-123: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:42:39Z" - latency: 2.511321ms message: 'network-check-target-ip-10-0-143-123: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:41:39Z" - latency: 2.173508ms message: 'network-check-target-ip-10-0-143-123: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:40:39Z" - latency: 2.269209ms message: 'network-check-target-ip-10-0-143-123: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:39:39Z" - latency: 2.567377ms message: 'network-check-target-ip-10-0-143-123: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:38:39Z" - latency: 1.952836ms message: 'network-check-target-ip-10-0-143-123: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:37:39Z" - latency: 2.008577ms message: 'network-check-target-ip-10-0-143-123: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:36:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T14:10:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-64-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-64.ec2.internal uid: 3599e800-89a5-4835-8cb5-a68e84258046 resourceVersion: "55730" uid: abf0f495-5550-43c5-b65a-135492e18264 spec: sourcePod: network-check-source-869dcfcdcd-2ftqc targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-10T14:16:39Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 949.024µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:46:39Z" - latency: 1.737321ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T14:46:39Z" - latency: 810.817µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:45:39Z" - latency: 1.907803ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T14:45:39Z" - latency: 1.280344ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:44:39Z" - latency: 1.601698ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T14:44:39Z" - latency: 1.140753ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:43:39Z" - latency: 1.523564ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T14:43:39Z" - latency: 876.231µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T14:42:39Z" - latency: 1.825399ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T14:42:39Z" kind: List metadata: resourceVersion: ""