apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T18:51:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-234-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-234.ec2.internal uid: d2feaa09-ed44-4b5f-8881-022ff0c9854f resourceVersion: "34519" uid: 86f644be-a982-4f76-bcce-1bc4710e3225 spec: sourcePod: network-check-source-8894fc9bd-v9ml5 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-22T18:58:10Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 887.353µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:12:10Z" - latency: 1.370942ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:11:10Z" - latency: 833.618µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:10:10Z" - latency: 1.117951ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:09:10Z" - latency: 1.165519ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:08:10Z" - latency: 848.219µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:07:10Z" - latency: 804.824µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:06:10Z" - latency: 1.03622ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:05:10Z" - latency: 914.808µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:04:10Z" - latency: 826.724µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:03:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T18:51:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-234-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-234.ec2.internal uid: d2feaa09-ed44-4b5f-8881-022ff0c9854f resourceVersion: "32045" uid: 303fb779-136b-4b52-9b1d-83823c49bb17 spec: sourcePod: network-check-source-8894fc9bd-v9ml5 targetEndpoint: a4f4aabc7a01a4d7da40e79567a4fa8a-a8584a16c163b62d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-22T18:57:10Z" message: 'load-balancer-api-external: tcp connection to a4f4aabc7a01a4d7da40e79567a4fa8a-a8584a16c163b62d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.790499ms message: 'load-balancer-api-external: tcp connection to a4f4aabc7a01a4d7da40e79567a4fa8a-a8584a16c163b62d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:09:10Z" - latency: 7.659827ms message: 'load-balancer-api-external: resolved host name a4f4aabc7a01a4d7da40e79567a4fa8a-a8584a16c163b62d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:09:10Z" - latency: 4.480642ms message: 'load-balancer-api-external: tcp connection to a4f4aabc7a01a4d7da40e79567a4fa8a-a8584a16c163b62d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:08:10Z" - latency: 6.370223ms message: 'load-balancer-api-external: resolved host name a4f4aabc7a01a4d7da40e79567a4fa8a-a8584a16c163b62d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:08:10Z" - latency: 3.802585ms message: 'load-balancer-api-external: tcp connection to a4f4aabc7a01a4d7da40e79567a4fa8a-a8584a16c163b62d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:07:10Z" - latency: 8.637247ms message: 'load-balancer-api-external: resolved host name a4f4aabc7a01a4d7da40e79567a4fa8a-a8584a16c163b62d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:07:10Z" - latency: 5.89166ms message: 'load-balancer-api-external: tcp connection to a4f4aabc7a01a4d7da40e79567a4fa8a-a8584a16c163b62d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:06:10Z" - latency: 7.029341ms message: 'load-balancer-api-external: resolved host name a4f4aabc7a01a4d7da40e79567a4fa8a-a8584a16c163b62d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:06:10Z" - latency: 5.095992ms message: 'load-balancer-api-external: tcp connection to a4f4aabc7a01a4d7da40e79567a4fa8a-a8584a16c163b62d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:05:10Z" - latency: 8.733524ms message: 'load-balancer-api-external: resolved host name a4f4aabc7a01a4d7da40e79567a4fa8a-a8584a16c163b62d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:05:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T18:51:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-234-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-234.ec2.internal uid: d2feaa09-ed44-4b5f-8881-022ff0c9854f resourceVersion: "32046" uid: 03161417-db42-486f-b7e0-9b99e8c96e51 spec: sourcePod: network-check-source-8894fc9bd-v9ml5 targetEndpoint: a4f4aabc7a01a4d7da40e79567a4fa8a-a8584a16c163b62d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-22T18:57:10Z" message: 'load-balancer-api-internal: tcp connection to a4f4aabc7a01a4d7da40e79567a4fa8a-a8584a16c163b62d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.695917ms message: 'load-balancer-api-internal: tcp connection to a4f4aabc7a01a4d7da40e79567a4fa8a-a8584a16c163b62d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:09:10Z" - latency: 7.770678ms message: 'load-balancer-api-internal: resolved host name a4f4aabc7a01a4d7da40e79567a4fa8a-a8584a16c163b62d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:09:10Z" - latency: 4.529087ms message: 'load-balancer-api-internal: tcp connection to a4f4aabc7a01a4d7da40e79567a4fa8a-a8584a16c163b62d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:08:10Z" - latency: 6.529486ms message: 'load-balancer-api-internal: resolved host name a4f4aabc7a01a4d7da40e79567a4fa8a-a8584a16c163b62d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:08:10Z" - latency: 4.082773ms message: 'load-balancer-api-internal: tcp connection to a4f4aabc7a01a4d7da40e79567a4fa8a-a8584a16c163b62d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:07:10Z" - latency: 8.59137ms message: 'load-balancer-api-internal: resolved host name a4f4aabc7a01a4d7da40e79567a4fa8a-a8584a16c163b62d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:07:10Z" - latency: 5.254832ms message: 'load-balancer-api-internal: tcp connection to a4f4aabc7a01a4d7da40e79567a4fa8a-a8584a16c163b62d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:06:10Z" - latency: 7.106906ms message: 'load-balancer-api-internal: resolved host name a4f4aabc7a01a4d7da40e79567a4fa8a-a8584a16c163b62d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:06:10Z" - latency: 5.10836ms message: 'load-balancer-api-internal: tcp connection to a4f4aabc7a01a4d7da40e79567a4fa8a-a8584a16c163b62d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:05:10Z" - latency: 8.757574ms message: 'load-balancer-api-internal: resolved host name a4f4aabc7a01a4d7da40e79567a4fa8a-a8584a16c163b62d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:05:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T18:51:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-234-to-network-check-target-ip-10-0-130-234 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-234.ec2.internal uid: d2feaa09-ed44-4b5f-8881-022ff0c9854f resourceVersion: "34516" uid: 6142bd94-ec2c-4510-a4c0-c5aea35c574d spec: sourcePod: network-check-source-8894fc9bd-v9ml5 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-22T18:58:10Z" message: 'network-check-target-ip-10-0-130-234: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 873.513µs message: 'network-check-target-ip-10-0-130-234: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:12:10Z" - latency: 816.052µs message: 'network-check-target-ip-10-0-130-234: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:11:10Z" - latency: 1.385023ms message: 'network-check-target-ip-10-0-130-234: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:10:10Z" - latency: 985.271µs message: 'network-check-target-ip-10-0-130-234: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:09:10Z" - latency: 1.297804ms message: 'network-check-target-ip-10-0-130-234: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:08:10Z" - latency: 747.641µs message: 'network-check-target-ip-10-0-130-234: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:07:10Z" - latency: 1.699474ms message: 'network-check-target-ip-10-0-130-234: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:06:10Z" - latency: 743.886µs message: 'network-check-target-ip-10-0-130-234: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:05:10Z" - latency: 831.651µs message: 'network-check-target-ip-10-0-130-234: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:04:10Z" - latency: 1.280911ms message: 'network-check-target-ip-10-0-130-234: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:03:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T18:51:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-234-to-network-check-target-ip-10-0-133-84 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-234.ec2.internal uid: d2feaa09-ed44-4b5f-8881-022ff0c9854f resourceVersion: "34517" uid: 3b0e4217-5af1-439e-9f71-36f76f193a99 spec: sourcePod: network-check-source-8894fc9bd-v9ml5 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-22T18:58:10Z" message: 'network-check-target-ip-10-0-133-84: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.244456ms message: 'network-check-target-ip-10-0-133-84: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:12:10Z" - latency: 2.404035ms message: 'network-check-target-ip-10-0-133-84: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:11:10Z" - latency: 1.95671ms message: 'network-check-target-ip-10-0-133-84: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:10:10Z" - latency: 2.22445ms message: 'network-check-target-ip-10-0-133-84: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:09:10Z" - latency: 1.942544ms message: 'network-check-target-ip-10-0-133-84: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:08:10Z" - latency: 1.959502ms message: 'network-check-target-ip-10-0-133-84: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:07:10Z" - latency: 2.56925ms message: 'network-check-target-ip-10-0-133-84: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:06:10Z" - latency: 2.102301ms message: 'network-check-target-ip-10-0-133-84: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:05:10Z" - latency: 2.11256ms message: 'network-check-target-ip-10-0-133-84: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:04:10Z" - latency: 2.080175ms message: 'network-check-target-ip-10-0-133-84: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:03:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T18:51:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-234-to-network-check-target-ip-10-0-136-53 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-234.ec2.internal uid: d2feaa09-ed44-4b5f-8881-022ff0c9854f resourceVersion: "34518" uid: a469335b-8a32-4b7c-add5-95eba5dbc0e3 spec: sourcePod: network-check-source-8894fc9bd-v9ml5 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-22T18:58:10Z" message: 'network-check-target-ip-10-0-136-53: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.652534ms message: 'network-check-target-ip-10-0-136-53: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:12:10Z" - latency: 2.290363ms message: 'network-check-target-ip-10-0-136-53: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:11:10Z" - latency: 2.26149ms message: 'network-check-target-ip-10-0-136-53: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:10:10Z" - latency: 2.233414ms message: 'network-check-target-ip-10-0-136-53: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:09:10Z" - latency: 2.183472ms message: 'network-check-target-ip-10-0-136-53: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:08:10Z" - latency: 2.175584ms message: 'network-check-target-ip-10-0-136-53: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:07:10Z" - latency: 2.630284ms message: 'network-check-target-ip-10-0-136-53: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:06:10Z" - latency: 2.621788ms message: 'network-check-target-ip-10-0-136-53: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:05:10Z" - latency: 2.373576ms message: 'network-check-target-ip-10-0-136-53: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:04:10Z" - latency: 2.263818ms message: 'network-check-target-ip-10-0-136-53: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:03:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T18:51:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-234-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-234.ec2.internal uid: d2feaa09-ed44-4b5f-8881-022ff0c9854f resourceVersion: "32044" uid: 8be06e7e-a343-41fc-a1cb-9b825cb0f23a spec: sourcePod: network-check-source-8894fc9bd-v9ml5 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-22T18:57:10Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 850.998µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:09:10Z" - latency: 1.656045ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T19:09:10Z" - latency: 931.425µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:08:10Z" - latency: 2.183067ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T19:08:10Z" - latency: 884.494µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:07:10Z" - latency: 1.563495ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T19:07:10Z" - latency: 987.027µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:06:10Z" - latency: 2.0938ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T19:06:10Z" - latency: 729.625µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:05:10Z" - latency: 1.660752ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T19:05:10Z" kind: List metadata: resourceVersion: ""