apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T08:52:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-177-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-177.ec2.internal uid: e0f968b2-5943-45a1-893e-13ff3ce2798b resourceVersion: "22765" uid: fe189e46-e118-4745-97bd-03b9785b6615 spec: sourcePod: network-check-source-685456655f-4zq87 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-08T08:59:01Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.160185ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:20:01Z" - latency: 1.202688ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:19:01Z" - latency: 917.349µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:18:01Z" - latency: 909.305µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:17:01Z" - latency: 881.711µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:16:01Z" - latency: 2.162298ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:15:01Z" - latency: 1.144494ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:14:01Z" - latency: 1.047028ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:13:01Z" - latency: 1.376079ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:12:01Z" - latency: 1.474801ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:11:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T08:52:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-177-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-177.ec2.internal uid: e0f968b2-5943-45a1-893e-13ff3ce2798b resourceVersion: "20880" uid: 8091f019-e7bf-42f0-b9d7-a04ff1335e0f spec: sourcePod: network-check-source-685456655f-4zq87 targetEndpoint: adb7537654347468f8c17f28c281af70-9966db3f31af2d87.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-08T08:58:01Z" message: 'load-balancer-api-external: tcp connection to adb7537654347468f8c17f28c281af70-9966db3f31af2d87.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.903802ms message: 'load-balancer-api-external: tcp connection to adb7537654347468f8c17f28c281af70-9966db3f31af2d87.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:16:01Z" - latency: 7.577068ms message: 'load-balancer-api-external: resolved host name adb7537654347468f8c17f28c281af70-9966db3f31af2d87.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T09:16:01Z" - latency: 3.566449ms message: 'load-balancer-api-external: tcp connection to adb7537654347468f8c17f28c281af70-9966db3f31af2d87.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:15:01Z" - latency: 9.026844ms message: 'load-balancer-api-external: resolved host name adb7537654347468f8c17f28c281af70-9966db3f31af2d87.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T09:15:01Z" - latency: 5.285714ms message: 'load-balancer-api-external: tcp connection to adb7537654347468f8c17f28c281af70-9966db3f31af2d87.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:14:01Z" - latency: 8.059996ms message: 'load-balancer-api-external: resolved host name adb7537654347468f8c17f28c281af70-9966db3f31af2d87.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T09:14:01Z" - latency: 3.371413ms message: 'load-balancer-api-external: tcp connection to adb7537654347468f8c17f28c281af70-9966db3f31af2d87.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:13:01Z" - latency: 8.102254ms message: 'load-balancer-api-external: resolved host name adb7537654347468f8c17f28c281af70-9966db3f31af2d87.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T09:13:01Z" - latency: 3.121277ms message: 'load-balancer-api-external: tcp connection to adb7537654347468f8c17f28c281af70-9966db3f31af2d87.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:12:01Z" - latency: 7.402347ms message: 'load-balancer-api-external: resolved host name adb7537654347468f8c17f28c281af70-9966db3f31af2d87.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T09:12:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T08:52:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-177-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-177.ec2.internal uid: e0f968b2-5943-45a1-893e-13ff3ce2798b resourceVersion: "20879" uid: e6202860-cbb5-4cdd-8d58-164d91bc8784 spec: sourcePod: network-check-source-685456655f-4zq87 targetEndpoint: adb7537654347468f8c17f28c281af70-9966db3f31af2d87.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-08T08:58:01Z" message: 'load-balancer-api-internal: tcp connection to adb7537654347468f8c17f28c281af70-9966db3f31af2d87.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.64239ms message: 'load-balancer-api-internal: tcp connection to adb7537654347468f8c17f28c281af70-9966db3f31af2d87.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:16:01Z" - latency: 7.531799ms message: 'load-balancer-api-internal: resolved host name adb7537654347468f8c17f28c281af70-9966db3f31af2d87.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T09:16:01Z" - latency: 4.465896ms message: 'load-balancer-api-internal: tcp connection to adb7537654347468f8c17f28c281af70-9966db3f31af2d87.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:15:01Z" - latency: 9.068351ms message: 'load-balancer-api-internal: resolved host name adb7537654347468f8c17f28c281af70-9966db3f31af2d87.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T09:15:01Z" - latency: 5.611258ms message: 'load-balancer-api-internal: tcp connection to adb7537654347468f8c17f28c281af70-9966db3f31af2d87.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:14:01Z" - latency: 8.08958ms message: 'load-balancer-api-internal: resolved host name adb7537654347468f8c17f28c281af70-9966db3f31af2d87.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T09:14:01Z" - latency: 4.563437ms message: 'load-balancer-api-internal: tcp connection to adb7537654347468f8c17f28c281af70-9966db3f31af2d87.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:13:01Z" - latency: 8.055071ms message: 'load-balancer-api-internal: resolved host name adb7537654347468f8c17f28c281af70-9966db3f31af2d87.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T09:13:01Z" - latency: 3.131143ms message: 'load-balancer-api-internal: tcp connection to adb7537654347468f8c17f28c281af70-9966db3f31af2d87.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:12:01Z" - latency: 7.319198ms message: 'load-balancer-api-internal: resolved host name adb7537654347468f8c17f28c281af70-9966db3f31af2d87.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T09:12:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T08:52:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-177-to-network-check-target-ip-10-0-132-205 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-177.ec2.internal uid: e0f968b2-5943-45a1-893e-13ff3ce2798b resourceVersion: "22764" uid: e4438943-d84b-4767-ac6e-b7b806841d7d spec: sourcePod: network-check-source-685456655f-4zq87 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-08T08:59:01Z" message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.27033ms message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:20:01Z" - latency: 2.10748ms message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:19:01Z" - latency: 2.589574ms message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:18:01Z" - latency: 2.387183ms message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:17:01Z" - latency: 2.256599ms message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:16:01Z" - latency: 2.750237ms message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:15:01Z" - latency: 2.309141ms message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:14:01Z" - latency: 2.706654ms message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:13:01Z" - latency: 2.425178ms message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:12:01Z" - latency: 2.465426ms message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:11:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T08:52:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-177-to-network-check-target-ip-10-0-141-177 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-177.ec2.internal uid: e0f968b2-5943-45a1-893e-13ff3ce2798b resourceVersion: "22762" uid: 4eba4f56-3d95-4054-bc37-a8b36d6a6cf2 spec: sourcePod: network-check-source-685456655f-4zq87 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-08T08:59:01Z" message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 991.008µs message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:20:01Z" - latency: 1.360468ms message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:19:01Z" - latency: 853.413µs message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:18:01Z" - latency: 952.674µs message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:17:01Z" - latency: 804.243µs message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:16:01Z" - latency: 1.820101ms message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:15:01Z" - latency: 845.441µs message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:14:01Z" - latency: 874.864µs message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:13:01Z" - latency: 1.039824ms message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:12:01Z" - latency: 840.535µs message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:11:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T08:52:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-177-to-network-check-target-ip-10-0-142-216 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-177.ec2.internal uid: e0f968b2-5943-45a1-893e-13ff3ce2798b resourceVersion: "22763" uid: 837fe37b-6d45-47da-9860-ab2780c74a5b spec: sourcePod: network-check-source-685456655f-4zq87 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-08T08:59:01Z" message: 'network-check-target-ip-10-0-142-216: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.307737ms message: 'network-check-target-ip-10-0-142-216: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:20:01Z" - latency: 1.922083ms message: 'network-check-target-ip-10-0-142-216: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:19:01Z" - latency: 2.201387ms message: 'network-check-target-ip-10-0-142-216: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:18:01Z" - latency: 2.260386ms message: 'network-check-target-ip-10-0-142-216: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:17:01Z" - latency: 2.025976ms message: 'network-check-target-ip-10-0-142-216: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:16:01Z" - latency: 5.412495ms message: 'network-check-target-ip-10-0-142-216: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:15:01Z" - latency: 1.998301ms message: 'network-check-target-ip-10-0-142-216: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:14:01Z" - latency: 2.152689ms message: 'network-check-target-ip-10-0-142-216: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:13:01Z" - latency: 2.334604ms message: 'network-check-target-ip-10-0-142-216: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:12:01Z" - latency: 2.168655ms message: 'network-check-target-ip-10-0-142-216: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:11:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T08:52:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-177-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-177.ec2.internal uid: e0f968b2-5943-45a1-893e-13ff3ce2798b resourceVersion: "20878" uid: 23c05ebb-2ee0-4994-a40d-c88a213095e3 spec: sourcePod: network-check-source-685456655f-4zq87 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-08T08:58:01Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 856µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:16:01Z" - latency: 1.670339ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-08T09:16:01Z" - latency: 1.011911ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:15:01Z" - latency: 3.561641ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-08T09:15:01Z" - latency: 1.448726ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:14:01Z" - latency: 1.690816ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-08T09:14:01Z" - latency: 734.137µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:13:01Z" - latency: 1.71024ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-08T09:13:01Z" - latency: 837.577µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-08T09:12:01Z" - latency: 1.853366ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-08T09:12:01Z" kind: List metadata: resourceVersion: ""