apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:13:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-111-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-111.ec2.internal
      uid: 4670cc1c-c606-4c75-bdb0-d419c6792c95
    resourceVersion: "106263"
    uid: 19b18b46-4bd9-4c7c-a4f5-689fd6cdc1d7
  spec:
    sourcePod: network-check-source-7d88cb55d8-dbf99
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:20:34Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.120723ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:51:34Z"
    - latency: 963.226µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:50:34Z"
    - latency: 1.416484ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:49:34Z"
    - latency: 848.233µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:48:34Z"
    - latency: 1.191067ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:47:34Z"
    - latency: 867.585µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:46:34Z"
    - latency: 819.42µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:45:34Z"
    - latency: 1.063295ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:44:34Z"
    - latency: 853.052µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:43:34Z"
    - latency: 1.035508ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:42:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:13:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-111-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-111.ec2.internal
      uid: 4670cc1c-c606-4c75-bdb0-d419c6792c95
    resourceVersion: "109607"
    uid: 1a9b5d1b-7b25-47b2-8c6a-c74eb4347fe5
  spec:
    sourcePod: network-check-source-7d88cb55d8-dbf99
    targetEndpoint: aa9909fac3272479a8f8d8923d568884-e2d1fad4d448ae5c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:19:34Z"
      message: 'load-balancer-api-external: tcp connection to aa9909fac3272479a8f8d8923d568884-e2d1fad4d448ae5c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.256291ms
      message: 'load-balancer-api-external: tcp connection to aa9909fac3272479a8f8d8923d568884-e2d1fad4d448ae5c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:55:34Z"
    - latency: 6.814547ms
      message: 'load-balancer-api-external: resolved host name aa9909fac3272479a8f8d8923d568884-e2d1fad4d448ae5c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:55:34Z"
    - latency: 6.442587ms
      message: 'load-balancer-api-external: tcp connection to aa9909fac3272479a8f8d8923d568884-e2d1fad4d448ae5c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:54:34Z"
    - latency: 9.069433ms
      message: 'load-balancer-api-external: resolved host name aa9909fac3272479a8f8d8923d568884-e2d1fad4d448ae5c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:54:34Z"
    - latency: 5.224684ms
      message: 'load-balancer-api-external: tcp connection to aa9909fac3272479a8f8d8923d568884-e2d1fad4d448ae5c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:53:34Z"
    - latency: 10.118059ms
      message: 'load-balancer-api-external: resolved host name aa9909fac3272479a8f8d8923d568884-e2d1fad4d448ae5c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:53:34Z"
    - latency: 4.446239ms
      message: 'load-balancer-api-external: tcp connection to aa9909fac3272479a8f8d8923d568884-e2d1fad4d448ae5c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:52:34Z"
    - latency: 7.095773ms
      message: 'load-balancer-api-external: resolved host name aa9909fac3272479a8f8d8923d568884-e2d1fad4d448ae5c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:52:34Z"
    - latency: 5.375948ms
      message: 'load-balancer-api-external: tcp connection to aa9909fac3272479a8f8d8923d568884-e2d1fad4d448ae5c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:51:34Z"
    - latency: 6.955873ms
      message: 'load-balancer-api-external: resolved host name aa9909fac3272479a8f8d8923d568884-e2d1fad4d448ae5c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:51:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:13:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-111-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-111.ec2.internal
      uid: 4670cc1c-c606-4c75-bdb0-d419c6792c95
    resourceVersion: "109606"
    uid: 3cdb7db6-9cee-41f2-95e6-96b2f530a1e8
  spec:
    sourcePod: network-check-source-7d88cb55d8-dbf99
    targetEndpoint: aa9909fac3272479a8f8d8923d568884-e2d1fad4d448ae5c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:19:34Z"
      message: 'load-balancer-api-internal: tcp connection to aa9909fac3272479a8f8d8923d568884-e2d1fad4d448ae5c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.486215ms
      message: 'load-balancer-api-internal: tcp connection to aa9909fac3272479a8f8d8923d568884-e2d1fad4d448ae5c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:55:34Z"
    - latency: 6.738782ms
      message: 'load-balancer-api-internal: resolved host name aa9909fac3272479a8f8d8923d568884-e2d1fad4d448ae5c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:55:34Z"
    - latency: 6.437525ms
      message: 'load-balancer-api-internal: tcp connection to aa9909fac3272479a8f8d8923d568884-e2d1fad4d448ae5c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:54:34Z"
    - latency: 9.002522ms
      message: 'load-balancer-api-internal: resolved host name aa9909fac3272479a8f8d8923d568884-e2d1fad4d448ae5c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:54:34Z"
    - latency: 5.243032ms
      message: 'load-balancer-api-internal: tcp connection to aa9909fac3272479a8f8d8923d568884-e2d1fad4d448ae5c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:53:34Z"
    - latency: 10.037144ms
      message: 'load-balancer-api-internal: resolved host name aa9909fac3272479a8f8d8923d568884-e2d1fad4d448ae5c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:53:34Z"
    - latency: 4.486364ms
      message: 'load-balancer-api-internal: tcp connection to aa9909fac3272479a8f8d8923d568884-e2d1fad4d448ae5c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:52:34Z"
    - latency: 7.005338ms
      message: 'load-balancer-api-internal: resolved host name aa9909fac3272479a8f8d8923d568884-e2d1fad4d448ae5c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:52:34Z"
    - latency: 4.660094ms
      message: 'load-balancer-api-internal: tcp connection to aa9909fac3272479a8f8d8923d568884-e2d1fad4d448ae5c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:51:34Z"
    - latency: 7.042923ms
      message: 'load-balancer-api-internal: resolved host name aa9909fac3272479a8f8d8923d568884-e2d1fad4d448ae5c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:51:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:13:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-111-to-network-check-target-ip-10-0-133-215
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-111.ec2.internal
      uid: 4670cc1c-c606-4c75-bdb0-d419c6792c95
    resourceVersion: "106260"
    uid: 36392c2e-b67d-49f5-b7b2-3a22c1ad27ed
  spec:
    sourcePod: network-check-source-7d88cb55d8-dbf99
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:20:34Z"
      message: 'network-check-target-ip-10-0-133-215: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.244895ms
      message: 'network-check-target-ip-10-0-133-215: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:51:34Z"
    - latency: 2.504861ms
      message: 'network-check-target-ip-10-0-133-215: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:50:34Z"
    - latency: 2.180783ms
      message: 'network-check-target-ip-10-0-133-215: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:49:34Z"
    - latency: 3.156409ms
      message: 'network-check-target-ip-10-0-133-215: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:48:34Z"
    - latency: 2.491511ms
      message: 'network-check-target-ip-10-0-133-215: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:47:34Z"
    - latency: 2.368273ms
      message: 'network-check-target-ip-10-0-133-215: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:46:34Z"
    - latency: 2.282187ms
      message: 'network-check-target-ip-10-0-133-215: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:45:34Z"
    - latency: 2.283964ms
      message: 'network-check-target-ip-10-0-133-215: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:44:34Z"
    - latency: 2.358432ms
      message: 'network-check-target-ip-10-0-133-215: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:43:34Z"
    - latency: 3.050779ms
      message: 'network-check-target-ip-10-0-133-215: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:42:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:13:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-111-to-network-check-target-ip-10-0-136-111
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-111.ec2.internal
      uid: 4670cc1c-c606-4c75-bdb0-d419c6792c95
    resourceVersion: "106259"
    uid: f9558f3b-db07-4962-8dce-c6fe19b7c730
  spec:
    sourcePod: network-check-source-7d88cb55d8-dbf99
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:20:34Z"
      message: 'network-check-target-ip-10-0-136-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.257521ms
      message: 'network-check-target-ip-10-0-136-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:51:34Z"
    - latency: 1.436268ms
      message: 'network-check-target-ip-10-0-136-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:50:34Z"
    - latency: 921.733µs
      message: 'network-check-target-ip-10-0-136-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:49:34Z"
    - latency: 1.870684ms
      message: 'network-check-target-ip-10-0-136-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:48:34Z"
    - latency: 1.727315ms
      message: 'network-check-target-ip-10-0-136-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:47:34Z"
    - latency: 990.206µs
      message: 'network-check-target-ip-10-0-136-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:46:34Z"
    - latency: 845.636µs
      message: 'network-check-target-ip-10-0-136-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:45:34Z"
    - latency: 945.035µs
      message: 'network-check-target-ip-10-0-136-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:44:34Z"
    - latency: 1.006582ms
      message: 'network-check-target-ip-10-0-136-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:43:34Z"
    - latency: 1.071934ms
      message: 'network-check-target-ip-10-0-136-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:42:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:13:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-111-to-network-check-target-ip-10-0-137-238
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-111.ec2.internal
      uid: 4670cc1c-c606-4c75-bdb0-d419c6792c95
    resourceVersion: "106261"
    uid: 533b7888-e073-4fe1-95d1-fcbea0f029bd
  spec:
    sourcePod: network-check-source-7d88cb55d8-dbf99
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:20:34Z"
      message: 'network-check-target-ip-10-0-137-238: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.590297ms
      message: 'network-check-target-ip-10-0-137-238: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:51:34Z"
    - latency: 2.492083ms
      message: 'network-check-target-ip-10-0-137-238: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:50:34Z"
    - latency: 2.51116ms
      message: 'network-check-target-ip-10-0-137-238: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:49:34Z"
    - latency: 2.620734ms
      message: 'network-check-target-ip-10-0-137-238: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:48:34Z"
    - latency: 2.228751ms
      message: 'network-check-target-ip-10-0-137-238: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:47:34Z"
    - latency: 1.957334ms
      message: 'network-check-target-ip-10-0-137-238: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:46:34Z"
    - latency: 1.901431ms
      message: 'network-check-target-ip-10-0-137-238: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:45:34Z"
    - latency: 1.935184ms
      message: 'network-check-target-ip-10-0-137-238: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:44:34Z"
    - latency: 2.017589ms
      message: 'network-check-target-ip-10-0-137-238: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:43:34Z"
    - latency: 1.944493ms
      message: 'network-check-target-ip-10-0-137-238: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:42:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:13:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-111-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-111.ec2.internal
      uid: 4670cc1c-c606-4c75-bdb0-d419c6792c95
    resourceVersion: "109605"
    uid: 647ed79a-ed13-45d4-9160-a3abd02da00a
  spec:
    sourcePod: network-check-source-7d88cb55d8-dbf99
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:19:34Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.115931ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:55:34Z"
    - latency: 1.944435ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:55:34Z"
    - latency: 1.13191ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:54:34Z"
    - latency: 1.77474ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:54:34Z"
    - latency: 1.030827ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:53:34Z"
    - latency: 1.887619ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:53:34Z"
    - latency: 816.722µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:52:34Z"
    - latency: 1.669341ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:52:34Z"
    - latency: 1.096331ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:51:34Z"
    - latency: 1.664859ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T18:51:34Z"
kind: List
metadata:
  resourceVersion: ""