apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T15:34:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-112-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-112.ec2.internal
      uid: 35351a3b-68cc-44e7-8860-30ffd418e010
    resourceVersion: "53625"
    uid: d325cba9-4fa4-461f-861a-4ab25a81c0a0
  spec:
    sourcePod: network-check-source-869dcfcdcd-cxxzz
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T15:42: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.794577ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:10:01Z"
    - latency: 902.417µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:09:01Z"
    - latency: 975.772µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:08:01Z"
    - latency: 933.701µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:07:01Z"
    - latency: 1.052622ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:06:01Z"
    - latency: 1.149094ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:05:01Z"
    - latency: 1.172297ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:04:01Z"
    - latency: 987.402µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:03:01Z"
    - latency: 1.004749ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:02:01Z"
    - latency: 1.005327ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:01:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T15:35:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-112-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-112.ec2.internal
      uid: 35351a3b-68cc-44e7-8860-30ffd418e010
    resourceVersion: "48805"
    uid: acfb28a2-bcd2-4d76-992b-d56cb3565455
  spec:
    sourcePod: network-check-source-869dcfcdcd-cxxzz
    targetEndpoint: a6ba6d7feaf0e41dd975508abe9f3423-6e231ad46310605a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T15:41:01Z"
      message: 'load-balancer-api-external: tcp connection to a6ba6d7feaf0e41dd975508abe9f3423-6e231ad46310605a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.155815ms
      message: 'load-balancer-api-external: tcp connection to a6ba6d7feaf0e41dd975508abe9f3423-6e231ad46310605a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:05:01Z"
    - latency: 7.832453ms
      message: 'load-balancer-api-external: resolved host name a6ba6d7feaf0e41dd975508abe9f3423-6e231ad46310605a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T16:05:01Z"
    - latency: 4.464173ms
      message: 'load-balancer-api-external: tcp connection to a6ba6d7feaf0e41dd975508abe9f3423-6e231ad46310605a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:04:01Z"
    - latency: 6.858677ms
      message: 'load-balancer-api-external: resolved host name a6ba6d7feaf0e41dd975508abe9f3423-6e231ad46310605a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T16:04:01Z"
    - latency: 4.483189ms
      message: 'load-balancer-api-external: tcp connection to a6ba6d7feaf0e41dd975508abe9f3423-6e231ad46310605a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:03:01Z"
    - latency: 12.463348ms
      message: 'load-balancer-api-external: resolved host name a6ba6d7feaf0e41dd975508abe9f3423-6e231ad46310605a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T16:03:01Z"
    - latency: 4.126052ms
      message: 'load-balancer-api-external: tcp connection to a6ba6d7feaf0e41dd975508abe9f3423-6e231ad46310605a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:02:01Z"
    - latency: 9.902505ms
      message: 'load-balancer-api-external: resolved host name a6ba6d7feaf0e41dd975508abe9f3423-6e231ad46310605a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T16:02:01Z"
    - latency: 4.356694ms
      message: 'load-balancer-api-external: tcp connection to a6ba6d7feaf0e41dd975508abe9f3423-6e231ad46310605a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:01:01Z"
    - latency: 10.462078ms
      message: 'load-balancer-api-external: resolved host name a6ba6d7feaf0e41dd975508abe9f3423-6e231ad46310605a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T16:01:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T15:34:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-112-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-112.ec2.internal
      uid: 35351a3b-68cc-44e7-8860-30ffd418e010
    resourceVersion: "48806"
    uid: 568f4a1f-0347-4cc4-9eb9-37edeedb8a1b
  spec:
    sourcePod: network-check-source-869dcfcdcd-cxxzz
    targetEndpoint: a6ba6d7feaf0e41dd975508abe9f3423-6e231ad46310605a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T15:41:01Z"
      message: 'load-balancer-api-internal: tcp connection to a6ba6d7feaf0e41dd975508abe9f3423-6e231ad46310605a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.176539ms
      message: 'load-balancer-api-internal: tcp connection to a6ba6d7feaf0e41dd975508abe9f3423-6e231ad46310605a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:05:01Z"
    - latency: 7.803847ms
      message: 'load-balancer-api-internal: resolved host name a6ba6d7feaf0e41dd975508abe9f3423-6e231ad46310605a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T16:05:01Z"
    - latency: 4.484707ms
      message: 'load-balancer-api-internal: tcp connection to a6ba6d7feaf0e41dd975508abe9f3423-6e231ad46310605a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:04:01Z"
    - latency: 6.784729ms
      message: 'load-balancer-api-internal: resolved host name a6ba6d7feaf0e41dd975508abe9f3423-6e231ad46310605a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T16:04:01Z"
    - latency: 3.696347ms
      message: 'load-balancer-api-internal: tcp connection to a6ba6d7feaf0e41dd975508abe9f3423-6e231ad46310605a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:03:01Z"
    - latency: 12.41909ms
      message: 'load-balancer-api-internal: resolved host name a6ba6d7feaf0e41dd975508abe9f3423-6e231ad46310605a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T16:03:01Z"
    - latency: 4.164106ms
      message: 'load-balancer-api-internal: tcp connection to a6ba6d7feaf0e41dd975508abe9f3423-6e231ad46310605a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:02:01Z"
    - latency: 9.866742ms
      message: 'load-balancer-api-internal: resolved host name a6ba6d7feaf0e41dd975508abe9f3423-6e231ad46310605a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T16:02:01Z"
    - latency: 4.083628ms
      message: 'load-balancer-api-internal: tcp connection to a6ba6d7feaf0e41dd975508abe9f3423-6e231ad46310605a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:01:01Z"
    - latency: 10.419508ms
      message: 'load-balancer-api-internal: resolved host name a6ba6d7feaf0e41dd975508abe9f3423-6e231ad46310605a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T16:01:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T15:34:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-112-to-network-check-target-ip-10-0-128-112
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-112.ec2.internal
      uid: 35351a3b-68cc-44e7-8860-30ffd418e010
    resourceVersion: "53622"
    uid: f828a8ff-3720-4190-b53e-de87fc4472b3
  spec:
    sourcePod: network-check-source-869dcfcdcd-cxxzz
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T15:42:01Z"
      message: 'network-check-target-ip-10-0-128-112: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 816.211µs
      message: 'network-check-target-ip-10-0-128-112: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:10:01Z"
    - latency: 1.12672ms
      message: 'network-check-target-ip-10-0-128-112: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:09:01Z"
    - latency: 1.278571ms
      message: 'network-check-target-ip-10-0-128-112: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:08:01Z"
    - latency: 1.479133ms
      message: 'network-check-target-ip-10-0-128-112: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:07:01Z"
    - latency: 918.392µs
      message: 'network-check-target-ip-10-0-128-112: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:06:01Z"
    - latency: 1.431357ms
      message: 'network-check-target-ip-10-0-128-112: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:05:01Z"
    - latency: 1.084144ms
      message: 'network-check-target-ip-10-0-128-112: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:04:01Z"
    - latency: 1.161092ms
      message: 'network-check-target-ip-10-0-128-112: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:03:01Z"
    - latency: 909.832µs
      message: 'network-check-target-ip-10-0-128-112: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:02:01Z"
    - latency: 1.465484ms
      message: 'network-check-target-ip-10-0-128-112: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:01:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T15:34:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-112-to-network-check-target-ip-10-0-133-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-112.ec2.internal
      uid: 35351a3b-68cc-44e7-8860-30ffd418e010
    resourceVersion: "53623"
    uid: 1b98107d-dada-4166-937c-8f95e08d2514
  spec:
    sourcePod: network-check-source-869dcfcdcd-cxxzz
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T15:42:01Z"
      message: 'network-check-target-ip-10-0-133-0: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.219088ms
      message: 'network-check-target-ip-10-0-133-0: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:10:01Z"
    - latency: 2.401128ms
      message: 'network-check-target-ip-10-0-133-0: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:09:01Z"
    - latency: 2.28044ms
      message: 'network-check-target-ip-10-0-133-0: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:08:01Z"
    - latency: 2.363304ms
      message: 'network-check-target-ip-10-0-133-0: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:07:01Z"
    - latency: 2.212347ms
      message: 'network-check-target-ip-10-0-133-0: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:06:01Z"
    - latency: 2.47399ms
      message: 'network-check-target-ip-10-0-133-0: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:05:01Z"
    - latency: 2.069128ms
      message: 'network-check-target-ip-10-0-133-0: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:04:01Z"
    - latency: 2.381972ms
      message: 'network-check-target-ip-10-0-133-0: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:03:01Z"
    - latency: 2.257578ms
      message: 'network-check-target-ip-10-0-133-0: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:02:01Z"
    - latency: 2.169396ms
      message: 'network-check-target-ip-10-0-133-0: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:01:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T15:34:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-112-to-network-check-target-ip-10-0-133-183
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-112.ec2.internal
      uid: 35351a3b-68cc-44e7-8860-30ffd418e010
    resourceVersion: "53624"
    uid: 78c01378-38f3-407a-a461-e1050b496d0c
  spec:
    sourcePod: network-check-source-869dcfcdcd-cxxzz
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T15:42:01Z"
      message: 'network-check-target-ip-10-0-133-183: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.776342ms
      message: 'network-check-target-ip-10-0-133-183: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:10:01Z"
    - latency: 2.418145ms
      message: 'network-check-target-ip-10-0-133-183: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:09:01Z"
    - latency: 2.500059ms
      message: 'network-check-target-ip-10-0-133-183: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:08:01Z"
    - latency: 2.258661ms
      message: 'network-check-target-ip-10-0-133-183: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:07:01Z"
    - latency: 2.324654ms
      message: 'network-check-target-ip-10-0-133-183: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:06:01Z"
    - latency: 2.524462ms
      message: 'network-check-target-ip-10-0-133-183: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:05:01Z"
    - latency: 2.379327ms
      message: 'network-check-target-ip-10-0-133-183: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:04:01Z"
    - latency: 2.49242ms
      message: 'network-check-target-ip-10-0-133-183: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:03:01Z"
    - latency: 2.356854ms
      message: 'network-check-target-ip-10-0-133-183: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:02:01Z"
    - latency: 2.115212ms
      message: 'network-check-target-ip-10-0-133-183: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:01:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T15:34:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-112-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-112.ec2.internal
      uid: 35351a3b-68cc-44e7-8860-30ffd418e010
    resourceVersion: "48804"
    uid: fda83319-8b63-49fd-81a9-469bb9ad4e20
  spec:
    sourcePod: network-check-source-869dcfcdcd-cxxzz
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T15:41:01Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.226621ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:05:01Z"
    - latency: 1.733649ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T16:05:01Z"
    - latency: 861.004µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:04:01Z"
    - latency: 1.695887ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T16:04:01Z"
    - latency: 884.895µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:03:01Z"
    - latency: 2.094523ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T16:03:01Z"
    - latency: 771.227µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:02:01Z"
    - latency: 1.741163ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T16:02:01Z"
    - latency: 898.555µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T16:01:01Z"
    - latency: 1.5516ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T16:01:01Z"
kind: List
metadata:
  resourceVersion: ""