apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T17:45:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-170-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-170.ec2.internal uid: 88abba99-a9bd-448d-8767-fe6a9a654f5a resourceVersion: "54238" uid: 47ecaea9-c87c-43a0-b534-0ea5b693380d spec: sourcePod: network-check-source-989f8b8dc-8xtch targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-07T17:52:03Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.209149ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:20:03Z" - latency: 1.005223ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:19:03Z" - latency: 1.08781ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:18:03Z" - latency: 1.61146ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:17:03Z" - latency: 1.307968ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:16:03Z" - latency: 1.286848ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:15:03Z" - latency: 1.458434ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:14:03Z" - latency: 993.611µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:13:03Z" - latency: 1.223476ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:12:03Z" - latency: 819.876µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:11:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T17:45:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-170-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-170.ec2.internal uid: 88abba99-a9bd-448d-8767-fe6a9a654f5a resourceVersion: "55285" uid: 8bb311b5-5c37-4039-b1b2-59eade591a77 spec: sourcePod: network-check-source-989f8b8dc-8xtch targetEndpoint: a53efc1d676cf4cd7994806e984ce761-3f92548797721652.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T17:51:03Z" message: 'load-balancer-api-external: tcp connection to a53efc1d676cf4cd7994806e984ce761-3f92548797721652.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.104139ms message: 'load-balancer-api-external: tcp connection to a53efc1d676cf4cd7994806e984ce761-3f92548797721652.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:21:03Z" - latency: 9.671186ms message: 'load-balancer-api-external: resolved host name a53efc1d676cf4cd7994806e984ce761-3f92548797721652.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T18:21:03Z" - latency: 5.370524ms message: 'load-balancer-api-external: tcp connection to a53efc1d676cf4cd7994806e984ce761-3f92548797721652.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:20:03Z" - latency: 9.855017ms message: 'load-balancer-api-external: resolved host name a53efc1d676cf4cd7994806e984ce761-3f92548797721652.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T18:20:03Z" - latency: 5.102793ms message: 'load-balancer-api-external: tcp connection to a53efc1d676cf4cd7994806e984ce761-3f92548797721652.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:19:03Z" - latency: 8.803684ms message: 'load-balancer-api-external: resolved host name a53efc1d676cf4cd7994806e984ce761-3f92548797721652.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T18:19:03Z" - latency: 3.640707ms message: 'load-balancer-api-external: tcp connection to a53efc1d676cf4cd7994806e984ce761-3f92548797721652.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:18:03Z" - latency: 7.868833ms message: 'load-balancer-api-external: resolved host name a53efc1d676cf4cd7994806e984ce761-3f92548797721652.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T18:18:03Z" - latency: 5.81502ms message: 'load-balancer-api-external: tcp connection to a53efc1d676cf4cd7994806e984ce761-3f92548797721652.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:17:03Z" - latency: 8.41631ms message: 'load-balancer-api-external: resolved host name a53efc1d676cf4cd7994806e984ce761-3f92548797721652.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T18:17:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T17:45:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-170-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-170.ec2.internal uid: 88abba99-a9bd-448d-8767-fe6a9a654f5a resourceVersion: "55284" uid: f1846aa0-eea5-4246-90b4-1ae352ee3cc6 spec: sourcePod: network-check-source-989f8b8dc-8xtch targetEndpoint: a53efc1d676cf4cd7994806e984ce761-3f92548797721652.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T17:51:03Z" message: 'load-balancer-api-internal: tcp connection to a53efc1d676cf4cd7994806e984ce761-3f92548797721652.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.578052ms message: 'load-balancer-api-internal: tcp connection to a53efc1d676cf4cd7994806e984ce761-3f92548797721652.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:21:03Z" - latency: 9.760038ms message: 'load-balancer-api-internal: resolved host name a53efc1d676cf4cd7994806e984ce761-3f92548797721652.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T18:21:03Z" - latency: 4.551759ms message: 'load-balancer-api-internal: tcp connection to a53efc1d676cf4cd7994806e984ce761-3f92548797721652.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:20:03Z" - latency: 10.008251ms message: 'load-balancer-api-internal: resolved host name a53efc1d676cf4cd7994806e984ce761-3f92548797721652.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T18:20:03Z" - latency: 4.316581ms message: 'load-balancer-api-internal: tcp connection to a53efc1d676cf4cd7994806e984ce761-3f92548797721652.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:19:03Z" - latency: 8.904333ms message: 'load-balancer-api-internal: resolved host name a53efc1d676cf4cd7994806e984ce761-3f92548797721652.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T18:19:03Z" - latency: 3.253724ms message: 'load-balancer-api-internal: tcp connection to a53efc1d676cf4cd7994806e984ce761-3f92548797721652.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:18:03Z" - latency: 7.810741ms message: 'load-balancer-api-internal: resolved host name a53efc1d676cf4cd7994806e984ce761-3f92548797721652.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T18:18:03Z" - latency: 5.759374ms message: 'load-balancer-api-internal: tcp connection to a53efc1d676cf4cd7994806e984ce761-3f92548797721652.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:17:03Z" - latency: 8.472695ms message: 'load-balancer-api-internal: resolved host name a53efc1d676cf4cd7994806e984ce761-3f92548797721652.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T18:17:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T17:45:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-170-to-network-check-target-ip-10-0-129-170 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-170.ec2.internal uid: 88abba99-a9bd-448d-8767-fe6a9a654f5a resourceVersion: "54235" uid: dcfae17e-a75b-4c9c-bfe3-ea1996dbd553 spec: sourcePod: network-check-source-989f8b8dc-8xtch targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-07T17:52:03Z" message: 'network-check-target-ip-10-0-129-170: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 904.453µs message: 'network-check-target-ip-10-0-129-170: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:20:03Z" - latency: 1.120126ms message: 'network-check-target-ip-10-0-129-170: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:19:03Z" - latency: 1.49366ms message: 'network-check-target-ip-10-0-129-170: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:18:03Z" - latency: 818.581µs message: 'network-check-target-ip-10-0-129-170: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:17:03Z" - latency: 842.23µs message: 'network-check-target-ip-10-0-129-170: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:16:03Z" - latency: 1.337111ms message: 'network-check-target-ip-10-0-129-170: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:15:03Z" - latency: 1.625595ms message: 'network-check-target-ip-10-0-129-170: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:14:03Z" - latency: 1.022771ms message: 'network-check-target-ip-10-0-129-170: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:13:03Z" - latency: 1.084229ms message: 'network-check-target-ip-10-0-129-170: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:12:03Z" - latency: 1.275022ms message: 'network-check-target-ip-10-0-129-170: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:11:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T17:45:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-170-to-network-check-target-ip-10-0-138-144 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-170.ec2.internal uid: 88abba99-a9bd-448d-8767-fe6a9a654f5a resourceVersion: "54236" uid: 7ee95717-f05b-4ca7-8006-a3555b7c3443 spec: sourcePod: network-check-source-989f8b8dc-8xtch targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-07T17:52:03Z" message: 'network-check-target-ip-10-0-138-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.585107ms message: 'network-check-target-ip-10-0-138-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:20:03Z" - latency: 2.3161ms message: 'network-check-target-ip-10-0-138-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:19:03Z" - latency: 2.214118ms message: 'network-check-target-ip-10-0-138-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:18:03Z" - latency: 2.290153ms message: 'network-check-target-ip-10-0-138-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:17:03Z" - latency: 2.350694ms message: 'network-check-target-ip-10-0-138-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:16:03Z" - latency: 2.570297ms message: 'network-check-target-ip-10-0-138-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:15:03Z" - latency: 2.669951ms message: 'network-check-target-ip-10-0-138-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:14:03Z" - latency: 2.243548ms message: 'network-check-target-ip-10-0-138-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:13:03Z" - latency: 2.510983ms message: 'network-check-target-ip-10-0-138-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:12:03Z" - latency: 2.399133ms message: 'network-check-target-ip-10-0-138-144: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:11:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T17:45:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-170-to-network-check-target-ip-10-0-140-129 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-170.ec2.internal uid: 88abba99-a9bd-448d-8767-fe6a9a654f5a resourceVersion: "54237" uid: 72546ca9-5497-4c37-8423-66bdd195f688 spec: sourcePod: network-check-source-989f8b8dc-8xtch targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-07T17:52:03Z" message: 'network-check-target-ip-10-0-140-129: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.193809ms message: 'network-check-target-ip-10-0-140-129: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:20:03Z" - latency: 2.062013ms message: 'network-check-target-ip-10-0-140-129: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:19:03Z" - latency: 2.124324ms message: 'network-check-target-ip-10-0-140-129: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:18:03Z" - latency: 1.892429ms message: 'network-check-target-ip-10-0-140-129: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:17:03Z" - latency: 1.950527ms message: 'network-check-target-ip-10-0-140-129: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:16:03Z" - latency: 2.15404ms message: 'network-check-target-ip-10-0-140-129: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:15:03Z" - latency: 2.300528ms message: 'network-check-target-ip-10-0-140-129: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:14:03Z" - latency: 2.076581ms message: 'network-check-target-ip-10-0-140-129: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:13:03Z" - latency: 1.914674ms message: 'network-check-target-ip-10-0-140-129: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:12:03Z" - latency: 1.583332ms message: 'network-check-target-ip-10-0-140-129: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:11:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T17:45:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-170-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-170.ec2.internal uid: 88abba99-a9bd-448d-8767-fe6a9a654f5a resourceVersion: "55283" uid: 3dde334a-130b-4c75-a83c-eb8929f4b1e7 spec: sourcePod: network-check-source-989f8b8dc-8xtch targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-07T17:51:03Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 905.328µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:21:03Z" - latency: 1.828541ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T18:21:03Z" - latency: 1.257903ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:20:03Z" - latency: 1.959522ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T18:20:03Z" - latency: 948.326µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:19:03Z" - latency: 1.894648ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T18:19:03Z" - latency: 964.637µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:18:03Z" - latency: 1.821691ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T18:18:03Z" - latency: 982.6µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T18:17:03Z" - latency: 1.799916ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T18:17:03Z" kind: List metadata: resourceVersion: ""