apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-18T13:19:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-234-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-234.ec2.internal uid: 1b00b80d-075b-43f4-90ec-0657132d3236 resourceVersion: "65799" uid: bb201d47-431e-4d51-a09f-06bde9e01173 spec: sourcePod: network-check-source-7cbc45fddc-mvmdl targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-18T13:26:19Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 984.937µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:54:19Z" - latency: 958.223µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:53:19Z" - latency: 1.157564ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:52:19Z" - latency: 1.06438ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:51:19Z" - latency: 1.19109ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:50:19Z" - latency: 1.224564ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:49:19Z" - latency: 1.033708ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:48:19Z" - latency: 1.246977ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:47:19Z" - latency: 1.248521ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:46:19Z" - latency: 1.393ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:45:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-18T13:19:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-234-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-234.ec2.internal uid: 1b00b80d-075b-43f4-90ec-0657132d3236 resourceVersion: "66508" uid: ec0135f0-9c9f-4f01-8484-8c4d874e03b8 spec: sourcePod: network-check-source-7cbc45fddc-mvmdl targetEndpoint: ac1860b11ee6d4d488ee5347ec2bfda4-5aedc9cd88d2f4de.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-18T13:25:19Z" message: 'load-balancer-api-external: tcp connection to ac1860b11ee6d4d488ee5347ec2bfda4-5aedc9cd88d2f4de.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.982611ms message: 'load-balancer-api-external: tcp connection to ac1860b11ee6d4d488ee5347ec2bfda4-5aedc9cd88d2f4de.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:55:19Z" - latency: 8.562315ms message: 'load-balancer-api-external: resolved host name ac1860b11ee6d4d488ee5347ec2bfda4-5aedc9cd88d2f4de.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T13:55:19Z" - latency: 5.612741ms message: 'load-balancer-api-external: tcp connection to ac1860b11ee6d4d488ee5347ec2bfda4-5aedc9cd88d2f4de.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:54:19Z" - latency: 8.816218ms message: 'load-balancer-api-external: resolved host name ac1860b11ee6d4d488ee5347ec2bfda4-5aedc9cd88d2f4de.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T13:54:19Z" - latency: 4.811023ms message: 'load-balancer-api-external: tcp connection to ac1860b11ee6d4d488ee5347ec2bfda4-5aedc9cd88d2f4de.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:53:19Z" - latency: 8.305291ms message: 'load-balancer-api-external: resolved host name ac1860b11ee6d4d488ee5347ec2bfda4-5aedc9cd88d2f4de.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T13:53:19Z" - latency: 4.012237ms message: 'load-balancer-api-external: tcp connection to ac1860b11ee6d4d488ee5347ec2bfda4-5aedc9cd88d2f4de.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:52:19Z" - latency: 7.853332ms message: 'load-balancer-api-external: resolved host name ac1860b11ee6d4d488ee5347ec2bfda4-5aedc9cd88d2f4de.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T13:52:19Z" - latency: 4.935376ms message: 'load-balancer-api-external: tcp connection to ac1860b11ee6d4d488ee5347ec2bfda4-5aedc9cd88d2f4de.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:51:19Z" - latency: 9.077111ms message: 'load-balancer-api-external: resolved host name ac1860b11ee6d4d488ee5347ec2bfda4-5aedc9cd88d2f4de.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T13:51:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-18T13:19:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-234-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-234.ec2.internal uid: 1b00b80d-075b-43f4-90ec-0657132d3236 resourceVersion: "66507" uid: efa16551-fd46-4fcd-ab8c-c0a8b261cc35 spec: sourcePod: network-check-source-7cbc45fddc-mvmdl targetEndpoint: ac1860b11ee6d4d488ee5347ec2bfda4-5aedc9cd88d2f4de.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-18T13:25:19Z" message: 'load-balancer-api-internal: tcp connection to ac1860b11ee6d4d488ee5347ec2bfda4-5aedc9cd88d2f4de.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.042221ms message: 'load-balancer-api-internal: tcp connection to ac1860b11ee6d4d488ee5347ec2bfda4-5aedc9cd88d2f4de.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:55:19Z" - latency: 8.545266ms message: 'load-balancer-api-internal: resolved host name ac1860b11ee6d4d488ee5347ec2bfda4-5aedc9cd88d2f4de.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T13:55:19Z" - latency: 4.628805ms message: 'load-balancer-api-internal: tcp connection to ac1860b11ee6d4d488ee5347ec2bfda4-5aedc9cd88d2f4de.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:54:19Z" - latency: 8.866787ms message: 'load-balancer-api-internal: resolved host name ac1860b11ee6d4d488ee5347ec2bfda4-5aedc9cd88d2f4de.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T13:54:19Z" - latency: 4.503793ms message: 'load-balancer-api-internal: tcp connection to ac1860b11ee6d4d488ee5347ec2bfda4-5aedc9cd88d2f4de.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:53:19Z" - latency: 8.361853ms message: 'load-balancer-api-internal: resolved host name ac1860b11ee6d4d488ee5347ec2bfda4-5aedc9cd88d2f4de.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T13:53:19Z" - latency: 5.841666ms message: 'load-balancer-api-internal: tcp connection to ac1860b11ee6d4d488ee5347ec2bfda4-5aedc9cd88d2f4de.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:52:19Z" - latency: 7.95505ms message: 'load-balancer-api-internal: resolved host name ac1860b11ee6d4d488ee5347ec2bfda4-5aedc9cd88d2f4de.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T13:52:19Z" - latency: 5.734921ms message: 'load-balancer-api-internal: tcp connection to ac1860b11ee6d4d488ee5347ec2bfda4-5aedc9cd88d2f4de.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:51:19Z" - latency: 9.176052ms message: 'load-balancer-api-internal: resolved host name ac1860b11ee6d4d488ee5347ec2bfda4-5aedc9cd88d2f4de.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-18T13:51:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-18T13:19:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-234-to-network-check-target-ip-10-0-129-234 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-234.ec2.internal uid: 1b00b80d-075b-43f4-90ec-0657132d3236 resourceVersion: "65797" uid: 46cb4f54-e96b-47ed-8d54-d8a747915431 spec: sourcePod: network-check-source-7cbc45fddc-mvmdl targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-18T13:26:19Z" message: 'network-check-target-ip-10-0-129-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.861693ms message: 'network-check-target-ip-10-0-129-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:54:19Z" - latency: 884.575µs message: 'network-check-target-ip-10-0-129-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:53:19Z" - latency: 1.170723ms message: 'network-check-target-ip-10-0-129-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:52:19Z" - latency: 1.296791ms message: 'network-check-target-ip-10-0-129-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:51:19Z" - latency: 964.034µs message: 'network-check-target-ip-10-0-129-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:50:19Z" - latency: 1.410962ms message: 'network-check-target-ip-10-0-129-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:49:19Z" - latency: 1.096539ms message: 'network-check-target-ip-10-0-129-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:48:19Z" - latency: 1.097525ms message: 'network-check-target-ip-10-0-129-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:47:19Z" - latency: 1.094772ms message: 'network-check-target-ip-10-0-129-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:46:19Z" - latency: 1.943042ms message: 'network-check-target-ip-10-0-129-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:45:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-18T13:19:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-234-to-network-check-target-ip-10-0-131-221 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-234.ec2.internal uid: 1b00b80d-075b-43f4-90ec-0657132d3236 resourceVersion: "65798" uid: 797f89e0-347e-4cf8-8ba3-89b899e6ef28 spec: sourcePod: network-check-source-7cbc45fddc-mvmdl targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-18T13:26:19Z" message: 'network-check-target-ip-10-0-131-221: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.147308ms message: 'network-check-target-ip-10-0-131-221: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:54:19Z" - latency: 1.717215ms message: 'network-check-target-ip-10-0-131-221: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:53:19Z" - latency: 1.924886ms message: 'network-check-target-ip-10-0-131-221: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:52:19Z" - latency: 2.408739ms message: 'network-check-target-ip-10-0-131-221: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:51:19Z" - latency: 2.652ms message: 'network-check-target-ip-10-0-131-221: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:50:19Z" - latency: 2.166334ms message: 'network-check-target-ip-10-0-131-221: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:49:19Z" - latency: 1.924609ms message: 'network-check-target-ip-10-0-131-221: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:48:19Z" - latency: 2.438446ms message: 'network-check-target-ip-10-0-131-221: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:47:19Z" - latency: 2.234871ms message: 'network-check-target-ip-10-0-131-221: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:46:19Z" - latency: 2.323369ms message: 'network-check-target-ip-10-0-131-221: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:45:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-18T13:19:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-234-to-network-check-target-ip-10-0-136-225 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-234.ec2.internal uid: 1b00b80d-075b-43f4-90ec-0657132d3236 resourceVersion: "65796" uid: 5087eef8-057c-4424-a6c4-e9e2dbdf35ce spec: sourcePod: network-check-source-7cbc45fddc-mvmdl targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-18T13:26:19Z" message: 'network-check-target-ip-10-0-136-225: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.884526ms message: 'network-check-target-ip-10-0-136-225: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:54:19Z" - latency: 2.214097ms message: 'network-check-target-ip-10-0-136-225: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:53:19Z" - latency: 2.319204ms message: 'network-check-target-ip-10-0-136-225: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:52:19Z" - latency: 2.375459ms message: 'network-check-target-ip-10-0-136-225: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:51:19Z" - latency: 2.338191ms message: 'network-check-target-ip-10-0-136-225: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:50:19Z" - latency: 2.51743ms message: 'network-check-target-ip-10-0-136-225: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:49:19Z" - latency: 2.097156ms message: 'network-check-target-ip-10-0-136-225: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:48:19Z" - latency: 2.386759ms message: 'network-check-target-ip-10-0-136-225: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:47:19Z" - latency: 2.380552ms message: 'network-check-target-ip-10-0-136-225: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:46:19Z" - latency: 2.319134ms message: 'network-check-target-ip-10-0-136-225: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:45:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-18T13:19:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-234-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-234.ec2.internal uid: 1b00b80d-075b-43f4-90ec-0657132d3236 resourceVersion: "66506" uid: 2220e102-be87-4f8b-8fb9-c886aa8ffd9e spec: sourcePod: network-check-source-7cbc45fddc-mvmdl targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-18T13:25:19Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 965.421µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:55:19Z" - latency: 1.811918ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-18T13:55:19Z" - latency: 933.941µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:54:19Z" - latency: 2.039835ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-18T13:54:19Z" - latency: 891.328µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:53:19Z" - latency: 1.764252ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-18T13:53:19Z" - latency: 884.377µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:52:19Z" - latency: 1.978162ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-18T13:52:19Z" - latency: 1.082072ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-18T13:51:19Z" - latency: 2.142222ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-18T13:51:19Z" kind: List metadata: resourceVersion: ""