apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T19:51:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-165-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-165.ec2.internal uid: ea870359-d734-43e6-818d-2eb57464d9a5 resourceVersion: "40796" uid: 4a7c8201-2207-47e2-876b-a7097830607f spec: sourcePod: network-check-source-7f44b6dd87-x29mj targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-26T19:58:52Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.328642ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:19:52Z" - latency: 1.172726ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:18:52Z" - latency: 1.342759ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:17:52Z" - latency: 1.184083ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:16:52Z" - latency: 983.233µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:15:52Z" - latency: 1.011537ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:14:52Z" - latency: 1.202739ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:13:52Z" - latency: 1.100576ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:12:52Z" - latency: 1.159096ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:11:52Z" - latency: 890.017µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:10:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T19:51:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-165-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-165.ec2.internal uid: ea870359-d734-43e6-818d-2eb57464d9a5 resourceVersion: "43237" uid: b843aaab-3e34-4489-be55-ecc6fee484f8 spec: sourcePod: network-check-source-7f44b6dd87-x29mj targetEndpoint: a9e568f1ec1bf4aebbb9bbb449910e14-8ce1ad4de08905e0.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-26T19:57:52Z" message: 'load-balancer-api-external: tcp connection to a9e568f1ec1bf4aebbb9bbb449910e14-8ce1ad4de08905e0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.651065ms message: 'load-balancer-api-external: tcp connection to a9e568f1ec1bf4aebbb9bbb449910e14-8ce1ad4de08905e0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:21:52Z" - latency: 6.327879ms message: 'load-balancer-api-external: resolved host name a9e568f1ec1bf4aebbb9bbb449910e14-8ce1ad4de08905e0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T20:21:52Z" - latency: 16.599505ms message: 'load-balancer-api-external: tcp connection to a9e568f1ec1bf4aebbb9bbb449910e14-8ce1ad4de08905e0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:20:52Z" - latency: 8.754511ms message: 'load-balancer-api-external: resolved host name a9e568f1ec1bf4aebbb9bbb449910e14-8ce1ad4de08905e0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T20:20:52Z" - latency: 5.259291ms message: 'load-balancer-api-external: tcp connection to a9e568f1ec1bf4aebbb9bbb449910e14-8ce1ad4de08905e0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:19:52Z" - latency: 6.446903ms message: 'load-balancer-api-external: resolved host name a9e568f1ec1bf4aebbb9bbb449910e14-8ce1ad4de08905e0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T20:19:52Z" - latency: 4.897916ms message: 'load-balancer-api-external: tcp connection to a9e568f1ec1bf4aebbb9bbb449910e14-8ce1ad4de08905e0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:18:52Z" - latency: 6.686404ms message: 'load-balancer-api-external: resolved host name a9e568f1ec1bf4aebbb9bbb449910e14-8ce1ad4de08905e0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T20:18:52Z" - latency: 4.161793ms message: 'load-balancer-api-external: tcp connection to a9e568f1ec1bf4aebbb9bbb449910e14-8ce1ad4de08905e0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:17:52Z" - latency: 6.817436ms message: 'load-balancer-api-external: resolved host name a9e568f1ec1bf4aebbb9bbb449910e14-8ce1ad4de08905e0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T20:17:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T19:51:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-165-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-165.ec2.internal uid: ea870359-d734-43e6-818d-2eb57464d9a5 resourceVersion: "43236" uid: 5782d381-c3df-4f26-a4d1-4fa2971cfd78 spec: sourcePod: network-check-source-7f44b6dd87-x29mj targetEndpoint: a9e568f1ec1bf4aebbb9bbb449910e14-8ce1ad4de08905e0.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-26T19:57:52Z" message: 'load-balancer-api-internal: tcp connection to a9e568f1ec1bf4aebbb9bbb449910e14-8ce1ad4de08905e0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.053527ms message: 'load-balancer-api-internal: tcp connection to a9e568f1ec1bf4aebbb9bbb449910e14-8ce1ad4de08905e0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:21:52Z" - latency: 6.380167ms message: 'load-balancer-api-internal: resolved host name a9e568f1ec1bf4aebbb9bbb449910e14-8ce1ad4de08905e0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T20:21:52Z" - latency: 5.683995ms message: 'load-balancer-api-internal: tcp connection to a9e568f1ec1bf4aebbb9bbb449910e14-8ce1ad4de08905e0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:20:52Z" - latency: 8.788035ms message: 'load-balancer-api-internal: resolved host name a9e568f1ec1bf4aebbb9bbb449910e14-8ce1ad4de08905e0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T20:20:52Z" - latency: 5.256642ms message: 'load-balancer-api-internal: tcp connection to a9e568f1ec1bf4aebbb9bbb449910e14-8ce1ad4de08905e0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:19:52Z" - latency: 6.49698ms message: 'load-balancer-api-internal: resolved host name a9e568f1ec1bf4aebbb9bbb449910e14-8ce1ad4de08905e0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T20:19:52Z" - latency: 5.22349ms message: 'load-balancer-api-internal: tcp connection to a9e568f1ec1bf4aebbb9bbb449910e14-8ce1ad4de08905e0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:18:52Z" - latency: 6.656512ms message: 'load-balancer-api-internal: resolved host name a9e568f1ec1bf4aebbb9bbb449910e14-8ce1ad4de08905e0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T20:18:52Z" - latency: 4.149436ms message: 'load-balancer-api-internal: tcp connection to a9e568f1ec1bf4aebbb9bbb449910e14-8ce1ad4de08905e0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:17:52Z" - latency: 6.832431ms message: 'load-balancer-api-internal: resolved host name a9e568f1ec1bf4aebbb9bbb449910e14-8ce1ad4de08905e0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T20:17:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T19:51:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-165-to-network-check-target-ip-10-0-130-165 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-165.ec2.internal uid: ea870359-d734-43e6-818d-2eb57464d9a5 resourceVersion: "40793" uid: 3e725826-3bcf-4ae4-ac22-9be3dde81b47 spec: sourcePod: network-check-source-7f44b6dd87-x29mj targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-26T19:58:52Z" message: 'network-check-target-ip-10-0-130-165: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.493203ms message: 'network-check-target-ip-10-0-130-165: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:19:52Z" - latency: 941.229µs message: 'network-check-target-ip-10-0-130-165: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:18:52Z" - latency: 1.089133ms message: 'network-check-target-ip-10-0-130-165: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:17:52Z" - latency: 1.165871ms message: 'network-check-target-ip-10-0-130-165: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:16:52Z" - latency: 1.736604ms message: 'network-check-target-ip-10-0-130-165: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:15:52Z" - latency: 870.624µs message: 'network-check-target-ip-10-0-130-165: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:14:52Z" - latency: 1.122251ms message: 'network-check-target-ip-10-0-130-165: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:13:52Z" - latency: 847.954µs message: 'network-check-target-ip-10-0-130-165: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:12:52Z" - latency: 782.668µs message: 'network-check-target-ip-10-0-130-165: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:11:52Z" - latency: 870.554µs message: 'network-check-target-ip-10-0-130-165: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:10:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T19:51:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-165-to-network-check-target-ip-10-0-136-217 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-165.ec2.internal uid: ea870359-d734-43e6-818d-2eb57464d9a5 resourceVersion: "40794" uid: 6a59d83b-43f2-43c7-bdaf-072bccd84e48 spec: sourcePod: network-check-source-7f44b6dd87-x29mj targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-26T19:58:52Z" message: 'network-check-target-ip-10-0-136-217: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.467541ms message: 'network-check-target-ip-10-0-136-217: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:19:52Z" - latency: 2.905337ms message: 'network-check-target-ip-10-0-136-217: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:18:52Z" - latency: 2.455481ms message: 'network-check-target-ip-10-0-136-217: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:17:52Z" - latency: 2.209383ms message: 'network-check-target-ip-10-0-136-217: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:16:52Z" - latency: 2.179302ms message: 'network-check-target-ip-10-0-136-217: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:15:52Z" - latency: 2.310646ms message: 'network-check-target-ip-10-0-136-217: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:14:52Z" - latency: 2.395341ms message: 'network-check-target-ip-10-0-136-217: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:13:52Z" - latency: 2.461817ms message: 'network-check-target-ip-10-0-136-217: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:12:52Z" - latency: 2.316834ms message: 'network-check-target-ip-10-0-136-217: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:11:52Z" - latency: 2.784313ms message: 'network-check-target-ip-10-0-136-217: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:10:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T19:51:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-165-to-network-check-target-ip-10-0-141-124 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-165.ec2.internal uid: ea870359-d734-43e6-818d-2eb57464d9a5 resourceVersion: "40795" uid: 2c463914-bd0e-4117-bbd9-21ab390af652 spec: sourcePod: network-check-source-7f44b6dd87-x29mj targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-26T19:58:52Z" message: 'network-check-target-ip-10-0-141-124: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.349975ms message: 'network-check-target-ip-10-0-141-124: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:19:52Z" - latency: 2.5402ms message: 'network-check-target-ip-10-0-141-124: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:18:52Z" - latency: 2.199112ms message: 'network-check-target-ip-10-0-141-124: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:17:52Z" - latency: 2.100409ms message: 'network-check-target-ip-10-0-141-124: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:16:52Z" - latency: 2.663774ms message: 'network-check-target-ip-10-0-141-124: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:15:52Z" - latency: 2.387609ms message: 'network-check-target-ip-10-0-141-124: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:14:52Z" - latency: 2.334316ms message: 'network-check-target-ip-10-0-141-124: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:13:52Z" - latency: 2.26887ms message: 'network-check-target-ip-10-0-141-124: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:12:52Z" - latency: 2.138205ms message: 'network-check-target-ip-10-0-141-124: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:11:52Z" - latency: 2.309936ms message: 'network-check-target-ip-10-0-141-124: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:10:52Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T19:51:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-165-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-165.ec2.internal uid: ea870359-d734-43e6-818d-2eb57464d9a5 resourceVersion: "43235" uid: 916d958f-7b75-47b5-8578-0042ef4c20d0 spec: sourcePod: network-check-source-7f44b6dd87-x29mj targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-26T19:57:52Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 799.962µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:21:52Z" - latency: 1.703223ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T20:21:52Z" - latency: 1.178477ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:20:52Z" - latency: 1.567988ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T20:20:52Z" - latency: 944.212µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:19:52Z" - latency: 1.575754ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T20:19:52Z" - latency: 962.378µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:18:52Z" - latency: 1.634503ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T20:18:52Z" - latency: 866.467µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T20:17:52Z" - latency: 2.413885ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T20:17:52Z" kind: List metadata: resourceVersion: ""