apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T08:24:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-160-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-160.ec2.internal
      uid: d2b9384b-3ce2-4355-b307-6ec53e493365
    resourceVersion: "44689"
    uid: c94cea83-28d6-4862-9c54-12855e539894
  spec:
    sourcePod: network-check-source-6947749cfc-4vxgr
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T08:31:56Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 801.277µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:52:56Z"
    - latency: 1.154689ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:51:56Z"
    - latency: 870.681µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:50:56Z"
    - latency: 1.032048ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:49:56Z"
    - latency: 988.532µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:48:56Z"
    - latency: 854.241µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:47:56Z"
    - latency: 778.296µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:46:56Z"
    - latency: 1.735293ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:45:56Z"
    - latency: 1.072768ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:44:56Z"
    - latency: 801.9µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:43:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T08:24:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-160-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-160.ec2.internal
      uid: d2b9384b-3ce2-4355-b307-6ec53e493365
    resourceVersion: "46726"
    uid: f5390f2b-bec5-4643-8708-15b6262b2503
  spec:
    sourcePod: network-check-source-6947749cfc-4vxgr
    targetEndpoint: a3d59a8e3cc8f455d93af66aa07b3dc4-75a181113c0fc40f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T08:30:56Z"
      message: 'load-balancer-api-external: tcp connection to a3d59a8e3cc8f455d93af66aa07b3dc4-75a181113c0fc40f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 9.237458ms
      message: 'load-balancer-api-external: tcp connection to a3d59a8e3cc8f455d93af66aa07b3dc4-75a181113c0fc40f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:54:56Z"
    - latency: 7.599431ms
      message: 'load-balancer-api-external: resolved host name a3d59a8e3cc8f455d93af66aa07b3dc4-75a181113c0fc40f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T08:54:56Z"
    - latency: 4.624469ms
      message: 'load-balancer-api-external: tcp connection to a3d59a8e3cc8f455d93af66aa07b3dc4-75a181113c0fc40f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:53:56Z"
    - latency: 8.834342ms
      message: 'load-balancer-api-external: resolved host name a3d59a8e3cc8f455d93af66aa07b3dc4-75a181113c0fc40f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T08:53:56Z"
    - latency: 4.02523ms
      message: 'load-balancer-api-external: tcp connection to a3d59a8e3cc8f455d93af66aa07b3dc4-75a181113c0fc40f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:52:56Z"
    - latency: 9.299338ms
      message: 'load-balancer-api-external: resolved host name a3d59a8e3cc8f455d93af66aa07b3dc4-75a181113c0fc40f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T08:52:56Z"
    - latency: 4.225266ms
      message: 'load-balancer-api-external: tcp connection to a3d59a8e3cc8f455d93af66aa07b3dc4-75a181113c0fc40f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:51:56Z"
    - latency: 9.34985ms
      message: 'load-balancer-api-external: resolved host name a3d59a8e3cc8f455d93af66aa07b3dc4-75a181113c0fc40f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T08:51:56Z"
    - latency: 4.123074ms
      message: 'load-balancer-api-external: tcp connection to a3d59a8e3cc8f455d93af66aa07b3dc4-75a181113c0fc40f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:50:56Z"
    - latency: 7.614082ms
      message: 'load-balancer-api-external: resolved host name a3d59a8e3cc8f455d93af66aa07b3dc4-75a181113c0fc40f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T08:50:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T08:24:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-160-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-160.ec2.internal
      uid: d2b9384b-3ce2-4355-b307-6ec53e493365
    resourceVersion: "46725"
    uid: 5e4d0029-5d93-4cb8-90e8-bf0db6f5fb5b
  spec:
    sourcePod: network-check-source-6947749cfc-4vxgr
    targetEndpoint: a3d59a8e3cc8f455d93af66aa07b3dc4-75a181113c0fc40f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T08:30:56Z"
      message: 'load-balancer-api-internal: tcp connection to a3d59a8e3cc8f455d93af66aa07b3dc4-75a181113c0fc40f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.57863ms
      message: 'load-balancer-api-internal: tcp connection to a3d59a8e3cc8f455d93af66aa07b3dc4-75a181113c0fc40f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:54:56Z"
    - latency: 7.668376ms
      message: 'load-balancer-api-internal: resolved host name a3d59a8e3cc8f455d93af66aa07b3dc4-75a181113c0fc40f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T08:54:56Z"
    - latency: 6.249303ms
      message: 'load-balancer-api-internal: tcp connection to a3d59a8e3cc8f455d93af66aa07b3dc4-75a181113c0fc40f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:53:56Z"
    - latency: 8.859955ms
      message: 'load-balancer-api-internal: resolved host name a3d59a8e3cc8f455d93af66aa07b3dc4-75a181113c0fc40f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T08:53:56Z"
    - latency: 6.055496ms
      message: 'load-balancer-api-internal: tcp connection to a3d59a8e3cc8f455d93af66aa07b3dc4-75a181113c0fc40f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:52:56Z"
    - latency: 9.361215ms
      message: 'load-balancer-api-internal: resolved host name a3d59a8e3cc8f455d93af66aa07b3dc4-75a181113c0fc40f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T08:52:56Z"
    - latency: 4.27783ms
      message: 'load-balancer-api-internal: tcp connection to a3d59a8e3cc8f455d93af66aa07b3dc4-75a181113c0fc40f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:51:56Z"
    - latency: 9.318386ms
      message: 'load-balancer-api-internal: resolved host name a3d59a8e3cc8f455d93af66aa07b3dc4-75a181113c0fc40f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T08:51:56Z"
    - latency: 4.04134ms
      message: 'load-balancer-api-internal: tcp connection to a3d59a8e3cc8f455d93af66aa07b3dc4-75a181113c0fc40f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:50:56Z"
    - latency: 7.681666ms
      message: 'load-balancer-api-internal: resolved host name a3d59a8e3cc8f455d93af66aa07b3dc4-75a181113c0fc40f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T08:50:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T08:24:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-160-to-network-check-target-ip-10-0-130-187
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-160.ec2.internal
      uid: d2b9384b-3ce2-4355-b307-6ec53e493365
    resourceVersion: "44687"
    uid: 6dd22859-c58b-4900-81fb-2ab03e1a2c23
  spec:
    sourcePod: network-check-source-6947749cfc-4vxgr
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T08:31:56Z"
      message: 'network-check-target-ip-10-0-130-187: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.210114ms
      message: 'network-check-target-ip-10-0-130-187: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:52:56Z"
    - latency: 2.282751ms
      message: 'network-check-target-ip-10-0-130-187: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:51:56Z"
    - latency: 2.310745ms
      message: 'network-check-target-ip-10-0-130-187: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:50:56Z"
    - latency: 2.22499ms
      message: 'network-check-target-ip-10-0-130-187: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:49:56Z"
    - latency: 2.456182ms
      message: 'network-check-target-ip-10-0-130-187: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:48:56Z"
    - latency: 2.304947ms
      message: 'network-check-target-ip-10-0-130-187: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:47:56Z"
    - latency: 2.388742ms
      message: 'network-check-target-ip-10-0-130-187: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:46:56Z"
    - latency: 2.413468ms
      message: 'network-check-target-ip-10-0-130-187: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:45:56Z"
    - latency: 2.685709ms
      message: 'network-check-target-ip-10-0-130-187: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:44:56Z"
    - latency: 2.308765ms
      message: 'network-check-target-ip-10-0-130-187: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:43:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T08:24:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-160-to-network-check-target-ip-10-0-134-160
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-160.ec2.internal
      uid: d2b9384b-3ce2-4355-b307-6ec53e493365
    resourceVersion: "44686"
    uid: 9988a70d-3814-452d-849c-21d92b4bda2a
  spec:
    sourcePod: network-check-source-6947749cfc-4vxgr
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T08:31:56Z"
      message: 'network-check-target-ip-10-0-134-160: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 968.715µs
      message: 'network-check-target-ip-10-0-134-160: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:52:56Z"
    - latency: 932.443µs
      message: 'network-check-target-ip-10-0-134-160: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:51:56Z"
    - latency: 1.510691ms
      message: 'network-check-target-ip-10-0-134-160: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:50:56Z"
    - latency: 869.779µs
      message: 'network-check-target-ip-10-0-134-160: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:49:56Z"
    - latency: 989.281µs
      message: 'network-check-target-ip-10-0-134-160: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:48:56Z"
    - latency: 1.271758ms
      message: 'network-check-target-ip-10-0-134-160: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:47:56Z"
    - latency: 740.498µs
      message: 'network-check-target-ip-10-0-134-160: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:46:56Z"
    - latency: 916.184µs
      message: 'network-check-target-ip-10-0-134-160: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:45:56Z"
    - latency: 975.309µs
      message: 'network-check-target-ip-10-0-134-160: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:44:56Z"
    - latency: 846.48µs
      message: 'network-check-target-ip-10-0-134-160: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:43:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T08:24:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-160-to-network-check-target-ip-10-0-136-100
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-160.ec2.internal
      uid: d2b9384b-3ce2-4355-b307-6ec53e493365
    resourceVersion: "44688"
    uid: 1496735d-c025-4aac-b978-d4d69659f80b
  spec:
    sourcePod: network-check-source-6947749cfc-4vxgr
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T08:31:56Z"
      message: 'network-check-target-ip-10-0-136-100: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.920371ms
      message: 'network-check-target-ip-10-0-136-100: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:52:56Z"
    - latency: 2.065462ms
      message: 'network-check-target-ip-10-0-136-100: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:51:56Z"
    - latency: 2.628833ms
      message: 'network-check-target-ip-10-0-136-100: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:50:56Z"
    - latency: 2.112724ms
      message: 'network-check-target-ip-10-0-136-100: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:49:56Z"
    - latency: 2.166977ms
      message: 'network-check-target-ip-10-0-136-100: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:48:56Z"
    - latency: 2.452239ms
      message: 'network-check-target-ip-10-0-136-100: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:47:56Z"
    - latency: 2.166037ms
      message: 'network-check-target-ip-10-0-136-100: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:46:56Z"
    - latency: 1.756511ms
      message: 'network-check-target-ip-10-0-136-100: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:45:56Z"
    - latency: 2.634136ms
      message: 'network-check-target-ip-10-0-136-100: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:44:56Z"
    - latency: 2.271566ms
      message: 'network-check-target-ip-10-0-136-100: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:43:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T08:24:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-160-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-160.ec2.internal
      uid: d2b9384b-3ce2-4355-b307-6ec53e493365
    resourceVersion: "46724"
    uid: e948be23-bd7c-4988-ad62-63eaed337589
  spec:
    sourcePod: network-check-source-6947749cfc-4vxgr
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T08:30:56Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 884.089µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:54:56Z"
    - latency: 1.829724ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T08:54:56Z"
    - latency: 888.12µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:53:56Z"
    - latency: 2.402705ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T08:53:56Z"
    - latency: 981.385µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:52:56Z"
    - latency: 1.918692ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T08:52:56Z"
    - latency: 840.624µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:51:56Z"
    - latency: 1.644658ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T08:51:56Z"
    - latency: 889.053µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T08:50:56Z"
    - latency: 1.764718ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T08:50:56Z"
kind: List
metadata:
  resourceVersion: ""