apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T10:22:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-166-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-166.ec2.internal
      uid: 82e8aedb-4d6f-4ad4-85f7-facf7ca21452
    resourceVersion: "55477"
    uid: b1fa38fd-97f1-45b3-a0c8-52d6a333a71f
  spec:
    sourcePod: network-check-source-685456655f-nspbh
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T10:29:38Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.253008ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:57:38Z"
    - latency: 1.129686ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:56:38Z"
    - latency: 1.447804ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:55:38Z"
    - latency: 892.942µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:54:38Z"
    - latency: 809.719µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:53:38Z"
    - latency: 842.711µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:52:38Z"
    - latency: 1.49814ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:51:38Z"
    - latency: 1.22577ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:50:38Z"
    - latency: 1.429419ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:49:38Z"
    - latency: 1.11185ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:48:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T10:22:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-166-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-166.ec2.internal
      uid: 82e8aedb-4d6f-4ad4-85f7-facf7ca21452
    resourceVersion: "56364"
    uid: 466f7754-a794-4ae7-9ea1-01ea118c05fc
  spec:
    sourcePod: network-check-source-685456655f-nspbh
    targetEndpoint: a92acdfc50c74437987fd8ab85c2712d-5d866c8de5c62306.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T10:28:38Z"
      message: 'load-balancer-api-external: tcp connection to a92acdfc50c74437987fd8ab85c2712d-5d866c8de5c62306.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.628809ms
      message: 'load-balancer-api-external: tcp connection to a92acdfc50c74437987fd8ab85c2712d-5d866c8de5c62306.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:58:38Z"
    - latency: 7.363723ms
      message: 'load-balancer-api-external: resolved host name a92acdfc50c74437987fd8ab85c2712d-5d866c8de5c62306.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T10:58:38Z"
    - latency: 4.06665ms
      message: 'load-balancer-api-external: tcp connection to a92acdfc50c74437987fd8ab85c2712d-5d866c8de5c62306.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:57:38Z"
    - latency: 7.173707ms
      message: 'load-balancer-api-external: resolved host name a92acdfc50c74437987fd8ab85c2712d-5d866c8de5c62306.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T10:57:38Z"
    - latency: 4.102401ms
      message: 'load-balancer-api-external: tcp connection to a92acdfc50c74437987fd8ab85c2712d-5d866c8de5c62306.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:56:38Z"
    - latency: 6.673946ms
      message: 'load-balancer-api-external: resolved host name a92acdfc50c74437987fd8ab85c2712d-5d866c8de5c62306.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T10:56:38Z"
    - latency: 4.519564ms
      message: 'load-balancer-api-external: tcp connection to a92acdfc50c74437987fd8ab85c2712d-5d866c8de5c62306.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:55:38Z"
    - latency: 7.127044ms
      message: 'load-balancer-api-external: resolved host name a92acdfc50c74437987fd8ab85c2712d-5d866c8de5c62306.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T10:55:38Z"
    - latency: 2.915541ms
      message: 'load-balancer-api-external: tcp connection to a92acdfc50c74437987fd8ab85c2712d-5d866c8de5c62306.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:54:38Z"
    - latency: 8.368862ms
      message: 'load-balancer-api-external: resolved host name a92acdfc50c74437987fd8ab85c2712d-5d866c8de5c62306.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T10:54:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T10:22:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-166-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-166.ec2.internal
      uid: 82e8aedb-4d6f-4ad4-85f7-facf7ca21452
    resourceVersion: "56363"
    uid: 80f6a796-f194-4968-93f0-18f8a602383c
  spec:
    sourcePod: network-check-source-685456655f-nspbh
    targetEndpoint: a92acdfc50c74437987fd8ab85c2712d-5d866c8de5c62306.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T10:28:38Z"
      message: 'load-balancer-api-internal: tcp connection to a92acdfc50c74437987fd8ab85c2712d-5d866c8de5c62306.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.697944ms
      message: 'load-balancer-api-internal: tcp connection to a92acdfc50c74437987fd8ab85c2712d-5d866c8de5c62306.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:58:38Z"
    - latency: 7.391209ms
      message: 'load-balancer-api-internal: resolved host name a92acdfc50c74437987fd8ab85c2712d-5d866c8de5c62306.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T10:58:38Z"
    - latency: 4.035386ms
      message: 'load-balancer-api-internal: tcp connection to a92acdfc50c74437987fd8ab85c2712d-5d866c8de5c62306.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:57:38Z"
    - latency: 7.106119ms
      message: 'load-balancer-api-internal: resolved host name a92acdfc50c74437987fd8ab85c2712d-5d866c8de5c62306.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T10:57:38Z"
    - latency: 4.144063ms
      message: 'load-balancer-api-internal: tcp connection to a92acdfc50c74437987fd8ab85c2712d-5d866c8de5c62306.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:56:38Z"
    - latency: 6.636736ms
      message: 'load-balancer-api-internal: resolved host name a92acdfc50c74437987fd8ab85c2712d-5d866c8de5c62306.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T10:56:38Z"
    - latency: 4.880076ms
      message: 'load-balancer-api-internal: tcp connection to a92acdfc50c74437987fd8ab85c2712d-5d866c8de5c62306.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:55:38Z"
    - latency: 7.086648ms
      message: 'load-balancer-api-internal: resolved host name a92acdfc50c74437987fd8ab85c2712d-5d866c8de5c62306.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T10:55:38Z"
    - latency: 4.877476ms
      message: 'load-balancer-api-internal: tcp connection to a92acdfc50c74437987fd8ab85c2712d-5d866c8de5c62306.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:54:38Z"
    - latency: 8.402505ms
      message: 'load-balancer-api-internal: resolved host name a92acdfc50c74437987fd8ab85c2712d-5d866c8de5c62306.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T10:54:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T10:22:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-166-to-network-check-target-ip-10-0-128-166
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-166.ec2.internal
      uid: 82e8aedb-4d6f-4ad4-85f7-facf7ca21452
    resourceVersion: "55474"
    uid: dba42ff7-ae09-48eb-9e91-2d62ad228531
  spec:
    sourcePod: network-check-source-685456655f-nspbh
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T10:29:38Z"
      message: 'network-check-target-ip-10-0-128-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.043321ms
      message: 'network-check-target-ip-10-0-128-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:57:38Z"
    - latency: 880.649µs
      message: 'network-check-target-ip-10-0-128-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:56:38Z"
    - latency: 1.378335ms
      message: 'network-check-target-ip-10-0-128-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:55:38Z"
    - latency: 1.037511ms
      message: 'network-check-target-ip-10-0-128-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:54:38Z"
    - latency: 853.234µs
      message: 'network-check-target-ip-10-0-128-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:53:38Z"
    - latency: 1.035206ms
      message: 'network-check-target-ip-10-0-128-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:52:38Z"
    - latency: 1.510753ms
      message: 'network-check-target-ip-10-0-128-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:51:38Z"
    - latency: 1.42557ms
      message: 'network-check-target-ip-10-0-128-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:50:38Z"
    - latency: 1.153492ms
      message: 'network-check-target-ip-10-0-128-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:49:38Z"
    - latency: 1.010984ms
      message: 'network-check-target-ip-10-0-128-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:48:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T10:22:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-166-to-network-check-target-ip-10-0-141-95
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-166.ec2.internal
      uid: 82e8aedb-4d6f-4ad4-85f7-facf7ca21452
    resourceVersion: "55475"
    uid: 43c424a1-1f4d-4285-9da6-991b1d3191b7
  spec:
    sourcePod: network-check-source-685456655f-nspbh
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T10:29:38Z"
      message: 'network-check-target-ip-10-0-141-95: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.242867ms
      message: 'network-check-target-ip-10-0-141-95: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:57:38Z"
    - latency: 2.321709ms
      message: 'network-check-target-ip-10-0-141-95: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:56:38Z"
    - latency: 2.038402ms
      message: 'network-check-target-ip-10-0-141-95: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:55:38Z"
    - latency: 2.208587ms
      message: 'network-check-target-ip-10-0-141-95: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:54:38Z"
    - latency: 1.803863ms
      message: 'network-check-target-ip-10-0-141-95: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:53:38Z"
    - latency: 1.636947ms
      message: 'network-check-target-ip-10-0-141-95: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:52:38Z"
    - latency: 1.671622ms
      message: 'network-check-target-ip-10-0-141-95: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:51:38Z"
    - latency: 2.274145ms
      message: 'network-check-target-ip-10-0-141-95: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:50:38Z"
    - latency: 2.46167ms
      message: 'network-check-target-ip-10-0-141-95: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:49:38Z"
    - latency: 2.418037ms
      message: 'network-check-target-ip-10-0-141-95: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:48:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T10:22:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-166-to-network-check-target-ip-10-0-142-36
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-166.ec2.internal
      uid: 82e8aedb-4d6f-4ad4-85f7-facf7ca21452
    resourceVersion: "55476"
    uid: b64bee96-3ada-4552-9b86-df1eaafa7466
  spec:
    sourcePod: network-check-source-685456655f-nspbh
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T10:29:38Z"
      message: 'network-check-target-ip-10-0-142-36: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.407389ms
      message: 'network-check-target-ip-10-0-142-36: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:57:38Z"
    - latency: 2.697353ms
      message: 'network-check-target-ip-10-0-142-36: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:56:38Z"
    - latency: 2.245285ms
      message: 'network-check-target-ip-10-0-142-36: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:55:38Z"
    - latency: 2.341764ms
      message: 'network-check-target-ip-10-0-142-36: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:54:38Z"
    - latency: 2.222178ms
      message: 'network-check-target-ip-10-0-142-36: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:53:38Z"
    - latency: 2.546175ms
      message: 'network-check-target-ip-10-0-142-36: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:52:38Z"
    - latency: 2.345764ms
      message: 'network-check-target-ip-10-0-142-36: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:51:38Z"
    - latency: 2.34122ms
      message: 'network-check-target-ip-10-0-142-36: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:50:38Z"
    - latency: 2.549259ms
      message: 'network-check-target-ip-10-0-142-36: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:49:38Z"
    - latency: 2.626115ms
      message: 'network-check-target-ip-10-0-142-36: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:48:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T10:22:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-166-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-166.ec2.internal
      uid: 82e8aedb-4d6f-4ad4-85f7-facf7ca21452
    resourceVersion: "56362"
    uid: cd6cc9a3-3942-497c-b2ed-3ac3cde64e4b
  spec:
    sourcePod: network-check-source-685456655f-nspbh
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T10:28:38Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 943.818µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:58:38Z"
    - latency: 2.343924ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T10:58:38Z"
    - latency: 969.896µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:57:38Z"
    - latency: 1.87213ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T10:57:38Z"
    - latency: 1.239317ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:56:38Z"
    - latency: 2.154962ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T10:56:38Z"
    - latency: 1.110389ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:55:38Z"
    - latency: 2.134057ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T10:55:38Z"
    - latency: 961.569µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T10:54:38Z"
    - latency: 2.312137ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T10:54:38Z"
kind: List
metadata:
  resourceVersion: ""