apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T20:04:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-142-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-142.ec2.internal
      uid: 2997dea9-e952-4388-b3f5-743af92806b8
    resourceVersion: "30272"
    uid: 26404777-89e6-4d0e-a7c1-eacb1ab7ca29
  spec:
    sourcePod: network-check-source-6947749cfc-h5kxx
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T20:11:33Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 991.041µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:18:33Z"
    - latency: 1.205872ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:17:33Z"
    - latency: 1.465546ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:16:33Z"
    - latency: 933.198µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:15:33Z"
    - latency: 1.385279ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:14:33Z"
    - latency: 967.92µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:13:33Z"
    - latency: 1.38622ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:12:33Z"
    - latency: 1.132162ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:11:33Z"
    - latency: 1.428359ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:10:33Z"
    - latency: 1.176806ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:09:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T20:04:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-142-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-142.ec2.internal
      uid: 2997dea9-e952-4388-b3f5-743af92806b8
    resourceVersion: "28975"
    uid: 5b6735c6-c767-4a62-92cb-8809e373811c
  spec:
    sourcePod: network-check-source-6947749cfc-h5kxx
    targetEndpoint: ac75f655ba8c84f40b7e51365c560e97-b08c12dd26efb311.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T20:10:33Z"
      message: 'load-balancer-api-external: tcp connection to ac75f655ba8c84f40b7e51365c560e97-b08c12dd26efb311.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.816466ms
      message: 'load-balancer-api-external: tcp connection to ac75f655ba8c84f40b7e51365c560e97-b08c12dd26efb311.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:16:33Z"
    - latency: 7.2538ms
      message: 'load-balancer-api-external: resolved host name ac75f655ba8c84f40b7e51365c560e97-b08c12dd26efb311.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T20:16:33Z"
    - latency: 4.307182ms
      message: 'load-balancer-api-external: tcp connection to ac75f655ba8c84f40b7e51365c560e97-b08c12dd26efb311.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:15:33Z"
    - latency: 8.518645ms
      message: 'load-balancer-api-external: resolved host name ac75f655ba8c84f40b7e51365c560e97-b08c12dd26efb311.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T20:15:33Z"
    - latency: 4.681349ms
      message: 'load-balancer-api-external: tcp connection to ac75f655ba8c84f40b7e51365c560e97-b08c12dd26efb311.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:14:33Z"
    - latency: 12.215523ms
      message: 'load-balancer-api-external: resolved host name ac75f655ba8c84f40b7e51365c560e97-b08c12dd26efb311.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T20:14:33Z"
    - latency: 3.590098ms
      message: 'load-balancer-api-external: tcp connection to ac75f655ba8c84f40b7e51365c560e97-b08c12dd26efb311.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:13:33Z"
    - latency: 9.958515ms
      message: 'load-balancer-api-external: resolved host name ac75f655ba8c84f40b7e51365c560e97-b08c12dd26efb311.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T20:13:33Z"
    - latency: 4.787778ms
      message: 'load-balancer-api-external: tcp connection to ac75f655ba8c84f40b7e51365c560e97-b08c12dd26efb311.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:12:33Z"
    - latency: 8.666611ms
      message: 'load-balancer-api-external: resolved host name ac75f655ba8c84f40b7e51365c560e97-b08c12dd26efb311.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T20:12:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T20:04:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-142-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-142.ec2.internal
      uid: 2997dea9-e952-4388-b3f5-743af92806b8
    resourceVersion: "28976"
    uid: 52be6c6b-8e56-4023-9c86-c1b35bd74e0a
  spec:
    sourcePod: network-check-source-6947749cfc-h5kxx
    targetEndpoint: ac75f655ba8c84f40b7e51365c560e97-b08c12dd26efb311.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T20:10:33Z"
      message: 'load-balancer-api-internal: tcp connection to ac75f655ba8c84f40b7e51365c560e97-b08c12dd26efb311.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.68911ms
      message: 'load-balancer-api-internal: tcp connection to ac75f655ba8c84f40b7e51365c560e97-b08c12dd26efb311.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:16:33Z"
    - latency: 7.289062ms
      message: 'load-balancer-api-internal: resolved host name ac75f655ba8c84f40b7e51365c560e97-b08c12dd26efb311.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T20:16:33Z"
    - latency: 4.286053ms
      message: 'load-balancer-api-internal: tcp connection to ac75f655ba8c84f40b7e51365c560e97-b08c12dd26efb311.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:15:33Z"
    - latency: 8.466511ms
      message: 'load-balancer-api-internal: resolved host name ac75f655ba8c84f40b7e51365c560e97-b08c12dd26efb311.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T20:15:33Z"
    - latency: 4.697027ms
      message: 'load-balancer-api-internal: tcp connection to ac75f655ba8c84f40b7e51365c560e97-b08c12dd26efb311.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:14:33Z"
    - latency: 12.270695ms
      message: 'load-balancer-api-internal: resolved host name ac75f655ba8c84f40b7e51365c560e97-b08c12dd26efb311.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T20:14:33Z"
    - latency: 3.628634ms
      message: 'load-balancer-api-internal: tcp connection to ac75f655ba8c84f40b7e51365c560e97-b08c12dd26efb311.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:13:33Z"
    - latency: 9.854004ms
      message: 'load-balancer-api-internal: resolved host name ac75f655ba8c84f40b7e51365c560e97-b08c12dd26efb311.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T20:13:33Z"
    - latency: 4.770734ms
      message: 'load-balancer-api-internal: tcp connection to ac75f655ba8c84f40b7e51365c560e97-b08c12dd26efb311.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:12:33Z"
    - latency: 8.783938ms
      message: 'load-balancer-api-internal: resolved host name ac75f655ba8c84f40b7e51365c560e97-b08c12dd26efb311.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T20:12:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T20:04:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-142-to-network-check-target-ip-10-0-137-142
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-142.ec2.internal
      uid: 2997dea9-e952-4388-b3f5-743af92806b8
    resourceVersion: "30268"
    uid: d3c14d1b-d004-499b-8d45-b4773a32756a
  spec:
    sourcePod: network-check-source-6947749cfc-h5kxx
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T20:11:33Z"
      message: 'network-check-target-ip-10-0-137-142: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 936.39µs
      message: 'network-check-target-ip-10-0-137-142: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:18:33Z"
    - latency: 1.121206ms
      message: 'network-check-target-ip-10-0-137-142: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:17:33Z"
    - latency: 1.385959ms
      message: 'network-check-target-ip-10-0-137-142: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:16:33Z"
    - latency: 1.095712ms
      message: 'network-check-target-ip-10-0-137-142: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:15:33Z"
    - latency: 885.317µs
      message: 'network-check-target-ip-10-0-137-142: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:14:33Z"
    - latency: 986.754µs
      message: 'network-check-target-ip-10-0-137-142: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:13:33Z"
    - latency: 1.835163ms
      message: 'network-check-target-ip-10-0-137-142: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:12:33Z"
    - latency: 923.711µs
      message: 'network-check-target-ip-10-0-137-142: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:11:33Z"
    - latency: 1.12005ms
      message: 'network-check-target-ip-10-0-137-142: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:10:33Z"
    - latency: 1.018708ms
      message: 'network-check-target-ip-10-0-137-142: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:09:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T20:04:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-142-to-network-check-target-ip-10-0-138-226
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-142.ec2.internal
      uid: 2997dea9-e952-4388-b3f5-743af92806b8
    resourceVersion: "30269"
    uid: cb6ae1fb-ff96-498e-815e-bec4bae65b06
  spec:
    sourcePod: network-check-source-6947749cfc-h5kxx
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T20:11:33Z"
      message: 'network-check-target-ip-10-0-138-226: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.284337ms
      message: 'network-check-target-ip-10-0-138-226: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:18:33Z"
    - latency: 2.792246ms
      message: 'network-check-target-ip-10-0-138-226: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:17:33Z"
    - latency: 2.438968ms
      message: 'network-check-target-ip-10-0-138-226: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:16:33Z"
    - latency: 2.280517ms
      message: 'network-check-target-ip-10-0-138-226: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:15:33Z"
    - latency: 2.241181ms
      message: 'network-check-target-ip-10-0-138-226: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:14:33Z"
    - latency: 2.078077ms
      message: 'network-check-target-ip-10-0-138-226: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:13:33Z"
    - latency: 2.284154ms
      message: 'network-check-target-ip-10-0-138-226: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:12:33Z"
    - latency: 2.403562ms
      message: 'network-check-target-ip-10-0-138-226: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:11:33Z"
    - latency: 2.348387ms
      message: 'network-check-target-ip-10-0-138-226: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:10:33Z"
    - latency: 2.180015ms
      message: 'network-check-target-ip-10-0-138-226: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:09:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T20:04:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-142-to-network-check-target-ip-10-0-139-62
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-142.ec2.internal
      uid: 2997dea9-e952-4388-b3f5-743af92806b8
    resourceVersion: "30270"
    uid: c5d12e4b-f9cf-4ecb-b166-84d5007cb3ff
  spec:
    sourcePod: network-check-source-6947749cfc-h5kxx
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T20:11:33Z"
      message: 'network-check-target-ip-10-0-139-62: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.991771ms
      message: 'network-check-target-ip-10-0-139-62: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:18:33Z"
    - latency: 2.604029ms
      message: 'network-check-target-ip-10-0-139-62: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:17:33Z"
    - latency: 2.277156ms
      message: 'network-check-target-ip-10-0-139-62: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:16:33Z"
    - latency: 2.31937ms
      message: 'network-check-target-ip-10-0-139-62: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:15:33Z"
    - latency: 2.261725ms
      message: 'network-check-target-ip-10-0-139-62: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:14:33Z"
    - latency: 2.595812ms
      message: 'network-check-target-ip-10-0-139-62: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:13:33Z"
    - latency: 2.338205ms
      message: 'network-check-target-ip-10-0-139-62: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:12:33Z"
    - latency: 2.425912ms
      message: 'network-check-target-ip-10-0-139-62: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:11:33Z"
    - latency: 2.902763ms
      message: 'network-check-target-ip-10-0-139-62: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:10:33Z"
    - latency: 2.237645ms
      message: 'network-check-target-ip-10-0-139-62: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:09:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T20:04:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-142-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-142.ec2.internal
      uid: 2997dea9-e952-4388-b3f5-743af92806b8
    resourceVersion: "28973"
    uid: 03f6530a-1240-4d8e-8764-e4a79fb4dab0
  spec:
    sourcePod: network-check-source-6947749cfc-h5kxx
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T20:10:33Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.267907ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:16:33Z"
    - latency: 1.802705ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T20:16:33Z"
    - latency: 707.924µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:15:33Z"
    - latency: 1.920063ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T20:15:33Z"
    - latency: 863.876µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:14:33Z"
    - latency: 1.789225ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T20:14:33Z"
    - latency: 861.779µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:13:33Z"
    - latency: 1.646979ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T20:13:33Z"
    - latency: 1.090231ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T20:12:33Z"
    - latency: 1.829036ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T20:12:33Z"
kind: List
metadata:
  resourceVersion: ""