apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T23:02:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-120-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-120.ec2.internal
      uid: 3e44754d-b665-4e62-8c28-b947344f2538
    resourceVersion: "53201"
    uid: 8dd2ee1f-d932-4b07-bc7b-447c9d2f0342
  spec:
    sourcePod: network-check-source-6f8b768455-bkdqz
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T23:09:47Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.247703ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:30:47Z"
    - latency: 1.164957ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:29:47Z"
    - latency: 974.719µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:28:47Z"
    - latency: 752.607µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:27:47Z"
    - latency: 1.016448ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:26:47Z"
    - latency: 1.835178ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:25:47Z"
    - latency: 948.034µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:24:47Z"
    - latency: 877.117µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:23:47Z"
    - latency: 1.22202ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:22:47Z"
    - latency: 1.062068ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:21:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T23:02:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-120-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-120.ec2.internal
      uid: 3e44754d-b665-4e62-8c28-b947344f2538
    resourceVersion: "54761"
    uid: 4c644c8f-2b1b-468e-90b2-27ca74604d30
  spec:
    sourcePod: network-check-source-6f8b768455-bkdqz
    targetEndpoint: af2c4624641794f18adef2945cfdb575-2ef40ffa65641609.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T23:08:47Z"
      message: 'load-balancer-api-external: tcp connection to af2c4624641794f18adef2945cfdb575-2ef40ffa65641609.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.934283ms
      message: 'load-balancer-api-external: tcp connection to af2c4624641794f18adef2945cfdb575-2ef40ffa65641609.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:32:47Z"
    - latency: 11.028287ms
      message: 'load-balancer-api-external: resolved host name af2c4624641794f18adef2945cfdb575-2ef40ffa65641609.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T23:32:47Z"
    - latency: 4.750811ms
      message: 'load-balancer-api-external: tcp connection to af2c4624641794f18adef2945cfdb575-2ef40ffa65641609.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:31:47Z"
    - latency: 8.557906ms
      message: 'load-balancer-api-external: resolved host name af2c4624641794f18adef2945cfdb575-2ef40ffa65641609.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T23:31:47Z"
    - latency: 6.116372ms
      message: 'load-balancer-api-external: tcp connection to af2c4624641794f18adef2945cfdb575-2ef40ffa65641609.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:30:47Z"
    - latency: 14.11424ms
      message: 'load-balancer-api-external: resolved host name af2c4624641794f18adef2945cfdb575-2ef40ffa65641609.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T23:30:47Z"
    - latency: 5.509017ms
      message: 'load-balancer-api-external: tcp connection to af2c4624641794f18adef2945cfdb575-2ef40ffa65641609.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:29:47Z"
    - latency: 8.927705ms
      message: 'load-balancer-api-external: resolved host name af2c4624641794f18adef2945cfdb575-2ef40ffa65641609.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T23:29:47Z"
    - latency: 4.627875ms
      message: 'load-balancer-api-external: tcp connection to af2c4624641794f18adef2945cfdb575-2ef40ffa65641609.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:28:47Z"
    - latency: 6.759545ms
      message: 'load-balancer-api-external: resolved host name af2c4624641794f18adef2945cfdb575-2ef40ffa65641609.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T23:28:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T23:02:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-120-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-120.ec2.internal
      uid: 3e44754d-b665-4e62-8c28-b947344f2538
    resourceVersion: "54762"
    uid: 3d5b5a36-e648-4efd-b246-82c1cc56c0e7
  spec:
    sourcePod: network-check-source-6f8b768455-bkdqz
    targetEndpoint: af2c4624641794f18adef2945cfdb575-2ef40ffa65641609.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T23:08:47Z"
      message: 'load-balancer-api-internal: tcp connection to af2c4624641794f18adef2945cfdb575-2ef40ffa65641609.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.500017ms
      message: 'load-balancer-api-internal: tcp connection to af2c4624641794f18adef2945cfdb575-2ef40ffa65641609.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:32:47Z"
    - latency: 11.074759ms
      message: 'load-balancer-api-internal: resolved host name af2c4624641794f18adef2945cfdb575-2ef40ffa65641609.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T23:32:47Z"
    - latency: 4.685967ms
      message: 'load-balancer-api-internal: tcp connection to af2c4624641794f18adef2945cfdb575-2ef40ffa65641609.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:31:47Z"
    - latency: 8.677169ms
      message: 'load-balancer-api-internal: resolved host name af2c4624641794f18adef2945cfdb575-2ef40ffa65641609.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T23:31:47Z"
    - latency: 6.112406ms
      message: 'load-balancer-api-internal: tcp connection to af2c4624641794f18adef2945cfdb575-2ef40ffa65641609.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:30:47Z"
    - latency: 14.175532ms
      message: 'load-balancer-api-internal: resolved host name af2c4624641794f18adef2945cfdb575-2ef40ffa65641609.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T23:30:47Z"
    - latency: 4.906504ms
      message: 'load-balancer-api-internal: tcp connection to af2c4624641794f18adef2945cfdb575-2ef40ffa65641609.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:29:47Z"
    - latency: 9.011339ms
      message: 'load-balancer-api-internal: resolved host name af2c4624641794f18adef2945cfdb575-2ef40ffa65641609.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T23:29:47Z"
    - latency: 4.67947ms
      message: 'load-balancer-api-internal: tcp connection to af2c4624641794f18adef2945cfdb575-2ef40ffa65641609.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:28:47Z"
    - latency: 6.814206ms
      message: 'load-balancer-api-internal: resolved host name af2c4624641794f18adef2945cfdb575-2ef40ffa65641609.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T23:28:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T23:02:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-120-to-network-check-target-ip-10-0-137-120
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-120.ec2.internal
      uid: 3e44754d-b665-4e62-8c28-b947344f2538
    resourceVersion: "53197"
    uid: e8683fb2-b063-418d-9923-ea962cfcd676
  spec:
    sourcePod: network-check-source-6f8b768455-bkdqz
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T23:09:47Z"
      message: 'network-check-target-ip-10-0-137-120: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 984.945µs
      message: 'network-check-target-ip-10-0-137-120: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:30:47Z"
    - latency: 1.407604ms
      message: 'network-check-target-ip-10-0-137-120: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:29:47Z"
    - latency: 846.288µs
      message: 'network-check-target-ip-10-0-137-120: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:28:47Z"
    - latency: 697.946µs
      message: 'network-check-target-ip-10-0-137-120: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:27:47Z"
    - latency: 958.292µs
      message: 'network-check-target-ip-10-0-137-120: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:26:47Z"
    - latency: 2.632986ms
      message: 'network-check-target-ip-10-0-137-120: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:25:47Z"
    - latency: 989.991µs
      message: 'network-check-target-ip-10-0-137-120: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:24:47Z"
    - latency: 1.409865ms
      message: 'network-check-target-ip-10-0-137-120: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:23:47Z"
    - latency: 914.267µs
      message: 'network-check-target-ip-10-0-137-120: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:22:47Z"
    - latency: 900.631µs
      message: 'network-check-target-ip-10-0-137-120: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:21:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T23:02:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-120-to-network-check-target-ip-10-0-138-139
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-120.ec2.internal
      uid: 3e44754d-b665-4e62-8c28-b947344f2538
    resourceVersion: "53199"
    uid: 0e2f7f7b-8df8-4863-a8ba-40674203a40e
  spec:
    sourcePod: network-check-source-6f8b768455-bkdqz
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T23:09:47Z"
      message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.091387ms
      message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:30:47Z"
    - latency: 2.179039ms
      message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:29:47Z"
    - latency: 2.24173ms
      message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:28:47Z"
    - latency: 1.942307ms
      message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:27:47Z"
    - latency: 2.226351ms
      message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:26:47Z"
    - latency: 4.621711ms
      message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:25:47Z"
    - latency: 2.534433ms
      message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:24:47Z"
    - latency: 2.63128ms
      message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:23:47Z"
    - latency: 2.577663ms
      message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:22:47Z"
    - latency: 2.669503ms
      message: 'network-check-target-ip-10-0-138-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:21:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T23:02:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-120-to-network-check-target-ip-10-0-138-150
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-120.ec2.internal
      uid: 3e44754d-b665-4e62-8c28-b947344f2538
    resourceVersion: "53198"
    uid: ac17ebfd-de57-4313-9192-2b70a3b4ba91
  spec:
    sourcePod: network-check-source-6f8b768455-bkdqz
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T23:09:47Z"
      message: 'network-check-target-ip-10-0-138-150: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.542621ms
      message: 'network-check-target-ip-10-0-138-150: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:30:47Z"
    - latency: 2.184936ms
      message: 'network-check-target-ip-10-0-138-150: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:29:47Z"
    - latency: 2.370625ms
      message: 'network-check-target-ip-10-0-138-150: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:28:47Z"
    - latency: 2.396838ms
      message: 'network-check-target-ip-10-0-138-150: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:27:47Z"
    - latency: 2.855195ms
      message: 'network-check-target-ip-10-0-138-150: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:26:47Z"
    - latency: 1.913744ms
      message: 'network-check-target-ip-10-0-138-150: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:25:47Z"
    - latency: 2.513431ms
      message: 'network-check-target-ip-10-0-138-150: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:24:47Z"
    - latency: 2.56095ms
      message: 'network-check-target-ip-10-0-138-150: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:23:47Z"
    - latency: 2.324468ms
      message: 'network-check-target-ip-10-0-138-150: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:22:47Z"
    - latency: 2.482989ms
      message: 'network-check-target-ip-10-0-138-150: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:21:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T23:02:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-120-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-120.ec2.internal
      uid: 3e44754d-b665-4e62-8c28-b947344f2538
    resourceVersion: "54760"
    uid: 714402b4-c89c-4787-b951-8893d6be62c7
  spec:
    sourcePod: network-check-source-6f8b768455-bkdqz
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T23:08:47Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 758.324µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:32:47Z"
    - latency: 1.874811ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T23:32:47Z"
    - latency: 876.871µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:31:47Z"
    - latency: 2.25694ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T23:31:47Z"
    - latency: 904.562µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:30:47Z"
    - latency: 1.876673ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T23:30:47Z"
    - latency: 847.816µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:29:47Z"
    - latency: 2.075713ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T23:29:47Z"
    - latency: 863.915µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:28:47Z"
    - latency: 1.857933ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T23:28:47Z"
kind: List
metadata:
  resourceVersion: ""