apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T21:10:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-20-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-20.ec2.internal
      uid: e2f61349-3c6d-4714-8094-8e803f03ebca
    resourceVersion: "42952"
    uid: 309f6cbb-fce5-40b9-a291-8e45f0324026
  spec:
    sourcePod: network-check-source-8894fc9bd-hqxdd
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T21:17:56Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.157593ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:38:56Z"
    - latency: 1.108429ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:37:56Z"
    - latency: 921.579µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:36:56Z"
    - latency: 799.88µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:35:56Z"
    - latency: 1.076137ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:34:56Z"
    - latency: 826.568µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:33:56Z"
    - latency: 975.064µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:32:56Z"
    - latency: 1.316052ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:31:56Z"
    - latency: 832.241µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:30:56Z"
    - latency: 1.130513ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:29:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T21:10:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-20-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-20.ec2.internal
      uid: e2f61349-3c6d-4714-8094-8e803f03ebca
    resourceVersion: "44919"
    uid: 58f22ead-a6f9-4f77-82de-7fb6b7e20bad
  spec:
    sourcePod: network-check-source-8894fc9bd-hqxdd
    targetEndpoint: aaf2024fcb99d4655a37b66304742294-ee84aa3122cc58e2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T21:16:56Z"
      message: 'load-balancer-api-external: tcp connection to aaf2024fcb99d4655a37b66304742294-ee84aa3122cc58e2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.149622ms
      message: 'load-balancer-api-external: tcp connection to aaf2024fcb99d4655a37b66304742294-ee84aa3122cc58e2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:40:56Z"
    - latency: 7.553874ms
      message: 'load-balancer-api-external: resolved host name aaf2024fcb99d4655a37b66304742294-ee84aa3122cc58e2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T21:40:56Z"
    - latency: 3.634967ms
      message: 'load-balancer-api-external: tcp connection to aaf2024fcb99d4655a37b66304742294-ee84aa3122cc58e2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:39:56Z"
    - latency: 6.771536ms
      message: 'load-balancer-api-external: resolved host name aaf2024fcb99d4655a37b66304742294-ee84aa3122cc58e2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T21:39:56Z"
    - latency: 5.135159ms
      message: 'load-balancer-api-external: tcp connection to aaf2024fcb99d4655a37b66304742294-ee84aa3122cc58e2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:38:56Z"
    - latency: 8.601551ms
      message: 'load-balancer-api-external: resolved host name aaf2024fcb99d4655a37b66304742294-ee84aa3122cc58e2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T21:38:56Z"
    - latency: 3.724982ms
      message: 'load-balancer-api-external: tcp connection to aaf2024fcb99d4655a37b66304742294-ee84aa3122cc58e2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:37:56Z"
    - latency: 10.978956ms
      message: 'load-balancer-api-external: resolved host name aaf2024fcb99d4655a37b66304742294-ee84aa3122cc58e2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T21:37:56Z"
    - latency: 2.86982ms
      message: 'load-balancer-api-external: tcp connection to aaf2024fcb99d4655a37b66304742294-ee84aa3122cc58e2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:36:56Z"
    - latency: 8.200645ms
      message: 'load-balancer-api-external: resolved host name aaf2024fcb99d4655a37b66304742294-ee84aa3122cc58e2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T21:36:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T21:10:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-20-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-20.ec2.internal
      uid: e2f61349-3c6d-4714-8094-8e803f03ebca
    resourceVersion: "44918"
    uid: 576b2693-8bcc-4aaf-be6e-3c886eb5fe7c
  spec:
    sourcePod: network-check-source-8894fc9bd-hqxdd
    targetEndpoint: aaf2024fcb99d4655a37b66304742294-ee84aa3122cc58e2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T21:16:56Z"
      message: 'load-balancer-api-internal: tcp connection to aaf2024fcb99d4655a37b66304742294-ee84aa3122cc58e2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.553758ms
      message: 'load-balancer-api-internal: tcp connection to aaf2024fcb99d4655a37b66304742294-ee84aa3122cc58e2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:40:56Z"
    - latency: 7.524131ms
      message: 'load-balancer-api-internal: resolved host name aaf2024fcb99d4655a37b66304742294-ee84aa3122cc58e2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T21:40:56Z"
    - latency: 3.678847ms
      message: 'load-balancer-api-internal: tcp connection to aaf2024fcb99d4655a37b66304742294-ee84aa3122cc58e2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:39:56Z"
    - latency: 6.693126ms
      message: 'load-balancer-api-internal: resolved host name aaf2024fcb99d4655a37b66304742294-ee84aa3122cc58e2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T21:39:56Z"
    - latency: 5.412165ms
      message: 'load-balancer-api-internal: tcp connection to aaf2024fcb99d4655a37b66304742294-ee84aa3122cc58e2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:38:56Z"
    - latency: 8.573763ms
      message: 'load-balancer-api-internal: resolved host name aaf2024fcb99d4655a37b66304742294-ee84aa3122cc58e2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T21:38:56Z"
    - latency: 4.60946ms
      message: 'load-balancer-api-internal: tcp connection to aaf2024fcb99d4655a37b66304742294-ee84aa3122cc58e2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:37:56Z"
    - latency: 10.95333ms
      message: 'load-balancer-api-internal: resolved host name aaf2024fcb99d4655a37b66304742294-ee84aa3122cc58e2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T21:37:56Z"
    - latency: 3.428405ms
      message: 'load-balancer-api-internal: tcp connection to aaf2024fcb99d4655a37b66304742294-ee84aa3122cc58e2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:36:56Z"
    - latency: 8.156067ms
      message: 'load-balancer-api-internal: resolved host name aaf2024fcb99d4655a37b66304742294-ee84aa3122cc58e2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T21:36:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T21:10:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-20-to-network-check-target-ip-10-0-130-19
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-20.ec2.internal
      uid: e2f61349-3c6d-4714-8094-8e803f03ebca
    resourceVersion: "42951"
    uid: efde71bb-12cf-4f20-abc2-bdc323c4a16d
  spec:
    sourcePod: network-check-source-8894fc9bd-hqxdd
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T21:17:56Z"
      message: 'network-check-target-ip-10-0-130-19: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.322166ms
      message: 'network-check-target-ip-10-0-130-19: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:38:56Z"
    - latency: 2.257917ms
      message: 'network-check-target-ip-10-0-130-19: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:37:56Z"
    - latency: 2.206063ms
      message: 'network-check-target-ip-10-0-130-19: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:36:56Z"
    - latency: 2.202519ms
      message: 'network-check-target-ip-10-0-130-19: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:35:56Z"
    - latency: 2.272428ms
      message: 'network-check-target-ip-10-0-130-19: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:34:56Z"
    - latency: 2.156576ms
      message: 'network-check-target-ip-10-0-130-19: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:33:56Z"
    - latency: 2.075977ms
      message: 'network-check-target-ip-10-0-130-19: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:32:56Z"
    - latency: 2.220447ms
      message: 'network-check-target-ip-10-0-130-19: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:31:56Z"
    - latency: 2.160674ms
      message: 'network-check-target-ip-10-0-130-19: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:30:56Z"
    - latency: 2.429707ms
      message: 'network-check-target-ip-10-0-130-19: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:29:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T21:10:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-20-to-network-check-target-ip-10-0-133-75
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-20.ec2.internal
      uid: e2f61349-3c6d-4714-8094-8e803f03ebca
    resourceVersion: "42950"
    uid: b78c76a6-d6d3-4a9f-aa75-6a71729d7767
  spec:
    sourcePod: network-check-source-8894fc9bd-hqxdd
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T21:17:56Z"
      message: 'network-check-target-ip-10-0-133-75: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.170332ms
      message: 'network-check-target-ip-10-0-133-75: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:38:56Z"
    - latency: 1.815797ms
      message: 'network-check-target-ip-10-0-133-75: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:37:56Z"
    - latency: 1.862063ms
      message: 'network-check-target-ip-10-0-133-75: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:36:56Z"
    - latency: 1.759441ms
      message: 'network-check-target-ip-10-0-133-75: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:35:56Z"
    - latency: 1.995066ms
      message: 'network-check-target-ip-10-0-133-75: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:34:56Z"
    - latency: 1.656413ms
      message: 'network-check-target-ip-10-0-133-75: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:33:56Z"
    - latency: 2.116166ms
      message: 'network-check-target-ip-10-0-133-75: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:32:56Z"
    - latency: 1.791198ms
      message: 'network-check-target-ip-10-0-133-75: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:31:56Z"
    - latency: 1.891297ms
      message: 'network-check-target-ip-10-0-133-75: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:30:56Z"
    - latency: 1.860202ms
      message: 'network-check-target-ip-10-0-133-75: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:29:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T21:10:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-20-to-network-check-target-ip-10-0-138-20
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-20.ec2.internal
      uid: e2f61349-3c6d-4714-8094-8e803f03ebca
    resourceVersion: "42949"
    uid: 5854fc27-138c-49c0-b339-ed4e1cc77ebd
  spec:
    sourcePod: network-check-source-8894fc9bd-hqxdd
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T21:17:56Z"
      message: 'network-check-target-ip-10-0-138-20: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.285207ms
      message: 'network-check-target-ip-10-0-138-20: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:38:56Z"
    - latency: 847.954µs
      message: 'network-check-target-ip-10-0-138-20: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:37:56Z"
    - latency: 826.789µs
      message: 'network-check-target-ip-10-0-138-20: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:36:56Z"
    - latency: 766.485µs
      message: 'network-check-target-ip-10-0-138-20: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:35:56Z"
    - latency: 1.409811ms
      message: 'network-check-target-ip-10-0-138-20: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:34:56Z"
    - latency: 1.090535ms
      message: 'network-check-target-ip-10-0-138-20: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:33:56Z"
    - latency: 1.26436ms
      message: 'network-check-target-ip-10-0-138-20: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:32:56Z"
    - latency: 939.116µs
      message: 'network-check-target-ip-10-0-138-20: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:31:56Z"
    - latency: 891.763µs
      message: 'network-check-target-ip-10-0-138-20: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:30:56Z"
    - latency: 1.351024ms
      message: 'network-check-target-ip-10-0-138-20: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:29:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T21:10:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-20-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-20.ec2.internal
      uid: e2f61349-3c6d-4714-8094-8e803f03ebca
    resourceVersion: "44916"
    uid: e57fe92b-d291-4c4a-8177-cf49c2232299
  spec:
    sourcePod: network-check-source-8894fc9bd-hqxdd
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T21:16:56Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.090637ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:40:56Z"
    - latency: 1.660285ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T21:40:56Z"
    - latency: 871.906µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:39:56Z"
    - latency: 1.585324ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T21:39:56Z"
    - latency: 1.185852ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:38:56Z"
    - latency: 2.107138ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T21:38:56Z"
    - latency: 762.641µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:37:56Z"
    - latency: 1.579664ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T21:37:56Z"
    - latency: 866.008µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T21:36:56Z"
    - latency: 1.836122ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T21:36:56Z"
kind: List
metadata:
  resourceVersion: ""