apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T12:59:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-84-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-84.ec2.internal
      uid: 2728903a-ca3d-4b92-9d57-79fd58bf3fbb
    resourceVersion: "67552"
    uid: 6122a342-35ac-4f44-a3ff-85cbba3cb2b3
  spec:
    sourcePod: network-check-source-6f78d59f99-vdwgx
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T13:06:57Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 903.06µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:41:57Z"
    - latency: 1.01092ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:40:57Z"
    - latency: 1.138763ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:39:57Z"
    - latency: 971.169µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:38:57Z"
    - latency: 829.9µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:37:57Z"
    - latency: 880.611µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:36:57Z"
    - latency: 984.593µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:35:57Z"
    - latency: 1.028567ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:34:57Z"
    - latency: 984.256µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:33:57Z"
    - latency: 1.131566ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:32:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T12:59:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-84-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-84.ec2.internal
      uid: 2728903a-ca3d-4b92-9d57-79fd58bf3fbb
    resourceVersion: "67553"
    uid: beecfb56-e723-42c5-89ea-6dc9f653e4b3
  spec:
    sourcePod: network-check-source-6f78d59f99-vdwgx
    targetEndpoint: ac176805975ef461cbd09ec166370f20-88d3f2fe6a47f598.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T13:05:57Z"
      message: 'load-balancer-api-external: tcp connection to ac176805975ef461cbd09ec166370f20-88d3f2fe6a47f598.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 16.817479ms
      message: 'load-balancer-api-external: tcp connection to ac176805975ef461cbd09ec166370f20-88d3f2fe6a47f598.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:41:57Z"
    - latency: 7.121638ms
      message: 'load-balancer-api-external: resolved host name ac176805975ef461cbd09ec166370f20-88d3f2fe6a47f598.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:41:57Z"
    - latency: 16.701836ms
      message: 'load-balancer-api-external: tcp connection to ac176805975ef461cbd09ec166370f20-88d3f2fe6a47f598.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:40:57Z"
    - latency: 7.943272ms
      message: 'load-balancer-api-external: resolved host name ac176805975ef461cbd09ec166370f20-88d3f2fe6a47f598.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:40:57Z"
    - latency: 23.365326ms
      message: 'load-balancer-api-external: tcp connection to ac176805975ef461cbd09ec166370f20-88d3f2fe6a47f598.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:39:57Z"
    - latency: 6.618224ms
      message: 'load-balancer-api-external: resolved host name ac176805975ef461cbd09ec166370f20-88d3f2fe6a47f598.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:39:57Z"
    - latency: 18.302235ms
      message: 'load-balancer-api-external: tcp connection to ac176805975ef461cbd09ec166370f20-88d3f2fe6a47f598.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:38:57Z"
    - latency: 6.410242ms
      message: 'load-balancer-api-external: resolved host name ac176805975ef461cbd09ec166370f20-88d3f2fe6a47f598.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:38:57Z"
    - latency: 21.140464ms
      message: 'load-balancer-api-external: tcp connection to ac176805975ef461cbd09ec166370f20-88d3f2fe6a47f598.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:37:57Z"
    - latency: 6.99777ms
      message: 'load-balancer-api-external: resolved host name ac176805975ef461cbd09ec166370f20-88d3f2fe6a47f598.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:37:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T12:59:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-84-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-84.ec2.internal
      uid: 2728903a-ca3d-4b92-9d57-79fd58bf3fbb
    resourceVersion: "67554"
    uid: 84d6052a-8b50-4c43-a0b9-25bc4c839dac
  spec:
    sourcePod: network-check-source-6f78d59f99-vdwgx
    targetEndpoint: ac176805975ef461cbd09ec166370f20-88d3f2fe6a47f598.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T13:05:57Z"
      message: 'load-balancer-api-internal: tcp connection to ac176805975ef461cbd09ec166370f20-88d3f2fe6a47f598.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 18.189129ms
      message: 'load-balancer-api-internal: tcp connection to ac176805975ef461cbd09ec166370f20-88d3f2fe6a47f598.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:41:57Z"
    - latency: 7.176198ms
      message: 'load-balancer-api-internal: resolved host name ac176805975ef461cbd09ec166370f20-88d3f2fe6a47f598.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:41:57Z"
    - latency: 24.084671ms
      message: 'load-balancer-api-internal: tcp connection to ac176805975ef461cbd09ec166370f20-88d3f2fe6a47f598.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:40:57Z"
    - latency: 7.961145ms
      message: 'load-balancer-api-internal: resolved host name ac176805975ef461cbd09ec166370f20-88d3f2fe6a47f598.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:40:57Z"
    - latency: 17.538261ms
      message: 'load-balancer-api-internal: tcp connection to ac176805975ef461cbd09ec166370f20-88d3f2fe6a47f598.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:39:57Z"
    - latency: 6.636103ms
      message: 'load-balancer-api-internal: resolved host name ac176805975ef461cbd09ec166370f20-88d3f2fe6a47f598.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:39:57Z"
    - latency: 17.536652ms
      message: 'load-balancer-api-internal: tcp connection to ac176805975ef461cbd09ec166370f20-88d3f2fe6a47f598.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:38:57Z"
    - latency: 6.441704ms
      message: 'load-balancer-api-internal: resolved host name ac176805975ef461cbd09ec166370f20-88d3f2fe6a47f598.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:38:57Z"
    - latency: 18.379909ms
      message: 'load-balancer-api-internal: tcp connection to ac176805975ef461cbd09ec166370f20-88d3f2fe6a47f598.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:37:57Z"
    - latency: 7.015898ms
      message: 'load-balancer-api-internal: resolved host name ac176805975ef461cbd09ec166370f20-88d3f2fe6a47f598.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:37:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T12:59:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-84-to-network-check-target-ip-10-0-130-180
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-84.ec2.internal
      uid: 2728903a-ca3d-4b92-9d57-79fd58bf3fbb
    resourceVersion: "67549"
    uid: e63b5a23-b181-4f32-94ca-c36627798568
  spec:
    sourcePod: network-check-source-6f78d59f99-vdwgx
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T13:06:57Z"
      message: 'network-check-target-ip-10-0-130-180: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.338116ms
      message: 'network-check-target-ip-10-0-130-180: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:41:57Z"
    - latency: 2.285097ms
      message: 'network-check-target-ip-10-0-130-180: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:40:57Z"
    - latency: 2.213545ms
      message: 'network-check-target-ip-10-0-130-180: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:39:57Z"
    - latency: 2.480695ms
      message: 'network-check-target-ip-10-0-130-180: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:38:57Z"
    - latency: 2.504887ms
      message: 'network-check-target-ip-10-0-130-180: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:37:57Z"
    - latency: 2.082208ms
      message: 'network-check-target-ip-10-0-130-180: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:36:57Z"
    - latency: 2.599966ms
      message: 'network-check-target-ip-10-0-130-180: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:35:57Z"
    - latency: 2.062205ms
      message: 'network-check-target-ip-10-0-130-180: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:34:57Z"
    - latency: 2.514974ms
      message: 'network-check-target-ip-10-0-130-180: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:33:57Z"
    - latency: 2.525259ms
      message: 'network-check-target-ip-10-0-130-180: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:32:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T12:59:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-84-to-network-check-target-ip-10-0-130-34
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-84.ec2.internal
      uid: 2728903a-ca3d-4b92-9d57-79fd58bf3fbb
    resourceVersion: "67547"
    uid: f7ecc00d-dc24-4c3d-a0f3-555a99a56a24
  spec:
    sourcePod: network-check-source-6f78d59f99-vdwgx
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T13:06:57Z"
      message: 'network-check-target-ip-10-0-130-34: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.938016ms
      message: 'network-check-target-ip-10-0-130-34: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:41:57Z"
    - latency: 1.757905ms
      message: 'network-check-target-ip-10-0-130-34: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:40:57Z"
    - latency: 2.347326ms
      message: 'network-check-target-ip-10-0-130-34: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:39:57Z"
    - latency: 2.415545ms
      message: 'network-check-target-ip-10-0-130-34: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:38:57Z"
    - latency: 1.945967ms
      message: 'network-check-target-ip-10-0-130-34: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:37:57Z"
    - latency: 2.208246ms
      message: 'network-check-target-ip-10-0-130-34: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:36:57Z"
    - latency: 2.023231ms
      message: 'network-check-target-ip-10-0-130-34: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:35:57Z"
    - latency: 2.254481ms
      message: 'network-check-target-ip-10-0-130-34: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:34:57Z"
    - latency: 2.255254ms
      message: 'network-check-target-ip-10-0-130-34: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:33:57Z"
    - latency: 2.431332ms
      message: 'network-check-target-ip-10-0-130-34: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:32:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T12:59:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-84-to-network-check-target-ip-10-0-142-84
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-84.ec2.internal
      uid: 2728903a-ca3d-4b92-9d57-79fd58bf3fbb
    resourceVersion: "67546"
    uid: 4e5db545-92ce-48d5-9a7a-f30a239a91a6
  spec:
    sourcePod: network-check-source-6f78d59f99-vdwgx
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T13:06:57Z"
      message: 'network-check-target-ip-10-0-142-84: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.506126ms
      message: 'network-check-target-ip-10-0-142-84: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:41:57Z"
    - latency: 1.474549ms
      message: 'network-check-target-ip-10-0-142-84: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:40:57Z"
    - latency: 997.963µs
      message: 'network-check-target-ip-10-0-142-84: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:39:57Z"
    - latency: 1.626239ms
      message: 'network-check-target-ip-10-0-142-84: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:38:57Z"
    - latency: 819.247µs
      message: 'network-check-target-ip-10-0-142-84: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:37:57Z"
    - latency: 989.531µs
      message: 'network-check-target-ip-10-0-142-84: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:36:57Z"
    - latency: 1.271516ms
      message: 'network-check-target-ip-10-0-142-84: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:35:57Z"
    - latency: 987.868µs
      message: 'network-check-target-ip-10-0-142-84: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:34:57Z"
    - latency: 1.107502ms
      message: 'network-check-target-ip-10-0-142-84: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:33:57Z"
    - latency: 1.776313ms
      message: 'network-check-target-ip-10-0-142-84: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:32:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T12:59:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-84-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-84.ec2.internal
      uid: 2728903a-ca3d-4b92-9d57-79fd58bf3fbb
    resourceVersion: "67550"
    uid: ba16bcf2-3e90-4919-be16-a648fc7f68e7
  spec:
    sourcePod: network-check-source-6f78d59f99-vdwgx
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T13:05:57Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 850.387µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:41:57Z"
    - latency: 2.089734ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:41:57Z"
    - latency: 975.408µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:40:57Z"
    - latency: 2.060267ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:40:57Z"
    - latency: 1.210715ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:39:57Z"
    - latency: 1.95228ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:39:57Z"
    - latency: 949.278µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:38:57Z"
    - latency: 1.986737ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:38:57Z"
    - latency: 754.58µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:37:57Z"
    - latency: 1.577563ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:37:57Z"
kind: List
metadata:
  resourceVersion: ""