apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T11:20:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-24-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-24.ec2.internal uid: 052b9ab1-5e87-47f8-ab37-d0cbb5352f49 resourceVersion: "19681" uid: c198136f-9c98-46a0-a56e-825d32d8bb59 spec: sourcePod: network-check-source-dbd9cf844-sbp4l targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-05T11:27:10Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 973.763µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:41:10Z" - latency: 1.142827ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:40:10Z" - latency: 1.140294ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:39:10Z" - latency: 1.292669ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:38:10Z" - latency: 1.005032ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:37:10Z" - latency: 978.953µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:36:10Z" - latency: 1.0515ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:35:10Z" - latency: 1.004098ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:34:10Z" - latency: 1.009241ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:33:10Z" - latency: 1.051905ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:32:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T11:20:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-24-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-24.ec2.internal uid: 052b9ab1-5e87-47f8-ab37-d0cbb5352f49 resourceVersion: "18670" uid: d4b4a9fc-77ba-44ff-aa63-8941ec9d18a6 spec: sourcePod: network-check-source-dbd9cf844-sbp4l targetEndpoint: acde7dead20ac4fe29d8a2e50e4ac42f-1482f99cd1579df9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-05T11:26:10Z" message: 'load-balancer-api-external: tcp connection to acde7dead20ac4fe29d8a2e50e4ac42f-1482f99cd1579df9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.669082ms message: 'load-balancer-api-external: tcp connection to acde7dead20ac4fe29d8a2e50e4ac42f-1482f99cd1579df9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:38:10Z" - latency: 6.702493ms message: 'load-balancer-api-external: resolved host name acde7dead20ac4fe29d8a2e50e4ac42f-1482f99cd1579df9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T11:38:10Z" - latency: 4.283618ms message: 'load-balancer-api-external: tcp connection to acde7dead20ac4fe29d8a2e50e4ac42f-1482f99cd1579df9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:37:10Z" - latency: 7.28222ms message: 'load-balancer-api-external: resolved host name acde7dead20ac4fe29d8a2e50e4ac42f-1482f99cd1579df9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T11:37:10Z" - latency: 5.161969ms message: 'load-balancer-api-external: tcp connection to acde7dead20ac4fe29d8a2e50e4ac42f-1482f99cd1579df9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:36:10Z" - latency: 6.088703ms message: 'load-balancer-api-external: resolved host name acde7dead20ac4fe29d8a2e50e4ac42f-1482f99cd1579df9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T11:36:10Z" - latency: 4.812079ms message: 'load-balancer-api-external: tcp connection to acde7dead20ac4fe29d8a2e50e4ac42f-1482f99cd1579df9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:35:10Z" - latency: 8.071705ms message: 'load-balancer-api-external: resolved host name acde7dead20ac4fe29d8a2e50e4ac42f-1482f99cd1579df9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T11:35:10Z" - latency: 4.949ms message: 'load-balancer-api-external: tcp connection to acde7dead20ac4fe29d8a2e50e4ac42f-1482f99cd1579df9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:34:10Z" - latency: 6.954969ms message: 'load-balancer-api-external: resolved host name acde7dead20ac4fe29d8a2e50e4ac42f-1482f99cd1579df9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T11:34:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T11:20:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-24-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-24.ec2.internal uid: 052b9ab1-5e87-47f8-ab37-d0cbb5352f49 resourceVersion: "18669" uid: a1d45e35-77f0-4f04-ab56-065f3e11a529 spec: sourcePod: network-check-source-dbd9cf844-sbp4l targetEndpoint: acde7dead20ac4fe29d8a2e50e4ac42f-1482f99cd1579df9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-05T11:26:10Z" message: 'load-balancer-api-internal: tcp connection to acde7dead20ac4fe29d8a2e50e4ac42f-1482f99cd1579df9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.360659ms message: 'load-balancer-api-internal: tcp connection to acde7dead20ac4fe29d8a2e50e4ac42f-1482f99cd1579df9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:38:10Z" - latency: 6.720684ms message: 'load-balancer-api-internal: resolved host name acde7dead20ac4fe29d8a2e50e4ac42f-1482f99cd1579df9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T11:38:10Z" - latency: 4.289928ms message: 'load-balancer-api-internal: tcp connection to acde7dead20ac4fe29d8a2e50e4ac42f-1482f99cd1579df9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:37:10Z" - latency: 7.326292ms message: 'load-balancer-api-internal: resolved host name acde7dead20ac4fe29d8a2e50e4ac42f-1482f99cd1579df9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T11:37:10Z" - latency: 4.37256ms message: 'load-balancer-api-internal: tcp connection to acde7dead20ac4fe29d8a2e50e4ac42f-1482f99cd1579df9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:36:10Z" - latency: 6.1163ms message: 'load-balancer-api-internal: resolved host name acde7dead20ac4fe29d8a2e50e4ac42f-1482f99cd1579df9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T11:36:10Z" - latency: 3.968679ms message: 'load-balancer-api-internal: tcp connection to acde7dead20ac4fe29d8a2e50e4ac42f-1482f99cd1579df9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:35:10Z" - latency: 8.690548ms message: 'load-balancer-api-internal: resolved host name acde7dead20ac4fe29d8a2e50e4ac42f-1482f99cd1579df9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T11:35:10Z" - latency: 5.204811ms message: 'load-balancer-api-internal: tcp connection to acde7dead20ac4fe29d8a2e50e4ac42f-1482f99cd1579df9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:34:10Z" - latency: 6.835019ms message: 'load-balancer-api-internal: resolved host name acde7dead20ac4fe29d8a2e50e4ac42f-1482f99cd1579df9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T11:34:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T11:20:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-24-to-network-check-target-ip-10-0-128-24 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-24.ec2.internal uid: 052b9ab1-5e87-47f8-ab37-d0cbb5352f49 resourceVersion: "19678" uid: 5cfb548d-9946-49bd-bd88-8f901074ae1a spec: sourcePod: network-check-source-dbd9cf844-sbp4l targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-05T11:27:10Z" message: 'network-check-target-ip-10-0-128-24: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.476968ms message: 'network-check-target-ip-10-0-128-24: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:41:10Z" - latency: 1.287626ms message: 'network-check-target-ip-10-0-128-24: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:40:10Z" - latency: 1.252011ms message: 'network-check-target-ip-10-0-128-24: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:39:10Z" - latency: 1.21097ms message: 'network-check-target-ip-10-0-128-24: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:38:10Z" - latency: 1.297934ms message: 'network-check-target-ip-10-0-128-24: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:37:10Z" - latency: 892.577µs message: 'network-check-target-ip-10-0-128-24: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:36:10Z" - latency: 1.440181ms message: 'network-check-target-ip-10-0-128-24: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:35:10Z" - latency: 970.302µs message: 'network-check-target-ip-10-0-128-24: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:34:10Z" - latency: 951.002µs message: 'network-check-target-ip-10-0-128-24: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:33:10Z" - latency: 1.621181ms message: 'network-check-target-ip-10-0-128-24: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:32:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T11:20:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-24-to-network-check-target-ip-10-0-134-225 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-24.ec2.internal uid: 052b9ab1-5e87-47f8-ab37-d0cbb5352f49 resourceVersion: "19679" uid: c6aa6df2-53d2-4186-afb4-0e6e0cf56f56 spec: sourcePod: network-check-source-dbd9cf844-sbp4l targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-05T11:27:10Z" message: 'network-check-target-ip-10-0-134-225: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.140298ms message: 'network-check-target-ip-10-0-134-225: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:41:10Z" - latency: 2.465533ms message: 'network-check-target-ip-10-0-134-225: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:40:10Z" - latency: 2.530739ms message: 'network-check-target-ip-10-0-134-225: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:39:10Z" - latency: 2.315073ms message: 'network-check-target-ip-10-0-134-225: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:38:10Z" - latency: 2.152145ms message: 'network-check-target-ip-10-0-134-225: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:37:10Z" - latency: 2.111454ms message: 'network-check-target-ip-10-0-134-225: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:36:10Z" - latency: 2.272146ms message: 'network-check-target-ip-10-0-134-225: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:35:10Z" - latency: 2.047086ms message: 'network-check-target-ip-10-0-134-225: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:34:10Z" - latency: 2.215671ms message: 'network-check-target-ip-10-0-134-225: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:33:10Z" - latency: 2.704191ms message: 'network-check-target-ip-10-0-134-225: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:32:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T11:20:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-24-to-network-check-target-ip-10-0-139-125 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-24.ec2.internal uid: 052b9ab1-5e87-47f8-ab37-d0cbb5352f49 resourceVersion: "19680" uid: 5ad19513-c2d8-4dfc-a671-52ab34554c24 spec: sourcePod: network-check-source-dbd9cf844-sbp4l targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-05T11:27:10Z" message: 'network-check-target-ip-10-0-139-125: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.344695ms message: 'network-check-target-ip-10-0-139-125: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:41:10Z" - latency: 2.635087ms message: 'network-check-target-ip-10-0-139-125: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:40:10Z" - latency: 2.550499ms message: 'network-check-target-ip-10-0-139-125: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:39:10Z" - latency: 2.472352ms message: 'network-check-target-ip-10-0-139-125: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:38:10Z" - latency: 2.432385ms message: 'network-check-target-ip-10-0-139-125: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:37:10Z" - latency: 2.274678ms message: 'network-check-target-ip-10-0-139-125: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:36:10Z" - latency: 2.399891ms message: 'network-check-target-ip-10-0-139-125: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:35:10Z" - latency: 2.3568ms message: 'network-check-target-ip-10-0-139-125: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:34:10Z" - latency: 2.406456ms message: 'network-check-target-ip-10-0-139-125: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:33:10Z" - latency: 2.3284ms message: 'network-check-target-ip-10-0-139-125: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:32:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T11:20:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-24-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-24.ec2.internal uid: 052b9ab1-5e87-47f8-ab37-d0cbb5352f49 resourceVersion: "18668" uid: 100bf13a-d973-4fd9-88fa-4974e1aaaaaf spec: sourcePod: network-check-source-dbd9cf844-sbp4l targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-05T11:26:10Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.066261ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:38:10Z" - latency: 1.491645ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T11:38:10Z" - latency: 917.067µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:37:10Z" - latency: 1.911922ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T11:37:10Z" - latency: 1.245913ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:36:10Z" - latency: 1.723944ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T11:36:10Z" - latency: 931.769µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:35:10Z" - latency: 1.767487ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T11:35:10Z" - latency: 974.29µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T11:34:10Z" - latency: 1.584105ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T11:34:10Z" kind: List metadata: resourceVersion: ""