apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T21:00:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-162-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-162.ec2.internal uid: 2c7d2b6b-025b-41ba-a807-0bc533490719 resourceVersion: "77668" uid: 5ac94dc2-760e-4e5e-b911-7cac5d15a223 spec: sourcePod: network-check-source-65bdbbff45-wcvn4 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-30T21:07:23Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.197047ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:56:23Z" - latency: 1.072048ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:55:23Z" - latency: 1.101526ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:54:23Z" - latency: 1.007391ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:53:23Z" - latency: 780.79µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:52:23Z" - latency: 1.38773ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:51:23Z" - latency: 849.674µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:50:23Z" - latency: 852.533µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:49:23Z" - latency: 786.811µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:48:23Z" - latency: 1.475187ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:47:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T21:00:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-162-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-162.ec2.internal uid: 2c7d2b6b-025b-41ba-a807-0bc533490719 resourceVersion: "75644" uid: 317ceb0f-a84a-4ed2-93cc-280c25efe6a6 spec: sourcePod: network-check-source-65bdbbff45-wcvn4 targetEndpoint: adfc7eee24ebe4c52a9aac7e7d9b6b8d-0a3bffed04a25a06.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-30T21:06:23Z" message: 'load-balancer-api-external: tcp connection to adfc7eee24ebe4c52a9aac7e7d9b6b8d-0a3bffed04a25a06.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.41355ms message: 'load-balancer-api-external: tcp connection to adfc7eee24ebe4c52a9aac7e7d9b6b8d-0a3bffed04a25a06.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:54:23Z" - latency: 6.812344ms message: 'load-balancer-api-external: resolved host name adfc7eee24ebe4c52a9aac7e7d9b6b8d-0a3bffed04a25a06.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T21:54:23Z" - latency: 4.333055ms message: 'load-balancer-api-external: tcp connection to adfc7eee24ebe4c52a9aac7e7d9b6b8d-0a3bffed04a25a06.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:53:23Z" - latency: 9.363258ms message: 'load-balancer-api-external: resolved host name adfc7eee24ebe4c52a9aac7e7d9b6b8d-0a3bffed04a25a06.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T21:53:23Z" - latency: 4.064624ms message: 'load-balancer-api-external: tcp connection to adfc7eee24ebe4c52a9aac7e7d9b6b8d-0a3bffed04a25a06.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:52:23Z" - latency: 8.239807ms message: 'load-balancer-api-external: resolved host name adfc7eee24ebe4c52a9aac7e7d9b6b8d-0a3bffed04a25a06.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T21:52:23Z" - latency: 4.005621ms message: 'load-balancer-api-external: tcp connection to adfc7eee24ebe4c52a9aac7e7d9b6b8d-0a3bffed04a25a06.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:51:23Z" - latency: 8.7575ms message: 'load-balancer-api-external: resolved host name adfc7eee24ebe4c52a9aac7e7d9b6b8d-0a3bffed04a25a06.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T21:51:23Z" - latency: 5.051835ms message: 'load-balancer-api-external: tcp connection to adfc7eee24ebe4c52a9aac7e7d9b6b8d-0a3bffed04a25a06.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:50:23Z" - latency: 9.71764ms message: 'load-balancer-api-external: resolved host name adfc7eee24ebe4c52a9aac7e7d9b6b8d-0a3bffed04a25a06.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T21:50:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T21:00:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-162-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-162.ec2.internal uid: 2c7d2b6b-025b-41ba-a807-0bc533490719 resourceVersion: "75645" uid: 307129ec-5760-4db4-92ff-99111f732546 spec: sourcePod: network-check-source-65bdbbff45-wcvn4 targetEndpoint: adfc7eee24ebe4c52a9aac7e7d9b6b8d-0a3bffed04a25a06.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-30T21:06:23Z" message: 'load-balancer-api-internal: tcp connection to adfc7eee24ebe4c52a9aac7e7d9b6b8d-0a3bffed04a25a06.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.39123ms message: 'load-balancer-api-internal: tcp connection to adfc7eee24ebe4c52a9aac7e7d9b6b8d-0a3bffed04a25a06.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:54:23Z" - latency: 6.782309ms message: 'load-balancer-api-internal: resolved host name adfc7eee24ebe4c52a9aac7e7d9b6b8d-0a3bffed04a25a06.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T21:54:23Z" - latency: 4.402381ms message: 'load-balancer-api-internal: tcp connection to adfc7eee24ebe4c52a9aac7e7d9b6b8d-0a3bffed04a25a06.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:53:23Z" - latency: 9.392719ms message: 'load-balancer-api-internal: resolved host name adfc7eee24ebe4c52a9aac7e7d9b6b8d-0a3bffed04a25a06.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T21:53:23Z" - latency: 4.086117ms message: 'load-balancer-api-internal: tcp connection to adfc7eee24ebe4c52a9aac7e7d9b6b8d-0a3bffed04a25a06.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:52:23Z" - latency: 8.269996ms message: 'load-balancer-api-internal: resolved host name adfc7eee24ebe4c52a9aac7e7d9b6b8d-0a3bffed04a25a06.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T21:52:23Z" - latency: 3.9811ms message: 'load-balancer-api-internal: tcp connection to adfc7eee24ebe4c52a9aac7e7d9b6b8d-0a3bffed04a25a06.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:51:23Z" - latency: 8.823157ms message: 'load-balancer-api-internal: resolved host name adfc7eee24ebe4c52a9aac7e7d9b6b8d-0a3bffed04a25a06.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T21:51:23Z" - latency: 5.086261ms message: 'load-balancer-api-internal: tcp connection to adfc7eee24ebe4c52a9aac7e7d9b6b8d-0a3bffed04a25a06.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:50:23Z" - latency: 9.662876ms message: 'load-balancer-api-internal: resolved host name adfc7eee24ebe4c52a9aac7e7d9b6b8d-0a3bffed04a25a06.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T21:50:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T21:00:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-162-to-network-check-target-ip-10-0-129-162 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-162.ec2.internal uid: 2c7d2b6b-025b-41ba-a807-0bc533490719 resourceVersion: "77665" uid: 4fb981c0-6e8e-4433-806c-e70a3d2b42db spec: sourcePod: network-check-source-65bdbbff45-wcvn4 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-30T21:07:23Z" message: 'network-check-target-ip-10-0-129-162: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.078229ms message: 'network-check-target-ip-10-0-129-162: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:56:23Z" - latency: 849.239µs message: 'network-check-target-ip-10-0-129-162: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:55:23Z" - latency: 1.267709ms message: 'network-check-target-ip-10-0-129-162: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:54:23Z" - latency: 1.466499ms message: 'network-check-target-ip-10-0-129-162: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:53:23Z" - latency: 889.129µs message: 'network-check-target-ip-10-0-129-162: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:52:23Z" - latency: 1.596549ms message: 'network-check-target-ip-10-0-129-162: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:51:23Z" - latency: 1.445262ms message: 'network-check-target-ip-10-0-129-162: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:50:23Z" - latency: 1.390907ms message: 'network-check-target-ip-10-0-129-162: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:49:23Z" - latency: 904.235µs message: 'network-check-target-ip-10-0-129-162: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:48:23Z" - latency: 930.763µs message: 'network-check-target-ip-10-0-129-162: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:47:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T21:00:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-162-to-network-check-target-ip-10-0-133-49 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-162.ec2.internal uid: 2c7d2b6b-025b-41ba-a807-0bc533490719 resourceVersion: "77666" uid: 7b998d9b-3888-4678-944a-1e1890454a49 spec: sourcePod: network-check-source-65bdbbff45-wcvn4 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-30T21:07:23Z" message: 'network-check-target-ip-10-0-133-49: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.848559ms message: 'network-check-target-ip-10-0-133-49: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:56:23Z" - latency: 1.952118ms message: 'network-check-target-ip-10-0-133-49: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:55:23Z" - latency: 2.086469ms message: 'network-check-target-ip-10-0-133-49: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:54:23Z" - latency: 2.030668ms message: 'network-check-target-ip-10-0-133-49: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:53:23Z" - latency: 1.783915ms message: 'network-check-target-ip-10-0-133-49: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:52:23Z" - latency: 2.377316ms message: 'network-check-target-ip-10-0-133-49: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:51:23Z" - latency: 1.882221ms message: 'network-check-target-ip-10-0-133-49: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:50:23Z" - latency: 2.292934ms message: 'network-check-target-ip-10-0-133-49: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:49:23Z" - latency: 1.578879ms message: 'network-check-target-ip-10-0-133-49: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:48:23Z" - latency: 1.737001ms message: 'network-check-target-ip-10-0-133-49: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:47:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T21:00:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-162-to-network-check-target-ip-10-0-143-139 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-162.ec2.internal uid: 2c7d2b6b-025b-41ba-a807-0bc533490719 resourceVersion: "77667" uid: bfb19fa6-f64c-42d5-af7d-70e34b40e580 spec: sourcePod: network-check-source-65bdbbff45-wcvn4 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-30T21:07:23Z" message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.479609ms message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:56:23Z" - latency: 2.326663ms message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:55:23Z" - latency: 2.432692ms message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:54:23Z" - latency: 2.981431ms message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:53:23Z" - latency: 2.126258ms message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:52:23Z" - latency: 2.242567ms message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:51:23Z" - latency: 2.27631ms message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:50:23Z" - latency: 2.276203ms message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:49:23Z" - latency: 2.220756ms message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:48:23Z" - latency: 2.092272ms message: 'network-check-target-ip-10-0-143-139: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:47:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T21:00:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-162-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-162.ec2.internal uid: 2c7d2b6b-025b-41ba-a807-0bc533490719 resourceVersion: "75643" uid: 675c9ab1-f6b4-416e-b3b9-cdb32f85f6c4 spec: sourcePod: network-check-source-65bdbbff45-wcvn4 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-30T21:06:23Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.014248ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:54:23Z" - latency: 1.618448ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T21:54:23Z" - latency: 802.143µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:53:23Z" - latency: 2.277395ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T21:53:23Z" - latency: 911.972µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:52:23Z" - latency: 1.854909ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T21:52:23Z" - latency: 969.984µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:51:23Z" - latency: 2.272304ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T21:51:23Z" - latency: 880.944µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T21:50:23Z" - latency: 1.885572ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T21:50:23Z" kind: List metadata: resourceVersion: ""