apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T18:33:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-176-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-176.ec2.internal uid: 8f01737b-9843-40bd-acb1-254a21892be7 resourceVersion: "32879" uid: a22e0045-7a69-4f06-8008-01021519c917 spec: sourcePod: network-check-source-7cbc45fddc-bt5vp targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-17T18:40:39Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 967.864µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:15:39Z" - latency: 928.201µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:14:39Z" - latency: 1.326542ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:13:39Z" - latency: 1.000184ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:12:39Z" - latency: 821.735µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:11:39Z" - latency: 1.071573ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:10:39Z" - latency: 1.086045ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:09:39Z" - latency: 1.085025ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:08:39Z" - latency: 810.757µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:07:39Z" - latency: 1.124075ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:06:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T18:33:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-176-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-176.ec2.internal uid: 8f01737b-9843-40bd-acb1-254a21892be7 resourceVersion: "32880" uid: 0552d8c9-4e6b-4f69-a217-5c8ca575e3cb spec: sourcePod: network-check-source-7cbc45fddc-bt5vp targetEndpoint: a8155cb0713c54f6799f8b66ccd248b6-fdf5e64750d5f3c4.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-17T18:39:39Z" message: 'load-balancer-api-external: tcp connection to a8155cb0713c54f6799f8b66ccd248b6-fdf5e64750d5f3c4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.782916ms message: 'load-balancer-api-external: tcp connection to a8155cb0713c54f6799f8b66ccd248b6-fdf5e64750d5f3c4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:15:39Z" - latency: 8.679563ms message: 'load-balancer-api-external: resolved host name a8155cb0713c54f6799f8b66ccd248b6-fdf5e64750d5f3c4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T19:15:39Z" - latency: 4.449433ms message: 'load-balancer-api-external: tcp connection to a8155cb0713c54f6799f8b66ccd248b6-fdf5e64750d5f3c4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:14:39Z" - latency: 8.590082ms message: 'load-balancer-api-external: resolved host name a8155cb0713c54f6799f8b66ccd248b6-fdf5e64750d5f3c4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T19:14:39Z" - latency: 3.629322ms message: 'load-balancer-api-external: tcp connection to a8155cb0713c54f6799f8b66ccd248b6-fdf5e64750d5f3c4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:13:39Z" - latency: 8.378759ms message: 'load-balancer-api-external: resolved host name a8155cb0713c54f6799f8b66ccd248b6-fdf5e64750d5f3c4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T19:13:39Z" - latency: 5.129534ms message: 'load-balancer-api-external: tcp connection to a8155cb0713c54f6799f8b66ccd248b6-fdf5e64750d5f3c4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:12:39Z" - latency: 8.972366ms message: 'load-balancer-api-external: resolved host name a8155cb0713c54f6799f8b66ccd248b6-fdf5e64750d5f3c4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T19:12:39Z" - latency: 4.357163ms message: 'load-balancer-api-external: tcp connection to a8155cb0713c54f6799f8b66ccd248b6-fdf5e64750d5f3c4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:11:39Z" - latency: 7.228061ms message: 'load-balancer-api-external: resolved host name a8155cb0713c54f6799f8b66ccd248b6-fdf5e64750d5f3c4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T19:11:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T18:33:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-176-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-176.ec2.internal uid: 8f01737b-9843-40bd-acb1-254a21892be7 resourceVersion: "32881" uid: d991bd17-7ab9-46ff-bd55-496ebaeb9883 spec: sourcePod: network-check-source-7cbc45fddc-bt5vp targetEndpoint: a8155cb0713c54f6799f8b66ccd248b6-fdf5e64750d5f3c4.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-17T18:39:39Z" message: 'load-balancer-api-internal: tcp connection to a8155cb0713c54f6799f8b66ccd248b6-fdf5e64750d5f3c4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.788751ms message: 'load-balancer-api-internal: tcp connection to a8155cb0713c54f6799f8b66ccd248b6-fdf5e64750d5f3c4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:15:39Z" - latency: 8.701335ms message: 'load-balancer-api-internal: resolved host name a8155cb0713c54f6799f8b66ccd248b6-fdf5e64750d5f3c4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T19:15:39Z" - latency: 4.439855ms message: 'load-balancer-api-internal: tcp connection to a8155cb0713c54f6799f8b66ccd248b6-fdf5e64750d5f3c4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:14:39Z" - latency: 8.623124ms message: 'load-balancer-api-internal: resolved host name a8155cb0713c54f6799f8b66ccd248b6-fdf5e64750d5f3c4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T19:14:39Z" - latency: 3.61107ms message: 'load-balancer-api-internal: tcp connection to a8155cb0713c54f6799f8b66ccd248b6-fdf5e64750d5f3c4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:13:39Z" - latency: 8.427973ms message: 'load-balancer-api-internal: resolved host name a8155cb0713c54f6799f8b66ccd248b6-fdf5e64750d5f3c4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T19:13:39Z" - latency: 5.123665ms message: 'load-balancer-api-internal: tcp connection to a8155cb0713c54f6799f8b66ccd248b6-fdf5e64750d5f3c4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:12:39Z" - latency: 9.012169ms message: 'load-balancer-api-internal: resolved host name a8155cb0713c54f6799f8b66ccd248b6-fdf5e64750d5f3c4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T19:12:39Z" - latency: 3.259108ms message: 'load-balancer-api-internal: tcp connection to a8155cb0713c54f6799f8b66ccd248b6-fdf5e64750d5f3c4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:11:39Z" - latency: 7.255867ms message: 'load-balancer-api-internal: resolved host name a8155cb0713c54f6799f8b66ccd248b6-fdf5e64750d5f3c4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T19:11:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T18:33:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-176-to-network-check-target-ip-10-0-134-167 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-176.ec2.internal uid: 8f01737b-9843-40bd-acb1-254a21892be7 resourceVersion: "32877" uid: 72ea640b-2d9a-4fa7-9f14-c883c6531ac2 spec: sourcePod: network-check-source-7cbc45fddc-bt5vp targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-17T18:40:39Z" message: 'network-check-target-ip-10-0-134-167: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.52207ms message: 'network-check-target-ip-10-0-134-167: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:15:39Z" - latency: 2.169777ms message: 'network-check-target-ip-10-0-134-167: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:14:39Z" - latency: 2.540669ms message: 'network-check-target-ip-10-0-134-167: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:13:39Z" - latency: 2.519893ms message: 'network-check-target-ip-10-0-134-167: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:12:39Z" - latency: 2.700487ms message: 'network-check-target-ip-10-0-134-167: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:11:39Z" - latency: 2.556379ms message: 'network-check-target-ip-10-0-134-167: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:10:39Z" - latency: 2.59938ms message: 'network-check-target-ip-10-0-134-167: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:09:39Z" - latency: 2.498131ms message: 'network-check-target-ip-10-0-134-167: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:08:39Z" - latency: 2.445949ms message: 'network-check-target-ip-10-0-134-167: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:07:39Z" - latency: 2.492507ms message: 'network-check-target-ip-10-0-134-167: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:06:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T18:33:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-176-to-network-check-target-ip-10-0-136-130 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-176.ec2.internal uid: 8f01737b-9843-40bd-acb1-254a21892be7 resourceVersion: "32876" uid: b3c9cc24-fd39-4da1-bf1d-fe3ddb5a1084 spec: sourcePod: network-check-source-7cbc45fddc-bt5vp targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-17T18:40:39Z" message: 'network-check-target-ip-10-0-136-130: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.327832ms message: 'network-check-target-ip-10-0-136-130: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:15:39Z" - latency: 2.68717ms message: 'network-check-target-ip-10-0-136-130: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:14:39Z" - latency: 2.155895ms message: 'network-check-target-ip-10-0-136-130: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:13:39Z" - latency: 2.119588ms message: 'network-check-target-ip-10-0-136-130: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:12:39Z" - latency: 2.29842ms message: 'network-check-target-ip-10-0-136-130: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:11:39Z" - latency: 2.10908ms message: 'network-check-target-ip-10-0-136-130: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:10:39Z" - latency: 2.185609ms message: 'network-check-target-ip-10-0-136-130: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:09:39Z" - latency: 2.565145ms message: 'network-check-target-ip-10-0-136-130: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:08:39Z" - latency: 2.28054ms message: 'network-check-target-ip-10-0-136-130: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:07:39Z" - latency: 2.785663ms message: 'network-check-target-ip-10-0-136-130: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:06:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T18:33:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-176-to-network-check-target-ip-10-0-143-176 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-176.ec2.internal uid: 8f01737b-9843-40bd-acb1-254a21892be7 resourceVersion: "32875" uid: 8e2a917d-ceb0-4029-b305-c10afef5f8b6 spec: sourcePod: network-check-source-7cbc45fddc-bt5vp targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-17T18:40:39Z" message: 'network-check-target-ip-10-0-143-176: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.612211ms message: 'network-check-target-ip-10-0-143-176: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:15:39Z" - latency: 1.696291ms message: 'network-check-target-ip-10-0-143-176: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:14:39Z" - latency: 904.195µs message: 'network-check-target-ip-10-0-143-176: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:13:39Z" - latency: 1.017607ms message: 'network-check-target-ip-10-0-143-176: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:12:39Z" - latency: 833.336µs message: 'network-check-target-ip-10-0-143-176: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:11:39Z" - latency: 1.377879ms message: 'network-check-target-ip-10-0-143-176: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:10:39Z" - latency: 1.607162ms message: 'network-check-target-ip-10-0-143-176: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:09:39Z" - latency: 900.014µs message: 'network-check-target-ip-10-0-143-176: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:08:39Z" - latency: 903.722µs message: 'network-check-target-ip-10-0-143-176: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:07:39Z" - latency: 844.137µs message: 'network-check-target-ip-10-0-143-176: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:06:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T18:33:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-176-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-176.ec2.internal uid: 8f01737b-9843-40bd-acb1-254a21892be7 resourceVersion: "32878" uid: 4b99fda5-9ea3-4910-8048-6df7bbc61d90 spec: sourcePod: network-check-source-7cbc45fddc-bt5vp targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-17T18:39:39Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.084009ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:15:39Z" - latency: 2.045239ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T19:15:39Z" - latency: 1.029848ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:14:39Z" - latency: 1.638585ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T19:14:39Z" - latency: 851.358µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:13:39Z" - latency: 1.840331ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T19:13:39Z" - latency: 1.118103ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:12:39Z" - latency: 1.733377ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T19:12:39Z" - latency: 902.95µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T19:11:39Z" - latency: 2.482548ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T19:11:39Z" kind: List metadata: resourceVersion: ""