apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T14:02:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-60-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-60.ec2.internal
      uid: 266ae352-9c44-4f46-8b2f-d8d5d23b07e2
    resourceVersion: "37151"
    uid: 6a26ff9d-d9ae-4aeb-ae98-fdecb5bc4df0
  spec:
    sourcePod: network-check-source-7b678d77c7-mhlgp
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T14:10:00Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.026761ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:31:00Z"
    - latency: 1.104047ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:30:00Z"
    - latency: 1.603773ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:29:00Z"
    - latency: 1.098206ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:28:00Z"
    - latency: 1.384885ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:27:00Z"
    - latency: 1.164707ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:26:00Z"
    - latency: 995.412µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:25:00Z"
    - latency: 1.059895ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:24:00Z"
    - latency: 1.247188ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:23:00Z"
    - latency: 1.18532ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:22:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T14:02:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-60-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-60.ec2.internal
      uid: 266ae352-9c44-4f46-8b2f-d8d5d23b07e2
    resourceVersion: "38838"
    uid: a5a7e9f3-910f-4048-b1c5-faab684e0750
  spec:
    sourcePod: network-check-source-7b678d77c7-mhlgp
    targetEndpoint: af37834c57be24bcb9ff3ee3f5667181-304ad90b2a5d34c3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T14:09:00Z"
      message: 'load-balancer-api-external: tcp connection to af37834c57be24bcb9ff3ee3f5667181-304ad90b2a5d34c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.653264ms
      message: 'load-balancer-api-external: tcp connection to af37834c57be24bcb9ff3ee3f5667181-304ad90b2a5d34c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:33:00Z"
    - latency: 9.758595ms
      message: 'load-balancer-api-external: resolved host name af37834c57be24bcb9ff3ee3f5667181-304ad90b2a5d34c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T14:33:00Z"
    - latency: 5.228579ms
      message: 'load-balancer-api-external: tcp connection to af37834c57be24bcb9ff3ee3f5667181-304ad90b2a5d34c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:32:00Z"
    - latency: 7.547972ms
      message: 'load-balancer-api-external: resolved host name af37834c57be24bcb9ff3ee3f5667181-304ad90b2a5d34c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T14:32:00Z"
    - latency: 5.224335ms
      message: 'load-balancer-api-external: tcp connection to af37834c57be24bcb9ff3ee3f5667181-304ad90b2a5d34c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:31:00Z"
    - latency: 7.418789ms
      message: 'load-balancer-api-external: resolved host name af37834c57be24bcb9ff3ee3f5667181-304ad90b2a5d34c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T14:31:00Z"
    - latency: 5.396548ms
      message: 'load-balancer-api-external: tcp connection to af37834c57be24bcb9ff3ee3f5667181-304ad90b2a5d34c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:30:00Z"
    - latency: 6.572853ms
      message: 'load-balancer-api-external: resolved host name af37834c57be24bcb9ff3ee3f5667181-304ad90b2a5d34c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T14:30:00Z"
    - latency: 3.533615ms
      message: 'load-balancer-api-external: tcp connection to af37834c57be24bcb9ff3ee3f5667181-304ad90b2a5d34c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:29:00Z"
    - latency: 7.103672ms
      message: 'load-balancer-api-external: resolved host name af37834c57be24bcb9ff3ee3f5667181-304ad90b2a5d34c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T14:29:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T14:02:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-60-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-60.ec2.internal
      uid: 266ae352-9c44-4f46-8b2f-d8d5d23b07e2
    resourceVersion: "38837"
    uid: 420974df-913e-4a76-9fbb-cb029ff43b03
  spec:
    sourcePod: network-check-source-7b678d77c7-mhlgp
    targetEndpoint: af37834c57be24bcb9ff3ee3f5667181-304ad90b2a5d34c3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T14:09:00Z"
      message: 'load-balancer-api-internal: tcp connection to af37834c57be24bcb9ff3ee3f5667181-304ad90b2a5d34c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.690629ms
      message: 'load-balancer-api-internal: tcp connection to af37834c57be24bcb9ff3ee3f5667181-304ad90b2a5d34c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:33:00Z"
    - latency: 9.741964ms
      message: 'load-balancer-api-internal: resolved host name af37834c57be24bcb9ff3ee3f5667181-304ad90b2a5d34c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T14:33:00Z"
    - latency: 4.78842ms
      message: 'load-balancer-api-internal: tcp connection to af37834c57be24bcb9ff3ee3f5667181-304ad90b2a5d34c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:32:00Z"
    - latency: 7.660472ms
      message: 'load-balancer-api-internal: resolved host name af37834c57be24bcb9ff3ee3f5667181-304ad90b2a5d34c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T14:32:00Z"
    - latency: 5.200556ms
      message: 'load-balancer-api-internal: tcp connection to af37834c57be24bcb9ff3ee3f5667181-304ad90b2a5d34c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:31:00Z"
    - latency: 7.372835ms
      message: 'load-balancer-api-internal: resolved host name af37834c57be24bcb9ff3ee3f5667181-304ad90b2a5d34c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T14:31:00Z"
    - latency: 5.182625ms
      message: 'load-balancer-api-internal: tcp connection to af37834c57be24bcb9ff3ee3f5667181-304ad90b2a5d34c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:30:00Z"
    - latency: 6.595028ms
      message: 'load-balancer-api-internal: resolved host name af37834c57be24bcb9ff3ee3f5667181-304ad90b2a5d34c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T14:30:00Z"
    - latency: 4.441635ms
      message: 'load-balancer-api-internal: tcp connection to af37834c57be24bcb9ff3ee3f5667181-304ad90b2a5d34c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:29:00Z"
    - latency: 7.073162ms
      message: 'load-balancer-api-internal: resolved host name af37834c57be24bcb9ff3ee3f5667181-304ad90b2a5d34c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T14:29:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T14:02:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-60-to-network-check-target-ip-10-0-128-60
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-60.ec2.internal
      uid: 266ae352-9c44-4f46-8b2f-d8d5d23b07e2
    resourceVersion: "37150"
    uid: d2def3b9-7d94-4bff-a76c-9d4db516c8f4
  spec:
    sourcePod: network-check-source-7b678d77c7-mhlgp
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T14:10:00Z"
      message: 'network-check-target-ip-10-0-128-60: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.290236ms
      message: 'network-check-target-ip-10-0-128-60: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:31:00Z"
    - latency: 813.164µs
      message: 'network-check-target-ip-10-0-128-60: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:30:00Z"
    - latency: 982.096µs
      message: 'network-check-target-ip-10-0-128-60: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:29:00Z"
    - latency: 1.644298ms
      message: 'network-check-target-ip-10-0-128-60: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:28:00Z"
    - latency: 1.579288ms
      message: 'network-check-target-ip-10-0-128-60: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:27:00Z"
    - latency: 940.565µs
      message: 'network-check-target-ip-10-0-128-60: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:26:00Z"
    - latency: 1.09958ms
      message: 'network-check-target-ip-10-0-128-60: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:25:00Z"
    - latency: 1.48022ms
      message: 'network-check-target-ip-10-0-128-60: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:24:00Z"
    - latency: 922.859µs
      message: 'network-check-target-ip-10-0-128-60: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:23:00Z"
    - latency: 850.748µs
      message: 'network-check-target-ip-10-0-128-60: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:22:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T14:02:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-60-to-network-check-target-ip-10-0-133-133
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-60.ec2.internal
      uid: 266ae352-9c44-4f46-8b2f-d8d5d23b07e2
    resourceVersion: "37149"
    uid: bafaa7bf-5d4c-4271-91e5-faf128492606
  spec:
    sourcePod: network-check-source-7b678d77c7-mhlgp
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T14:10:00Z"
      message: 'network-check-target-ip-10-0-133-133: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.712637ms
      message: 'network-check-target-ip-10-0-133-133: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:31:00Z"
    - latency: 1.91008ms
      message: 'network-check-target-ip-10-0-133-133: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:30:00Z"
    - latency: 1.468848ms
      message: 'network-check-target-ip-10-0-133-133: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:29:00Z"
    - latency: 1.973443ms
      message: 'network-check-target-ip-10-0-133-133: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:28:00Z"
    - latency: 2.201465ms
      message: 'network-check-target-ip-10-0-133-133: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:27:00Z"
    - latency: 2.027702ms
      message: 'network-check-target-ip-10-0-133-133: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:26:00Z"
    - latency: 2.148806ms
      message: 'network-check-target-ip-10-0-133-133: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:25:00Z"
    - latency: 1.877555ms
      message: 'network-check-target-ip-10-0-133-133: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:24:00Z"
    - latency: 2.192197ms
      message: 'network-check-target-ip-10-0-133-133: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:23:00Z"
    - latency: 2.053559ms
      message: 'network-check-target-ip-10-0-133-133: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:22:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T14:02:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-60-to-network-check-target-ip-10-0-138-227
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-60.ec2.internal
      uid: 266ae352-9c44-4f46-8b2f-d8d5d23b07e2
    resourceVersion: "37148"
    uid: 387e19f7-7002-4b97-82f2-eaa5229cebbc
  spec:
    sourcePod: network-check-source-7b678d77c7-mhlgp
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T14:10:00Z"
      message: 'network-check-target-ip-10-0-138-227: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.051938ms
      message: 'network-check-target-ip-10-0-138-227: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:31:00Z"
    - latency: 1.836026ms
      message: 'network-check-target-ip-10-0-138-227: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:30:00Z"
    - latency: 2.07537ms
      message: 'network-check-target-ip-10-0-138-227: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:29:00Z"
    - latency: 1.98092ms
      message: 'network-check-target-ip-10-0-138-227: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:28:00Z"
    - latency: 2.273722ms
      message: 'network-check-target-ip-10-0-138-227: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:27:00Z"
    - latency: 2.161321ms
      message: 'network-check-target-ip-10-0-138-227: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:26:00Z"
    - latency: 2.205195ms
      message: 'network-check-target-ip-10-0-138-227: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:25:00Z"
    - latency: 2.224759ms
      message: 'network-check-target-ip-10-0-138-227: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:24:00Z"
    - latency: 2.016576ms
      message: 'network-check-target-ip-10-0-138-227: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:23:00Z"
    - latency: 2.056278ms
      message: 'network-check-target-ip-10-0-138-227: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:22:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T14:02:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-60-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-60.ec2.internal
      uid: 266ae352-9c44-4f46-8b2f-d8d5d23b07e2
    resourceVersion: "38836"
    uid: 2b70b652-f509-4245-b563-11eb2dce4611
  spec:
    sourcePod: network-check-source-7b678d77c7-mhlgp
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T14:09:00Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 947.59µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:33:00Z"
    - latency: 1.801366ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T14:33:00Z"
    - latency: 890.383µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:32:00Z"
    - latency: 1.716551ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T14:32:00Z"
    - latency: 1.119811ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:31:00Z"
    - latency: 1.786408ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T14:31:00Z"
    - latency: 811.056µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:30:00Z"
    - latency: 2.04701ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T14:30:00Z"
    - latency: 821.855µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T14:29:00Z"
    - latency: 2.10738ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T14:29:00Z"
kind: List
metadata:
  resourceVersion: ""