apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T11:18:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-40-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-40.ec2.internal
      uid: 9e1ae5a0-0f34-48b1-af07-e392d7b07c1f
    resourceVersion: "47645"
    uid: f2ec3196-e6cd-468a-8b9e-178589dd3b99
  spec:
    sourcePod: network-check-source-685456655f-c8rl2
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T11:25:01Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.254963ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:46:01Z"
    - latency: 1.151718ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:45:01Z"
    - latency: 1.041553ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:44:01Z"
    - latency: 1.14657ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:43:01Z"
    - latency: 1.036292ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:42:01Z"
    - latency: 2.066905ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:41:01Z"
    - latency: 4.303005ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:40:01Z"
    - latency: 1.111884ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:39:01Z"
    - latency: 1.118843ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:38:01Z"
    - latency: 1.007112ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:37:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T11:18:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-40-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-40.ec2.internal
      uid: 9e1ae5a0-0f34-48b1-af07-e392d7b07c1f
    resourceVersion: "49191"
    uid: baa03da6-3b2e-4309-812e-a7effff0d135
  spec:
    sourcePod: network-check-source-685456655f-c8rl2
    targetEndpoint: a56ad1af8943b469bbacde5815b8c922-a1381255694ed31a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T11:24:01Z"
      message: 'load-balancer-api-external: tcp connection to a56ad1af8943b469bbacde5815b8c922-a1381255694ed31a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.689543ms
      message: 'load-balancer-api-external: tcp connection to a56ad1af8943b469bbacde5815b8c922-a1381255694ed31a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:48:01Z"
    - latency: 6.462339ms
      message: 'load-balancer-api-external: resolved host name a56ad1af8943b469bbacde5815b8c922-a1381255694ed31a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T11:48:01Z"
    - latency: 5.275538ms
      message: 'load-balancer-api-external: tcp connection to a56ad1af8943b469bbacde5815b8c922-a1381255694ed31a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:47:01Z"
    - latency: 7.142139ms
      message: 'load-balancer-api-external: resolved host name a56ad1af8943b469bbacde5815b8c922-a1381255694ed31a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T11:47:01Z"
    - latency: 2.896937ms
      message: 'load-balancer-api-external: tcp connection to a56ad1af8943b469bbacde5815b8c922-a1381255694ed31a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:46:01Z"
    - latency: 7.32567ms
      message: 'load-balancer-api-external: resolved host name a56ad1af8943b469bbacde5815b8c922-a1381255694ed31a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T11:46:01Z"
    - latency: 3.420639ms
      message: 'load-balancer-api-external: tcp connection to a56ad1af8943b469bbacde5815b8c922-a1381255694ed31a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:45:01Z"
    - latency: 6.64755ms
      message: 'load-balancer-api-external: resolved host name a56ad1af8943b469bbacde5815b8c922-a1381255694ed31a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T11:45:01Z"
    - latency: 4.756819ms
      message: 'load-balancer-api-external: tcp connection to a56ad1af8943b469bbacde5815b8c922-a1381255694ed31a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:44:01Z"
    - latency: 8.031716ms
      message: 'load-balancer-api-external: resolved host name a56ad1af8943b469bbacde5815b8c922-a1381255694ed31a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T11:44:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T11:18:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-40-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-40.ec2.internal
      uid: 9e1ae5a0-0f34-48b1-af07-e392d7b07c1f
    resourceVersion: "49192"
    uid: 59c5f6d2-15b5-47aa-a1b5-b9bcfe1f27b9
  spec:
    sourcePod: network-check-source-685456655f-c8rl2
    targetEndpoint: a56ad1af8943b469bbacde5815b8c922-a1381255694ed31a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T11:24:01Z"
      message: 'load-balancer-api-internal: tcp connection to a56ad1af8943b469bbacde5815b8c922-a1381255694ed31a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.451136ms
      message: 'load-balancer-api-internal: tcp connection to a56ad1af8943b469bbacde5815b8c922-a1381255694ed31a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:48:01Z"
    - latency: 6.309993ms
      message: 'load-balancer-api-internal: resolved host name a56ad1af8943b469bbacde5815b8c922-a1381255694ed31a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T11:48:01Z"
    - latency: 5.312403ms
      message: 'load-balancer-api-internal: tcp connection to a56ad1af8943b469bbacde5815b8c922-a1381255694ed31a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:47:01Z"
    - latency: 7.107018ms
      message: 'load-balancer-api-internal: resolved host name a56ad1af8943b469bbacde5815b8c922-a1381255694ed31a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T11:47:01Z"
    - latency: 2.889781ms
      message: 'load-balancer-api-internal: tcp connection to a56ad1af8943b469bbacde5815b8c922-a1381255694ed31a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:46:01Z"
    - latency: 7.370102ms
      message: 'load-balancer-api-internal: resolved host name a56ad1af8943b469bbacde5815b8c922-a1381255694ed31a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T11:46:01Z"
    - latency: 3.423425ms
      message: 'load-balancer-api-internal: tcp connection to a56ad1af8943b469bbacde5815b8c922-a1381255694ed31a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:45:01Z"
    - latency: 6.703287ms
      message: 'load-balancer-api-internal: resolved host name a56ad1af8943b469bbacde5815b8c922-a1381255694ed31a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T11:45:01Z"
    - latency: 4.785239ms
      message: 'load-balancer-api-internal: tcp connection to a56ad1af8943b469bbacde5815b8c922-a1381255694ed31a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:44:01Z"
    - latency: 8.100836ms
      message: 'load-balancer-api-internal: resolved host name a56ad1af8943b469bbacde5815b8c922-a1381255694ed31a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T11:44:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T11:18:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-40-to-network-check-target-ip-10-0-128-153
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-40.ec2.internal
      uid: 9e1ae5a0-0f34-48b1-af07-e392d7b07c1f
    resourceVersion: "47643"
    uid: 0670cd82-95c3-4ea3-ba9e-16708f5dda83
  spec:
    sourcePod: network-check-source-685456655f-c8rl2
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T11:25:01Z"
      message: 'network-check-target-ip-10-0-128-153: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.034782ms
      message: 'network-check-target-ip-10-0-128-153: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:46:01Z"
    - latency: 2.328907ms
      message: 'network-check-target-ip-10-0-128-153: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:45:01Z"
    - latency: 1.824636ms
      message: 'network-check-target-ip-10-0-128-153: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:44:01Z"
    - latency: 2.254391ms
      message: 'network-check-target-ip-10-0-128-153: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:43:01Z"
    - latency: 2.530686ms
      message: 'network-check-target-ip-10-0-128-153: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:42:01Z"
    - latency: 3.218486ms
      message: 'network-check-target-ip-10-0-128-153: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:41:01Z"
    - latency: 5.204565ms
      message: 'network-check-target-ip-10-0-128-153: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:40:01Z"
    - latency: 2.314669ms
      message: 'network-check-target-ip-10-0-128-153: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:39:01Z"
    - latency: 2.354904ms
      message: 'network-check-target-ip-10-0-128-153: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:38:01Z"
    - latency: 2.722309ms
      message: 'network-check-target-ip-10-0-128-153: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:37:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T11:18:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-40-to-network-check-target-ip-10-0-132-86
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-40.ec2.internal
      uid: 9e1ae5a0-0f34-48b1-af07-e392d7b07c1f
    resourceVersion: "47644"
    uid: 735251d0-ea11-4fdc-ba74-7ad14fec7bae
  spec:
    sourcePod: network-check-source-685456655f-c8rl2
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T11:25:01Z"
      message: 'network-check-target-ip-10-0-132-86: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.001348ms
      message: 'network-check-target-ip-10-0-132-86: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:46:01Z"
    - latency: 1.994814ms
      message: 'network-check-target-ip-10-0-132-86: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:45:01Z"
    - latency: 2.002742ms
      message: 'network-check-target-ip-10-0-132-86: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:44:01Z"
    - latency: 2.143636ms
      message: 'network-check-target-ip-10-0-132-86: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:43:01Z"
    - latency: 2.120406ms
      message: 'network-check-target-ip-10-0-132-86: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:42:01Z"
    - latency: 2.791124ms
      message: 'network-check-target-ip-10-0-132-86: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:41:01Z"
    - latency: 4.603938ms
      message: 'network-check-target-ip-10-0-132-86: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:40:01Z"
    - latency: 2.145589ms
      message: 'network-check-target-ip-10-0-132-86: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:39:01Z"
    - latency: 2.014228ms
      message: 'network-check-target-ip-10-0-132-86: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:38:01Z"
    - latency: 2.657673ms
      message: 'network-check-target-ip-10-0-132-86: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:37:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T11:18:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-40-to-network-check-target-ip-10-0-141-40
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-40.ec2.internal
      uid: 9e1ae5a0-0f34-48b1-af07-e392d7b07c1f
    resourceVersion: "47642"
    uid: dcb76e37-e80a-4068-915c-f06b9feae201
  spec:
    sourcePod: network-check-source-685456655f-c8rl2
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T11:25:01Z"
      message: 'network-check-target-ip-10-0-141-40: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 863.493µs
      message: 'network-check-target-ip-10-0-141-40: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:46:01Z"
    - latency: 1.227502ms
      message: 'network-check-target-ip-10-0-141-40: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:45:01Z"
    - latency: 960.052µs
      message: 'network-check-target-ip-10-0-141-40: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:44:01Z"
    - latency: 1.304332ms
      message: 'network-check-target-ip-10-0-141-40: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:43:01Z"
    - latency: 1.387408ms
      message: 'network-check-target-ip-10-0-141-40: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:42:01Z"
    - latency: 4.200033ms
      message: 'network-check-target-ip-10-0-141-40: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:41:01Z"
    - latency: 4.860231ms
      message: 'network-check-target-ip-10-0-141-40: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:40:01Z"
    - latency: 1.092108ms
      message: 'network-check-target-ip-10-0-141-40: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:39:01Z"
    - latency: 943.1µs
      message: 'network-check-target-ip-10-0-141-40: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:38:01Z"
    - latency: 2.235169ms
      message: 'network-check-target-ip-10-0-141-40: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:37:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T11:18:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-40-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-40.ec2.internal
      uid: 9e1ae5a0-0f34-48b1-af07-e392d7b07c1f
    resourceVersion: "49190"
    uid: 180e21d6-6741-4792-ab6d-4361ee7ae1a0
  spec:
    sourcePod: network-check-source-685456655f-c8rl2
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T11:24:01Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 786.128µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:48:01Z"
    - latency: 2.149657ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T11:48:01Z"
    - latency: 1.108489ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:47:01Z"
    - latency: 1.895847ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T11:47:01Z"
    - latency: 968.383µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:46:01Z"
    - latency: 1.984173ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T11:46:01Z"
    - latency: 1.05411ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:45:01Z"
    - latency: 1.768165ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T11:45:01Z"
    - latency: 883.442µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:44:01Z"
    - latency: 2.057416ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T11:44:01Z"
kind: List
metadata:
  resourceVersion: ""