apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T21:49:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-4-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-4.ec2.internal
      uid: c87904a8-139e-40f3-b665-56a6058fcad3
    resourceVersion: "69097"
    uid: 95cb1994-75be-467d-b690-88213dcadb1c
  spec:
    sourcePod: network-check-source-7bc5b6bf85-fjjct
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T21:56:11Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.211345ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:38:11Z"
    - latency: 1.248214ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:37:11Z"
    - latency: 1.195134ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:36:11Z"
    - latency: 1.256847ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:35:11Z"
    - latency: 1.02109ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:34:11Z"
    - latency: 941.386µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:33:11Z"
    - latency: 1.452715ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:32:11Z"
    - latency: 1.136382ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:31:11Z"
    - latency: 1.303992ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:30:11Z"
    - latency: 867.641µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:29:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T21:49:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-4-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-4.ec2.internal
      uid: c87904a8-139e-40f3-b665-56a6058fcad3
    resourceVersion: "74889"
    uid: 4d64e0c1-3e06-47cb-b734-e7788e6669f3
  spec:
    sourcePod: network-check-source-7bc5b6bf85-fjjct
    targetEndpoint: a9afe288caea44018a0953c2a21408ee-53e4f526dde1cf28.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T21:55:11Z"
      message: 'load-balancer-api-external: tcp connection to a9afe288caea44018a0953c2a21408ee-53e4f526dde1cf28.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.662746ms
      message: 'load-balancer-api-external: tcp connection to a9afe288caea44018a0953c2a21408ee-53e4f526dde1cf28.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:43:11Z"
    - latency: 9.772653ms
      message: 'load-balancer-api-external: resolved host name a9afe288caea44018a0953c2a21408ee-53e4f526dde1cf28.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:43:11Z"
    - latency: 5.024401ms
      message: 'load-balancer-api-external: tcp connection to a9afe288caea44018a0953c2a21408ee-53e4f526dde1cf28.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:42:11Z"
    - latency: 9.035281ms
      message: 'load-balancer-api-external: resolved host name a9afe288caea44018a0953c2a21408ee-53e4f526dde1cf28.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:42:11Z"
    - latency: 6.586781ms
      message: 'load-balancer-api-external: tcp connection to a9afe288caea44018a0953c2a21408ee-53e4f526dde1cf28.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:41:11Z"
    - latency: 7.775209ms
      message: 'load-balancer-api-external: resolved host name a9afe288caea44018a0953c2a21408ee-53e4f526dde1cf28.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:41:11Z"
    - latency: 3.683574ms
      message: 'load-balancer-api-external: tcp connection to a9afe288caea44018a0953c2a21408ee-53e4f526dde1cf28.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:40:11Z"
    - latency: 9.469606ms
      message: 'load-balancer-api-external: resolved host name a9afe288caea44018a0953c2a21408ee-53e4f526dde1cf28.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:40:11Z"
    - latency: 6.213334ms
      message: 'load-balancer-api-external: tcp connection to a9afe288caea44018a0953c2a21408ee-53e4f526dde1cf28.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:39:11Z"
    - latency: 8.535176ms
      message: 'load-balancer-api-external: resolved host name a9afe288caea44018a0953c2a21408ee-53e4f526dde1cf28.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:39:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T21:49:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-4-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-4.ec2.internal
      uid: c87904a8-139e-40f3-b665-56a6058fcad3
    resourceVersion: "74888"
    uid: ea94711c-80d9-4dcb-b4d8-34bbdfe2d661
  spec:
    sourcePod: network-check-source-7bc5b6bf85-fjjct
    targetEndpoint: a9afe288caea44018a0953c2a21408ee-53e4f526dde1cf28.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T21:55:11Z"
      message: 'load-balancer-api-internal: tcp connection to a9afe288caea44018a0953c2a21408ee-53e4f526dde1cf28.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.707887ms
      message: 'load-balancer-api-internal: tcp connection to a9afe288caea44018a0953c2a21408ee-53e4f526dde1cf28.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:43:11Z"
    - latency: 9.788875ms
      message: 'load-balancer-api-internal: resolved host name a9afe288caea44018a0953c2a21408ee-53e4f526dde1cf28.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:43:11Z"
    - latency: 4.437333ms
      message: 'load-balancer-api-internal: tcp connection to a9afe288caea44018a0953c2a21408ee-53e4f526dde1cf28.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:42:11Z"
    - latency: 9.021276ms
      message: 'load-balancer-api-internal: resolved host name a9afe288caea44018a0953c2a21408ee-53e4f526dde1cf28.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:42:11Z"
    - latency: 6.555801ms
      message: 'load-balancer-api-internal: tcp connection to a9afe288caea44018a0953c2a21408ee-53e4f526dde1cf28.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:41:11Z"
    - latency: 7.806428ms
      message: 'load-balancer-api-internal: resolved host name a9afe288caea44018a0953c2a21408ee-53e4f526dde1cf28.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:41:11Z"
    - latency: 3.695394ms
      message: 'load-balancer-api-internal: tcp connection to a9afe288caea44018a0953c2a21408ee-53e4f526dde1cf28.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:40:11Z"
    - latency: 9.447069ms
      message: 'load-balancer-api-internal: resolved host name a9afe288caea44018a0953c2a21408ee-53e4f526dde1cf28.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:40:11Z"
    - latency: 5.849881ms
      message: 'load-balancer-api-internal: tcp connection to a9afe288caea44018a0953c2a21408ee-53e4f526dde1cf28.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:39:11Z"
    - latency: 8.497989ms
      message: 'load-balancer-api-internal: resolved host name a9afe288caea44018a0953c2a21408ee-53e4f526dde1cf28.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:39:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T21:49:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-4-to-network-check-target-ip-10-0-129-11
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-4.ec2.internal
      uid: c87904a8-139e-40f3-b665-56a6058fcad3
    resourceVersion: "69094"
    uid: 236df004-2aba-4253-859d-c91c53a61afd
  spec:
    sourcePod: network-check-source-7bc5b6bf85-fjjct
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T21:56:11Z"
      message: 'network-check-target-ip-10-0-129-11: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.118628ms
      message: 'network-check-target-ip-10-0-129-11: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:38:11Z"
    - latency: 2.181223ms
      message: 'network-check-target-ip-10-0-129-11: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:37:11Z"
    - latency: 2.322138ms
      message: 'network-check-target-ip-10-0-129-11: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:36:11Z"
    - latency: 2.469203ms
      message: 'network-check-target-ip-10-0-129-11: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:35:11Z"
    - latency: 2.363685ms
      message: 'network-check-target-ip-10-0-129-11: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:34:11Z"
    - latency: 2.191626ms
      message: 'network-check-target-ip-10-0-129-11: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:33:11Z"
    - latency: 2.206507ms
      message: 'network-check-target-ip-10-0-129-11: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:32:11Z"
    - latency: 1.873854ms
      message: 'network-check-target-ip-10-0-129-11: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:31:11Z"
    - latency: 2.174386ms
      message: 'network-check-target-ip-10-0-129-11: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:30:11Z"
    - latency: 1.989963ms
      message: 'network-check-target-ip-10-0-129-11: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:29:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T21:49:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-4-to-network-check-target-ip-10-0-131-14
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-4.ec2.internal
      uid: c87904a8-139e-40f3-b665-56a6058fcad3
    resourceVersion: "69095"
    uid: cac7706d-6f8a-474f-a99b-e3a5acaa8214
  spec:
    sourcePod: network-check-source-7bc5b6bf85-fjjct
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T21:56:11Z"
      message: 'network-check-target-ip-10-0-131-14: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.160549ms
      message: 'network-check-target-ip-10-0-131-14: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:38:11Z"
    - latency: 2.504658ms
      message: 'network-check-target-ip-10-0-131-14: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:37:11Z"
    - latency: 2.421258ms
      message: 'network-check-target-ip-10-0-131-14: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:36:11Z"
    - latency: 2.492335ms
      message: 'network-check-target-ip-10-0-131-14: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:35:11Z"
    - latency: 2.185332ms
      message: 'network-check-target-ip-10-0-131-14: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:34:11Z"
    - latency: 2.331982ms
      message: 'network-check-target-ip-10-0-131-14: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:33:11Z"
    - latency: 2.063069ms
      message: 'network-check-target-ip-10-0-131-14: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:32:11Z"
    - latency: 2.388062ms
      message: 'network-check-target-ip-10-0-131-14: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:31:11Z"
    - latency: 2.376799ms
      message: 'network-check-target-ip-10-0-131-14: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:30:11Z"
    - latency: 1.863634ms
      message: 'network-check-target-ip-10-0-131-14: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:29:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T21:49:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-4-to-network-check-target-ip-10-0-131-4
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-4.ec2.internal
      uid: c87904a8-139e-40f3-b665-56a6058fcad3
    resourceVersion: "69093"
    uid: 1026f1b1-c339-4101-8942-1284eeb233be
  spec:
    sourcePod: network-check-source-7bc5b6bf85-fjjct
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T21:56:11Z"
      message: 'network-check-target-ip-10-0-131-4: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.127744ms
      message: 'network-check-target-ip-10-0-131-4: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:38:11Z"
    - latency: 1.121262ms
      message: 'network-check-target-ip-10-0-131-4: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:37:11Z"
    - latency: 1.208882ms
      message: 'network-check-target-ip-10-0-131-4: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:36:11Z"
    - latency: 999.237µs
      message: 'network-check-target-ip-10-0-131-4: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:35:11Z"
    - latency: 1.126941ms
      message: 'network-check-target-ip-10-0-131-4: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:34:11Z"
    - latency: 1.134579ms
      message: 'network-check-target-ip-10-0-131-4: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:33:11Z"
    - latency: 1.251767ms
      message: 'network-check-target-ip-10-0-131-4: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:32:11Z"
    - latency: 820.998µs
      message: 'network-check-target-ip-10-0-131-4: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:31:11Z"
    - latency: 1.628637ms
      message: 'network-check-target-ip-10-0-131-4: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:30:11Z"
    - latency: 1.173928ms
      message: 'network-check-target-ip-10-0-131-4: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:29:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T21:49:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-4-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-4.ec2.internal
      uid: c87904a8-139e-40f3-b665-56a6058fcad3
    resourceVersion: "74887"
    uid: 3eb1351e-d50a-43b2-95f3-7311c0e26c23
  spec:
    sourcePod: network-check-source-7bc5b6bf85-fjjct
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T21:55:11Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.221407ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:43:11Z"
    - latency: 1.940257ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:43:11Z"
    - latency: 998.941µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:42:11Z"
    - latency: 2.038609ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:42:11Z"
    - latency: 1.135824ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:41:11Z"
    - latency: 1.954602ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:41:11Z"
    - latency: 850.438µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:40:11Z"
    - latency: 2.196409ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:40:11Z"
    - latency: 1.178726ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T22:39:11Z"
    - latency: 1.922128ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T22:39:11Z"
kind: List
metadata:
  resourceVersion: ""