apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T00:33:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-7-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-7.ec2.internal uid: cf6eaf82-9f66-4132-9cf0-ccf43ee893c9 resourceVersion: "149605" uid: 83083000-5c7a-4562-b998-883498b1c43e spec: sourcePod: network-check-source-6f78d59f99-jg5h6 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T00:40:04Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.259768ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:36:04Z" - latency: 1.381426ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:35:04Z" - latency: 888.934µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:34:04Z" - latency: 1.060677ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:33:04Z" - latency: 1.015908ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:32:04Z" - latency: 1.009209ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:31:04Z" - latency: 1.181747ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:30:04Z" - latency: 1.052055ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:29:04Z" - latency: 1.208142ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:28:04Z" - latency: 1.44691ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:27:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T00:33:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-7-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-7.ec2.internal uid: cf6eaf82-9f66-4132-9cf0-ccf43ee893c9 resourceVersion: "151579" uid: 2ab3ec3e-f804-47ed-b736-c1d4524905d2 spec: sourcePod: network-check-source-6f78d59f99-jg5h6 targetEndpoint: a2c224b96570b473b8bc4f8ee2d0cb23-4101d86e018c92cb.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T00:39:04Z" message: 'load-balancer-api-external: tcp connection to a2c224b96570b473b8bc4f8ee2d0cb23-4101d86e018c92cb.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 15.307968ms message: 'load-balancer-api-external: tcp connection to a2c224b96570b473b8bc4f8ee2d0cb23-4101d86e018c92cb.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:39:04Z" - latency: 7.393832ms message: 'load-balancer-api-external: resolved host name a2c224b96570b473b8bc4f8ee2d0cb23-4101d86e018c92cb.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T01:39:04Z" - latency: 16.89897ms message: 'load-balancer-api-external: tcp connection to a2c224b96570b473b8bc4f8ee2d0cb23-4101d86e018c92cb.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:38:04Z" - latency: 6.289478ms message: 'load-balancer-api-external: resolved host name a2c224b96570b473b8bc4f8ee2d0cb23-4101d86e018c92cb.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T01:38:04Z" - latency: 14.295793ms message: 'load-balancer-api-external: tcp connection to a2c224b96570b473b8bc4f8ee2d0cb23-4101d86e018c92cb.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:37:04Z" - latency: 6.794977ms message: 'load-balancer-api-external: resolved host name a2c224b96570b473b8bc4f8ee2d0cb23-4101d86e018c92cb.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T01:37:04Z" - latency: 14.650717ms message: 'load-balancer-api-external: tcp connection to a2c224b96570b473b8bc4f8ee2d0cb23-4101d86e018c92cb.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:36:04Z" - latency: 8.34021ms message: 'load-balancer-api-external: resolved host name a2c224b96570b473b8bc4f8ee2d0cb23-4101d86e018c92cb.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T01:36:04Z" - latency: 17.05306ms message: 'load-balancer-api-external: tcp connection to a2c224b96570b473b8bc4f8ee2d0cb23-4101d86e018c92cb.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:35:04Z" - latency: 6.596736ms message: 'load-balancer-api-external: resolved host name a2c224b96570b473b8bc4f8ee2d0cb23-4101d86e018c92cb.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T01:35:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T00:33:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-7-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-7.ec2.internal uid: cf6eaf82-9f66-4132-9cf0-ccf43ee893c9 resourceVersion: "151580" uid: f4245fcf-aae1-4368-9b1a-a7242fded868 spec: sourcePod: network-check-source-6f78d59f99-jg5h6 targetEndpoint: a2c224b96570b473b8bc4f8ee2d0cb23-4101d86e018c92cb.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T00:39:04Z" message: 'load-balancer-api-internal: tcp connection to a2c224b96570b473b8bc4f8ee2d0cb23-4101d86e018c92cb.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 15.257938ms message: 'load-balancer-api-internal: tcp connection to a2c224b96570b473b8bc4f8ee2d0cb23-4101d86e018c92cb.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:39:04Z" - latency: 7.410886ms message: 'load-balancer-api-internal: resolved host name a2c224b96570b473b8bc4f8ee2d0cb23-4101d86e018c92cb.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T01:39:04Z" - latency: 16.654794ms message: 'load-balancer-api-internal: tcp connection to a2c224b96570b473b8bc4f8ee2d0cb23-4101d86e018c92cb.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:38:04Z" - latency: 6.31053ms message: 'load-balancer-api-internal: resolved host name a2c224b96570b473b8bc4f8ee2d0cb23-4101d86e018c92cb.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T01:38:04Z" - latency: 16.078195ms message: 'load-balancer-api-internal: tcp connection to a2c224b96570b473b8bc4f8ee2d0cb23-4101d86e018c92cb.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:37:04Z" - latency: 6.763922ms message: 'load-balancer-api-internal: resolved host name a2c224b96570b473b8bc4f8ee2d0cb23-4101d86e018c92cb.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T01:37:04Z" - latency: 13.684523ms message: 'load-balancer-api-internal: tcp connection to a2c224b96570b473b8bc4f8ee2d0cb23-4101d86e018c92cb.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:36:04Z" - latency: 8.31311ms message: 'load-balancer-api-internal: resolved host name a2c224b96570b473b8bc4f8ee2d0cb23-4101d86e018c92cb.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T01:36:04Z" - latency: 17.021673ms message: 'load-balancer-api-internal: tcp connection to a2c224b96570b473b8bc4f8ee2d0cb23-4101d86e018c92cb.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:35:04Z" - latency: 6.622791ms message: 'load-balancer-api-internal: resolved host name a2c224b96570b473b8bc4f8ee2d0cb23-4101d86e018c92cb.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T01:35:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T00:33:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-7-to-network-check-target-ip-10-0-128-7 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-7.ec2.internal uid: cf6eaf82-9f66-4132-9cf0-ccf43ee893c9 resourceVersion: "149610" uid: 37262169-da96-4315-b815-de9f44f4d9db spec: sourcePod: network-check-source-6f78d59f99-jg5h6 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-30T00:40:04Z" message: 'network-check-target-ip-10-0-128-7: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.180488ms message: 'network-check-target-ip-10-0-128-7: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:36:04Z" - latency: 968.136µs message: 'network-check-target-ip-10-0-128-7: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:35:04Z" - latency: 1.349442ms message: 'network-check-target-ip-10-0-128-7: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:34:04Z" - latency: 958.462µs message: 'network-check-target-ip-10-0-128-7: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:33:04Z" - latency: 952.724µs message: 'network-check-target-ip-10-0-128-7: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:32:04Z" - latency: 730.344µs message: 'network-check-target-ip-10-0-128-7: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:31:04Z" - latency: 929.902µs message: 'network-check-target-ip-10-0-128-7: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:30:04Z" - latency: 1.358662ms message: 'network-check-target-ip-10-0-128-7: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:29:04Z" - latency: 1.262157ms message: 'network-check-target-ip-10-0-128-7: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:28:04Z" - latency: 972.886µs message: 'network-check-target-ip-10-0-128-7: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:27:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T00:33:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-7-to-network-check-target-ip-10-0-131-130 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-7.ec2.internal uid: cf6eaf82-9f66-4132-9cf0-ccf43ee893c9 resourceVersion: "149623" uid: 65223a23-048d-413c-b6da-5d00a792b314 spec: sourcePod: network-check-source-6f78d59f99-jg5h6 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-30T00:40:05Z" message: 'network-check-target-ip-10-0-131-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 899.213µs message: 'network-check-target-ip-10-0-131-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:36:05Z" - latency: 2.417808ms message: 'network-check-target-ip-10-0-131-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:35:05Z" - latency: 1.91911ms message: 'network-check-target-ip-10-0-131-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:34:05Z" - latency: 2.409043ms message: 'network-check-target-ip-10-0-131-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:33:05Z" - latency: 2.307008ms message: 'network-check-target-ip-10-0-131-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:32:05Z" - latency: 1.611966ms message: 'network-check-target-ip-10-0-131-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:31:05Z" - latency: 1.234021ms message: 'network-check-target-ip-10-0-131-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:30:05Z" - latency: 2.421253ms message: 'network-check-target-ip-10-0-131-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:29:05Z" - latency: 1.027463ms message: 'network-check-target-ip-10-0-131-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:28:05Z" - latency: 2.214503ms message: 'network-check-target-ip-10-0-131-130: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:27:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T00:33:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-7-to-network-check-target-ip-10-0-135-56 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-7.ec2.internal uid: cf6eaf82-9f66-4132-9cf0-ccf43ee893c9 resourceVersion: "149611" uid: 7335a240-d0c7-4b04-a025-0d5bee7129e5 spec: sourcePod: network-check-source-6f78d59f99-jg5h6 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-30T00:40:04Z" message: 'network-check-target-ip-10-0-135-56: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.254245ms message: 'network-check-target-ip-10-0-135-56: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:36:04Z" - latency: 2.781587ms message: 'network-check-target-ip-10-0-135-56: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:35:04Z" - latency: 981.701µs message: 'network-check-target-ip-10-0-135-56: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:34:04Z" - latency: 2.344362ms message: 'network-check-target-ip-10-0-135-56: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:33:04Z" - latency: 2.832328ms message: 'network-check-target-ip-10-0-135-56: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:32:04Z" - latency: 2.548647ms message: 'network-check-target-ip-10-0-135-56: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:31:04Z" - latency: 3.54269ms message: 'network-check-target-ip-10-0-135-56: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:30:04Z" - latency: 1.377575ms message: 'network-check-target-ip-10-0-135-56: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:29:04Z" - latency: 2.940389ms message: 'network-check-target-ip-10-0-135-56: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:28:04Z" - latency: 1.211638ms message: 'network-check-target-ip-10-0-135-56: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:27:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T00:33:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-7-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-7.ec2.internal uid: cf6eaf82-9f66-4132-9cf0-ccf43ee893c9 resourceVersion: "151582" uid: c5378d19-bba5-4c24-8845-051750688950 spec: sourcePod: network-check-source-6f78d59f99-jg5h6 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T00:39:04Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.268118ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:39:04Z" - latency: 884.805µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T01:39:04Z" - latency: 2.326392ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:38:04Z" - latency: 872.158µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T01:38:04Z" - latency: 1.208119ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:37:04Z" - latency: 997.202µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T01:37:04Z" - latency: 2.359619ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:36:04Z" - latency: 744.763µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T01:36:04Z" - latency: 1.359031ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T01:35:04Z" - latency: 893.389µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T01:35:04Z" kind: List metadata: resourceVersion: ""