apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T02:57:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-202-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-202.ec2.internal uid: ad45750d-e04d-46aa-bfc3-f072438df2c1 resourceVersion: "68230" uid: 3bd4ce51-010e-4a5f-af71-bd034be09e1c spec: sourcePod: network-check-source-6f78d59f99-q25gd targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T03:04:37Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 863.286µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:14:36Z" - latency: 1.036197ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:13:36Z" - latency: 956.521µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:12:36Z" - latency: 897.178µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:11:36Z" - latency: 1.009659ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:10:36Z" - latency: 977.431µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:09:36Z" - latency: 960.938µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:08:36Z" - latency: 1.21418ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:07:36Z" - latency: 923.508µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:06:36Z" - latency: 1.177403ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:05:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T02:57:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-202-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-202.ec2.internal uid: ad45750d-e04d-46aa-bfc3-f072438df2c1 resourceVersion: "68833" uid: 64003cf7-d03d-4467-b582-37b45746c235 spec: sourcePod: network-check-source-6f78d59f99-q25gd targetEndpoint: a8778f1cc0e62415e9a5e75f1b33ea5b-b8e51e5f5de21964.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T03:03:37Z" message: 'load-balancer-api-external: tcp connection to a8778f1cc0e62415e9a5e75f1b33ea5b-b8e51e5f5de21964.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 18.498708ms message: 'load-balancer-api-external: tcp connection to a8778f1cc0e62415e9a5e75f1b33ea5b-b8e51e5f5de21964.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:15:36Z" - latency: 7.070164ms message: 'load-balancer-api-external: resolved host name a8778f1cc0e62415e9a5e75f1b33ea5b-b8e51e5f5de21964.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T04:15:36Z" - latency: 18.870754ms message: 'load-balancer-api-external: tcp connection to a8778f1cc0e62415e9a5e75f1b33ea5b-b8e51e5f5de21964.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:14:36Z" - latency: 6.741033ms message: 'load-balancer-api-external: resolved host name a8778f1cc0e62415e9a5e75f1b33ea5b-b8e51e5f5de21964.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T04:14:36Z" - latency: 14.865256ms message: 'load-balancer-api-external: tcp connection to a8778f1cc0e62415e9a5e75f1b33ea5b-b8e51e5f5de21964.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:13:36Z" - latency: 7.287087ms message: 'load-balancer-api-external: resolved host name a8778f1cc0e62415e9a5e75f1b33ea5b-b8e51e5f5de21964.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T04:13:36Z" - latency: 18.105096ms message: 'load-balancer-api-external: tcp connection to a8778f1cc0e62415e9a5e75f1b33ea5b-b8e51e5f5de21964.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:12:36Z" - latency: 6.650477ms message: 'load-balancer-api-external: resolved host name a8778f1cc0e62415e9a5e75f1b33ea5b-b8e51e5f5de21964.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T04:12:36Z" - latency: 20.25285ms message: 'load-balancer-api-external: tcp connection to a8778f1cc0e62415e9a5e75f1b33ea5b-b8e51e5f5de21964.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:11:36Z" - latency: 6.443297ms message: 'load-balancer-api-external: resolved host name a8778f1cc0e62415e9a5e75f1b33ea5b-b8e51e5f5de21964.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T04:11:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T02:57:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-202-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-202.ec2.internal uid: ad45750d-e04d-46aa-bfc3-f072438df2c1 resourceVersion: "68832" uid: 49dfa387-9c14-4190-af8c-732a45a81ebe spec: sourcePod: network-check-source-6f78d59f99-q25gd targetEndpoint: a8778f1cc0e62415e9a5e75f1b33ea5b-b8e51e5f5de21964.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T03:03:37Z" message: 'load-balancer-api-internal: tcp connection to a8778f1cc0e62415e9a5e75f1b33ea5b-b8e51e5f5de21964.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 13.418667ms message: 'load-balancer-api-internal: tcp connection to a8778f1cc0e62415e9a5e75f1b33ea5b-b8e51e5f5de21964.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:15:36Z" - latency: 7.018873ms message: 'load-balancer-api-internal: resolved host name a8778f1cc0e62415e9a5e75f1b33ea5b-b8e51e5f5de21964.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T04:15:36Z" - latency: 16.93151ms message: 'load-balancer-api-internal: tcp connection to a8778f1cc0e62415e9a5e75f1b33ea5b-b8e51e5f5de21964.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:14:36Z" - latency: 6.665754ms message: 'load-balancer-api-internal: resolved host name a8778f1cc0e62415e9a5e75f1b33ea5b-b8e51e5f5de21964.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T04:14:36Z" - latency: 16.21559ms message: 'load-balancer-api-internal: tcp connection to a8778f1cc0e62415e9a5e75f1b33ea5b-b8e51e5f5de21964.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:13:36Z" - latency: 7.227712ms message: 'load-balancer-api-internal: resolved host name a8778f1cc0e62415e9a5e75f1b33ea5b-b8e51e5f5de21964.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T04:13:36Z" - latency: 17.943316ms message: 'load-balancer-api-internal: tcp connection to a8778f1cc0e62415e9a5e75f1b33ea5b-b8e51e5f5de21964.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:12:36Z" - latency: 6.589965ms message: 'load-balancer-api-internal: resolved host name a8778f1cc0e62415e9a5e75f1b33ea5b-b8e51e5f5de21964.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T04:12:36Z" - latency: 28.925024ms message: 'load-balancer-api-internal: tcp connection to a8778f1cc0e62415e9a5e75f1b33ea5b-b8e51e5f5de21964.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:11:36Z" - latency: 6.492412ms message: 'load-balancer-api-internal: resolved host name a8778f1cc0e62415e9a5e75f1b33ea5b-b8e51e5f5de21964.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T04:11:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T02:57:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-202-to-network-check-target-ip-10-0-130-130 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-202.ec2.internal uid: ad45750d-e04d-46aa-bfc3-f072438df2c1 resourceVersion: "68229" uid: 709a1bb5-a921-458c-b741-64870066a785 spec: sourcePod: network-check-source-6f78d59f99-q25gd targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-30T03:04:36Z" message: 'network-check-target-ip-10-0-130-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.54579ms message: 'network-check-target-ip-10-0-130-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:14:36Z" - latency: 2.814668ms message: 'network-check-target-ip-10-0-130-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:13:36Z" - latency: 2.5682ms message: 'network-check-target-ip-10-0-130-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:12:36Z" - latency: 2.039559ms message: 'network-check-target-ip-10-0-130-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:11:36Z" - latency: 2.079997ms message: 'network-check-target-ip-10-0-130-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:10:36Z" - latency: 2.306015ms message: 'network-check-target-ip-10-0-130-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:09:36Z" - latency: 1.939245ms message: 'network-check-target-ip-10-0-130-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:08:36Z" - latency: 2.285533ms message: 'network-check-target-ip-10-0-130-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:07:36Z" - latency: 2.851728ms message: 'network-check-target-ip-10-0-130-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:06:36Z" - latency: 2.541693ms message: 'network-check-target-ip-10-0-130-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:05:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T02:57:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-202-to-network-check-target-ip-10-0-136-202 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-202.ec2.internal uid: ad45750d-e04d-46aa-bfc3-f072438df2c1 resourceVersion: "68227" uid: a7e93839-a952-47e3-86e0-08ae0d5f3870 spec: sourcePod: network-check-source-6f78d59f99-q25gd targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-30T03:04:36Z" message: 'network-check-target-ip-10-0-136-202: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.154563ms message: 'network-check-target-ip-10-0-136-202: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:14:36Z" - latency: 1.049085ms message: 'network-check-target-ip-10-0-136-202: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:13:36Z" - latency: 954.386µs message: 'network-check-target-ip-10-0-136-202: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:12:36Z" - latency: 1.416752ms message: 'network-check-target-ip-10-0-136-202: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:11:36Z" - latency: 1.596914ms message: 'network-check-target-ip-10-0-136-202: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:10:36Z" - latency: 926.18µs message: 'network-check-target-ip-10-0-136-202: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:09:36Z" - latency: 959.55µs message: 'network-check-target-ip-10-0-136-202: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:08:36Z" - latency: 951.262µs message: 'network-check-target-ip-10-0-136-202: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:07:36Z" - latency: 1.246786ms message: 'network-check-target-ip-10-0-136-202: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:06:36Z" - latency: 1.015823ms message: 'network-check-target-ip-10-0-136-202: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:05:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T02:57:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-202-to-network-check-target-ip-10-0-143-156 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-202.ec2.internal uid: ad45750d-e04d-46aa-bfc3-f072438df2c1 resourceVersion: "68228" uid: 21bffda5-46d2-4b07-a09b-12978d70874c spec: sourcePod: network-check-source-6f78d59f99-q25gd targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-30T03:04:36Z" message: 'network-check-target-ip-10-0-143-156: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.019171ms message: 'network-check-target-ip-10-0-143-156: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:14:36Z" - latency: 2.148519ms message: 'network-check-target-ip-10-0-143-156: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:13:36Z" - latency: 1.736791ms message: 'network-check-target-ip-10-0-143-156: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:12:36Z" - latency: 1.88728ms message: 'network-check-target-ip-10-0-143-156: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:11:36Z" - latency: 1.981926ms message: 'network-check-target-ip-10-0-143-156: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:10:36Z" - latency: 2.177369ms message: 'network-check-target-ip-10-0-143-156: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:09:36Z" - latency: 2.041792ms message: 'network-check-target-ip-10-0-143-156: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:08:36Z" - latency: 2.133474ms message: 'network-check-target-ip-10-0-143-156: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:07:36Z" - latency: 2.111246ms message: 'network-check-target-ip-10-0-143-156: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:06:36Z" - latency: 1.826258ms message: 'network-check-target-ip-10-0-143-156: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:05:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T02:57:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-202-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-202.ec2.internal uid: ad45750d-e04d-46aa-bfc3-f072438df2c1 resourceVersion: "68830" uid: f8cdd5cc-618d-4ea1-b777-26cf43c2a595 spec: sourcePod: network-check-source-6f78d59f99-q25gd targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T03:03:36Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.051091ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:15:36Z" - latency: 1.918249ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T04:15:36Z" - latency: 957.734µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:14:36Z" - latency: 1.970571ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T04:14:36Z" - latency: 973.46µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:13:36Z" - latency: 1.95745ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T04:13:36Z" - latency: 1.037666ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:12:36Z" - latency: 1.855866ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T04:12:36Z" - latency: 930.898µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T04:11:36Z" - latency: 2.076078ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T04:11:36Z" kind: List metadata: resourceVersion: ""