apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T20:10:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-130-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-130.ec2.internal uid: e6598eea-1ded-4a86-a4f5-fd4260e89508 resourceVersion: "18666" uid: 1041dbc8-701a-4257-bd31-c703b09dae41 spec: sourcePod: network-check-source-8894fc9bd-6m4mg targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-20T20:17:28Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.06415ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:24:28Z" - latency: 981.176µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:23:28Z" - latency: 1.050427ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:22:28Z" - latency: 847.968µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:21:28Z" - latency: 940.75µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:20:28Z" - latency: 1.085164ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:19:28Z" - latency: 949.134µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:18:28Z" - latency: 912.124µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:17:28Z" - latency: 1.134357ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:16:28Z" - latency: 936.785µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:15:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T20:10:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-130-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-130.ec2.internal uid: e6598eea-1ded-4a86-a4f5-fd4260e89508 resourceVersion: "20773" uid: 684502d2-c5d4-4777-8248-c749077e3a83 spec: sourcePod: network-check-source-8894fc9bd-6m4mg targetEndpoint: a2518cc3fa8d24cac9d060dd995cf11a-800c2023e1f4abc8.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-20T20:16:28Z" message: 'load-balancer-api-external: tcp connection to a2518cc3fa8d24cac9d060dd995cf11a-800c2023e1f4abc8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.962727ms message: 'load-balancer-api-external: tcp connection to a2518cc3fa8d24cac9d060dd995cf11a-800c2023e1f4abc8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:28:28Z" - latency: 7.235866ms message: 'load-balancer-api-external: resolved host name a2518cc3fa8d24cac9d060dd995cf11a-800c2023e1f4abc8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T20:28:28Z" - latency: 3.753072ms message: 'load-balancer-api-external: tcp connection to a2518cc3fa8d24cac9d060dd995cf11a-800c2023e1f4abc8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:27:28Z" - latency: 7.022584ms message: 'load-balancer-api-external: resolved host name a2518cc3fa8d24cac9d060dd995cf11a-800c2023e1f4abc8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T20:27:28Z" - latency: 4.668938ms message: 'load-balancer-api-external: tcp connection to a2518cc3fa8d24cac9d060dd995cf11a-800c2023e1f4abc8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:26:28Z" - latency: 6.507918ms message: 'load-balancer-api-external: resolved host name a2518cc3fa8d24cac9d060dd995cf11a-800c2023e1f4abc8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T20:26:28Z" - latency: 4.058544ms message: 'load-balancer-api-external: tcp connection to a2518cc3fa8d24cac9d060dd995cf11a-800c2023e1f4abc8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:25:28Z" - latency: 6.567985ms message: 'load-balancer-api-external: resolved host name a2518cc3fa8d24cac9d060dd995cf11a-800c2023e1f4abc8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T20:25:28Z" - latency: 4.594039ms message: 'load-balancer-api-external: tcp connection to a2518cc3fa8d24cac9d060dd995cf11a-800c2023e1f4abc8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:24:28Z" - latency: 7.015598ms message: 'load-balancer-api-external: resolved host name a2518cc3fa8d24cac9d060dd995cf11a-800c2023e1f4abc8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T20:24:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T20:10:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-130-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-130.ec2.internal uid: e6598eea-1ded-4a86-a4f5-fd4260e89508 resourceVersion: "20774" uid: 8f1dbda1-d5ec-4629-9732-1352914a8b3c spec: sourcePod: network-check-source-8894fc9bd-6m4mg targetEndpoint: a2518cc3fa8d24cac9d060dd995cf11a-800c2023e1f4abc8.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-20T20:16:28Z" message: 'load-balancer-api-internal: tcp connection to a2518cc3fa8d24cac9d060dd995cf11a-800c2023e1f4abc8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.393524ms message: 'load-balancer-api-internal: tcp connection to a2518cc3fa8d24cac9d060dd995cf11a-800c2023e1f4abc8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:28:28Z" - latency: 7.441309ms message: 'load-balancer-api-internal: resolved host name a2518cc3fa8d24cac9d060dd995cf11a-800c2023e1f4abc8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T20:28:28Z" - latency: 3.712266ms message: 'load-balancer-api-internal: tcp connection to a2518cc3fa8d24cac9d060dd995cf11a-800c2023e1f4abc8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:27:28Z" - latency: 7.11455ms message: 'load-balancer-api-internal: resolved host name a2518cc3fa8d24cac9d060dd995cf11a-800c2023e1f4abc8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T20:27:28Z" - latency: 4.751206ms message: 'load-balancer-api-internal: tcp connection to a2518cc3fa8d24cac9d060dd995cf11a-800c2023e1f4abc8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:26:28Z" - latency: 6.555553ms message: 'load-balancer-api-internal: resolved host name a2518cc3fa8d24cac9d060dd995cf11a-800c2023e1f4abc8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T20:26:28Z" - latency: 4.13798ms message: 'load-balancer-api-internal: tcp connection to a2518cc3fa8d24cac9d060dd995cf11a-800c2023e1f4abc8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:25:28Z" - latency: 6.496936ms message: 'load-balancer-api-internal: resolved host name a2518cc3fa8d24cac9d060dd995cf11a-800c2023e1f4abc8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T20:25:28Z" - latency: 4.610727ms message: 'load-balancer-api-internal: tcp connection to a2518cc3fa8d24cac9d060dd995cf11a-800c2023e1f4abc8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:24:28Z" - latency: 6.98028ms message: 'load-balancer-api-internal: resolved host name a2518cc3fa8d24cac9d060dd995cf11a-800c2023e1f4abc8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T20:24:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T20:10:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-130-to-network-check-target-ip-10-0-135-184 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-130.ec2.internal uid: e6598eea-1ded-4a86-a4f5-fd4260e89508 resourceVersion: "18665" uid: 5bf91b7a-dea4-4de3-937f-19768dd803da spec: sourcePod: network-check-source-8894fc9bd-6m4mg targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-20T20:17:28Z" message: 'network-check-target-ip-10-0-135-184: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.250139ms message: 'network-check-target-ip-10-0-135-184: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:24:28Z" - latency: 2.208277ms message: 'network-check-target-ip-10-0-135-184: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:23:28Z" - latency: 2.239313ms message: 'network-check-target-ip-10-0-135-184: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:22:28Z" - latency: 2.304722ms message: 'network-check-target-ip-10-0-135-184: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:21:28Z" - latency: 2.327144ms message: 'network-check-target-ip-10-0-135-184: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:20:28Z" - latency: 2.137028ms message: 'network-check-target-ip-10-0-135-184: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:19:28Z" - latency: 2.351816ms message: 'network-check-target-ip-10-0-135-184: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:18:28Z" - latency: 2.127768ms message: 'network-check-target-ip-10-0-135-184: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:17:28Z" - latency: 2.456792ms message: 'network-check-target-ip-10-0-135-184: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:16:28Z" - latency: 2.337136ms message: 'network-check-target-ip-10-0-135-184: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:15:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T20:10:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-130-to-network-check-target-ip-10-0-136-158 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-130.ec2.internal uid: e6598eea-1ded-4a86-a4f5-fd4260e89508 resourceVersion: "18664" uid: 38319eb0-bdf4-4e63-aadd-7ddedc1bbac4 spec: sourcePod: network-check-source-8894fc9bd-6m4mg targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-20T20:17:28Z" message: 'network-check-target-ip-10-0-136-158: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.066536ms message: 'network-check-target-ip-10-0-136-158: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:24:28Z" - latency: 2.235436ms message: 'network-check-target-ip-10-0-136-158: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:23:28Z" - latency: 2.31899ms message: 'network-check-target-ip-10-0-136-158: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:22:28Z" - latency: 2.578742ms message: 'network-check-target-ip-10-0-136-158: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:21:28Z" - latency: 2.379402ms message: 'network-check-target-ip-10-0-136-158: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:20:28Z" - latency: 2.182454ms message: 'network-check-target-ip-10-0-136-158: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:19:28Z" - latency: 2.222563ms message: 'network-check-target-ip-10-0-136-158: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:18:28Z" - latency: 1.868449ms message: 'network-check-target-ip-10-0-136-158: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:17:28Z" - latency: 2.51688ms message: 'network-check-target-ip-10-0-136-158: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:16:28Z" - latency: 2.170014ms message: 'network-check-target-ip-10-0-136-158: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:15:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T20:10:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-130-to-network-check-target-ip-10-0-141-130 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-130.ec2.internal uid: e6598eea-1ded-4a86-a4f5-fd4260e89508 resourceVersion: "18663" uid: 2f266b22-5baf-42de-a53c-63251379b554 spec: sourcePod: network-check-source-8894fc9bd-6m4mg targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-20T20:17:28Z" message: 'network-check-target-ip-10-0-141-130: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.003255ms message: 'network-check-target-ip-10-0-141-130: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:24:28Z" - latency: 1.312562ms message: 'network-check-target-ip-10-0-141-130: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:23:28Z" - latency: 1.366037ms message: 'network-check-target-ip-10-0-141-130: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:22:28Z" - latency: 1.410296ms message: 'network-check-target-ip-10-0-141-130: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:21:28Z" - latency: 840.885µs message: 'network-check-target-ip-10-0-141-130: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:20:28Z" - latency: 1.018273ms message: 'network-check-target-ip-10-0-141-130: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:19:28Z" - latency: 943.972µs message: 'network-check-target-ip-10-0-141-130: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:18:28Z" - latency: 821.376µs message: 'network-check-target-ip-10-0-141-130: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:17:28Z" - latency: 1.05233ms message: 'network-check-target-ip-10-0-141-130: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:16:28Z" - latency: 906.962µs message: 'network-check-target-ip-10-0-141-130: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:15:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T20:10:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-130-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-130.ec2.internal uid: e6598eea-1ded-4a86-a4f5-fd4260e89508 resourceVersion: "20772" uid: a98ca222-2eff-4030-a4fb-53eef4106ba7 spec: sourcePod: network-check-source-8894fc9bd-6m4mg targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-20T20:16:28Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 890.149µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:28:28Z" - latency: 1.829283ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T20:28:28Z" - latency: 772.022µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:27:28Z" - latency: 2.027963ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T20:27:28Z" - latency: 797.119µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:26:28Z" - latency: 1.624011ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T20:26:28Z" - latency: 762.604µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:25:28Z" - latency: 1.557111ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T20:25:28Z" - latency: 1.178927ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:24:28Z" - latency: 1.918591ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T20:24:28Z" kind: List metadata: resourceVersion: ""