apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T00:24:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-224-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-224.ec2.internal
      uid: 807f679c-af17-4cf3-9138-d5fc7713a4a1
    resourceVersion: "45221"
    uid: 7741634b-82ea-4c3a-9324-c9eca217b56a
  spec:
    sourcePod: network-check-source-dbd9cf844-98dbm
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T00:31:28Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 966.877µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:52:28Z"
    - latency: 1.079525ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:51:28Z"
    - latency: 1.02316ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:50:28Z"
    - latency: 809.367µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:49:28Z"
    - latency: 1.382103ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:48:28Z"
    - latency: 1.382769ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:47:28Z"
    - latency: 905.657µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:46:28Z"
    - latency: 942.946µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:45:28Z"
    - latency: 1.409041ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:44:28Z"
    - latency: 959.507µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:43:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T00:24:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-224-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-224.ec2.internal
      uid: 807f679c-af17-4cf3-9138-d5fc7713a4a1
    resourceVersion: "47244"
    uid: 97c9690e-a3e5-4544-8455-51bfa4fd5632
  spec:
    sourcePod: network-check-source-dbd9cf844-98dbm
    targetEndpoint: ad3c3274521eb4ee7a0961f309677616-2b18a84758f0a3e5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T00:30:28Z"
      message: 'load-balancer-api-external: tcp connection to ad3c3274521eb4ee7a0961f309677616-2b18a84758f0a3e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.43356ms
      message: 'load-balancer-api-external: tcp connection to ad3c3274521eb4ee7a0961f309677616-2b18a84758f0a3e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:54:28Z"
    - latency: 10.408192ms
      message: 'load-balancer-api-external: resolved host name ad3c3274521eb4ee7a0961f309677616-2b18a84758f0a3e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T00:54:28Z"
    - latency: 4.980937ms
      message: 'load-balancer-api-external: tcp connection to ad3c3274521eb4ee7a0961f309677616-2b18a84758f0a3e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:53:28Z"
    - latency: 9.47329ms
      message: 'load-balancer-api-external: resolved host name ad3c3274521eb4ee7a0961f309677616-2b18a84758f0a3e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T00:53:28Z"
    - latency: 3.578483ms
      message: 'load-balancer-api-external: tcp connection to ad3c3274521eb4ee7a0961f309677616-2b18a84758f0a3e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:52:28Z"
    - latency: 7.610356ms
      message: 'load-balancer-api-external: resolved host name ad3c3274521eb4ee7a0961f309677616-2b18a84758f0a3e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T00:52:28Z"
    - latency: 4.428136ms
      message: 'load-balancer-api-external: tcp connection to ad3c3274521eb4ee7a0961f309677616-2b18a84758f0a3e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:51:28Z"
    - latency: 8.923785ms
      message: 'load-balancer-api-external: resolved host name ad3c3274521eb4ee7a0961f309677616-2b18a84758f0a3e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T00:51:28Z"
    - latency: 4.987933ms
      message: 'load-balancer-api-external: tcp connection to ad3c3274521eb4ee7a0961f309677616-2b18a84758f0a3e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:50:28Z"
    - latency: 7.205511ms
      message: 'load-balancer-api-external: resolved host name ad3c3274521eb4ee7a0961f309677616-2b18a84758f0a3e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T00:50:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T00:24:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-224-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-224.ec2.internal
      uid: 807f679c-af17-4cf3-9138-d5fc7713a4a1
    resourceVersion: "47243"
    uid: 830d98c2-4f6d-4038-a4dc-4eb61c9f6be9
  spec:
    sourcePod: network-check-source-dbd9cf844-98dbm
    targetEndpoint: ad3c3274521eb4ee7a0961f309677616-2b18a84758f0a3e5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T00:30:28Z"
      message: 'load-balancer-api-internal: tcp connection to ad3c3274521eb4ee7a0961f309677616-2b18a84758f0a3e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.460197ms
      message: 'load-balancer-api-internal: tcp connection to ad3c3274521eb4ee7a0961f309677616-2b18a84758f0a3e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:54:28Z"
    - latency: 10.371727ms
      message: 'load-balancer-api-internal: resolved host name ad3c3274521eb4ee7a0961f309677616-2b18a84758f0a3e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T00:54:28Z"
    - latency: 4.907096ms
      message: 'load-balancer-api-internal: tcp connection to ad3c3274521eb4ee7a0961f309677616-2b18a84758f0a3e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:53:28Z"
    - latency: 9.524491ms
      message: 'load-balancer-api-internal: resolved host name ad3c3274521eb4ee7a0961f309677616-2b18a84758f0a3e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T00:53:28Z"
    - latency: 4.874849ms
      message: 'load-balancer-api-internal: tcp connection to ad3c3274521eb4ee7a0961f309677616-2b18a84758f0a3e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:52:28Z"
    - latency: 7.556696ms
      message: 'load-balancer-api-internal: resolved host name ad3c3274521eb4ee7a0961f309677616-2b18a84758f0a3e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T00:52:28Z"
    - latency: 4.419457ms
      message: 'load-balancer-api-internal: tcp connection to ad3c3274521eb4ee7a0961f309677616-2b18a84758f0a3e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:51:28Z"
    - latency: 8.883499ms
      message: 'load-balancer-api-internal: resolved host name ad3c3274521eb4ee7a0961f309677616-2b18a84758f0a3e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T00:51:28Z"
    - latency: 5.029622ms
      message: 'load-balancer-api-internal: tcp connection to ad3c3274521eb4ee7a0961f309677616-2b18a84758f0a3e5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:50:28Z"
    - latency: 7.147027ms
      message: 'load-balancer-api-internal: resolved host name ad3c3274521eb4ee7a0961f309677616-2b18a84758f0a3e5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T00:50:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T00:24:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-224-to-network-check-target-ip-10-0-128-241
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-224.ec2.internal
      uid: 807f679c-af17-4cf3-9138-d5fc7713a4a1
    resourceVersion: "45220"
    uid: bd26b980-d909-4cc5-b0e9-b710b65da6dc
  spec:
    sourcePod: network-check-source-dbd9cf844-98dbm
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T00:31:28Z"
      message: 'network-check-target-ip-10-0-128-241: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.169777ms
      message: 'network-check-target-ip-10-0-128-241: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:52:28Z"
    - latency: 2.269878ms
      message: 'network-check-target-ip-10-0-128-241: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:51:28Z"
    - latency: 2.072562ms
      message: 'network-check-target-ip-10-0-128-241: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:50:28Z"
    - latency: 1.873937ms
      message: 'network-check-target-ip-10-0-128-241: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:49:28Z"
    - latency: 2.065348ms
      message: 'network-check-target-ip-10-0-128-241: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:48:28Z"
    - latency: 2.105415ms
      message: 'network-check-target-ip-10-0-128-241: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:47:28Z"
    - latency: 2.042394ms
      message: 'network-check-target-ip-10-0-128-241: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:46:28Z"
    - latency: 1.837033ms
      message: 'network-check-target-ip-10-0-128-241: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:45:28Z"
    - latency: 1.849245ms
      message: 'network-check-target-ip-10-0-128-241: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:44:28Z"
    - latency: 2.069482ms
      message: 'network-check-target-ip-10-0-128-241: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:43:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T00:24:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-224-to-network-check-target-ip-10-0-140-224
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-224.ec2.internal
      uid: 807f679c-af17-4cf3-9138-d5fc7713a4a1
    resourceVersion: "45218"
    uid: f0d66ea2-24cf-4101-90a4-a0c10c4fe269
  spec:
    sourcePod: network-check-source-dbd9cf844-98dbm
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T00:31:28Z"
      message: 'network-check-target-ip-10-0-140-224: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.241929ms
      message: 'network-check-target-ip-10-0-140-224: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:52:28Z"
    - latency: 1.904058ms
      message: 'network-check-target-ip-10-0-140-224: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:51:28Z"
    - latency: 1.551448ms
      message: 'network-check-target-ip-10-0-140-224: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:50:28Z"
    - latency: 788.26µs
      message: 'network-check-target-ip-10-0-140-224: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:49:28Z"
    - latency: 1.712316ms
      message: 'network-check-target-ip-10-0-140-224: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:48:28Z"
    - latency: 961.076µs
      message: 'network-check-target-ip-10-0-140-224: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:47:28Z"
    - latency: 1.443957ms
      message: 'network-check-target-ip-10-0-140-224: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:46:28Z"
    - latency: 1.42843ms
      message: 'network-check-target-ip-10-0-140-224: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:45:28Z"
    - latency: 958.785µs
      message: 'network-check-target-ip-10-0-140-224: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:44:28Z"
    - latency: 1.589378ms
      message: 'network-check-target-ip-10-0-140-224: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:43:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T00:24:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-224-to-network-check-target-ip-10-0-143-64
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-224.ec2.internal
      uid: 807f679c-af17-4cf3-9138-d5fc7713a4a1
    resourceVersion: "45219"
    uid: c8155931-69e2-49ad-9b0c-47e3e72933c7
  spec:
    sourcePod: network-check-source-dbd9cf844-98dbm
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T00:31:28Z"
      message: 'network-check-target-ip-10-0-143-64: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.165408ms
      message: 'network-check-target-ip-10-0-143-64: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:52:28Z"
    - latency: 2.765694ms
      message: 'network-check-target-ip-10-0-143-64: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:51:28Z"
    - latency: 2.371942ms
      message: 'network-check-target-ip-10-0-143-64: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:50:28Z"
    - latency: 2.072671ms
      message: 'network-check-target-ip-10-0-143-64: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:49:28Z"
    - latency: 2.426506ms
      message: 'network-check-target-ip-10-0-143-64: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:48:28Z"
    - latency: 2.535533ms
      message: 'network-check-target-ip-10-0-143-64: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:47:28Z"
    - latency: 2.60852ms
      message: 'network-check-target-ip-10-0-143-64: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:46:28Z"
    - latency: 2.323698ms
      message: 'network-check-target-ip-10-0-143-64: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:45:28Z"
    - latency: 2.141168ms
      message: 'network-check-target-ip-10-0-143-64: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:44:28Z"
    - latency: 1.947493ms
      message: 'network-check-target-ip-10-0-143-64: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:43:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T00:24:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-224-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-224.ec2.internal
      uid: 807f679c-af17-4cf3-9138-d5fc7713a4a1
    resourceVersion: "47242"
    uid: cf4ff7e1-0281-4eeb-b028-7d9c24d0ce92
  spec:
    sourcePod: network-check-source-dbd9cf844-98dbm
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T00:30:28Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 806.902µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:54:28Z"
    - latency: 2.339302ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T00:54:28Z"
    - latency: 1.455605ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:53:28Z"
    - latency: 2.154217ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T00:53:28Z"
    - latency: 990.919µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:52:28Z"
    - latency: 2.326049ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T00:52:28Z"
    - latency: 1.132839ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:51:28Z"
    - latency: 2.199082ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T00:51:28Z"
    - latency: 1.288846ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T00:50:28Z"
    - latency: 1.714299ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T00:50:28Z"
kind: List
metadata:
  resourceVersion: ""