apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T16:15:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-148-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-148.ec2.internal
      uid: 81a26236-83ba-4a86-9d63-7b186e1dd308
    resourceVersion: "54258"
    uid: a6016960-8854-4de1-a0bf-a99dd54ea3e0
  spec:
    sourcePod: network-check-source-685456655f-jpjpt
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T16:22:19Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.807642ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:43:19Z"
    - latency: 1.171662ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:42:19Z"
    - latency: 1.264359ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:41:19Z"
    - latency: 1.233849ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:40:19Z"
    - latency: 1.16514ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:39:19Z"
    - latency: 1.097839ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:38:19Z"
    - latency: 1.229619ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:37:19Z"
    - latency: 936.349µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:36:19Z"
    - latency: 1.558189ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:35:19Z"
    - latency: 1.194533ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:34:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T16:15:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-148-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-148.ec2.internal
      uid: 81a26236-83ba-4a86-9d63-7b186e1dd308
    resourceVersion: "55826"
    uid: 4dcf0cee-2927-48ae-bfa5-7f490095268a
  spec:
    sourcePod: network-check-source-685456655f-jpjpt
    targetEndpoint: ac7c67d58fb74432ba217727e8a5b3a5-35b01046218dccf8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T16:21:19Z"
      message: 'load-balancer-api-external: tcp connection to ac7c67d58fb74432ba217727e8a5b3a5-35b01046218dccf8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.777753ms
      message: 'load-balancer-api-external: tcp connection to ac7c67d58fb74432ba217727e8a5b3a5-35b01046218dccf8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:45:19Z"
    - latency: 7.879578ms
      message: 'load-balancer-api-external: resolved host name ac7c67d58fb74432ba217727e8a5b3a5-35b01046218dccf8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T16:45:19Z"
    - latency: 5.194556ms
      message: 'load-balancer-api-external: tcp connection to ac7c67d58fb74432ba217727e8a5b3a5-35b01046218dccf8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:44:19Z"
    - latency: 6.747089ms
      message: 'load-balancer-api-external: resolved host name ac7c67d58fb74432ba217727e8a5b3a5-35b01046218dccf8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T16:44:19Z"
    - latency: 4.245565ms
      message: 'load-balancer-api-external: tcp connection to ac7c67d58fb74432ba217727e8a5b3a5-35b01046218dccf8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:43:19Z"
    - latency: 7.569813ms
      message: 'load-balancer-api-external: resolved host name ac7c67d58fb74432ba217727e8a5b3a5-35b01046218dccf8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T16:43:19Z"
    - latency: 4.911737ms
      message: 'load-balancer-api-external: tcp connection to ac7c67d58fb74432ba217727e8a5b3a5-35b01046218dccf8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:42:19Z"
    - latency: 6.401276ms
      message: 'load-balancer-api-external: resolved host name ac7c67d58fb74432ba217727e8a5b3a5-35b01046218dccf8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T16:42:19Z"
    - latency: 3.577731ms
      message: 'load-balancer-api-external: tcp connection to ac7c67d58fb74432ba217727e8a5b3a5-35b01046218dccf8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:41:19Z"
    - latency: 8.979914ms
      message: 'load-balancer-api-external: resolved host name ac7c67d58fb74432ba217727e8a5b3a5-35b01046218dccf8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T16:41:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T16:15:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-148-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-148.ec2.internal
      uid: 81a26236-83ba-4a86-9d63-7b186e1dd308
    resourceVersion: "55827"
    uid: 1004683b-a9f6-4740-97d8-84a74b20ae31
  spec:
    sourcePod: network-check-source-685456655f-jpjpt
    targetEndpoint: ac7c67d58fb74432ba217727e8a5b3a5-35b01046218dccf8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T16:21:19Z"
      message: 'load-balancer-api-internal: tcp connection to ac7c67d58fb74432ba217727e8a5b3a5-35b01046218dccf8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.147949ms
      message: 'load-balancer-api-internal: tcp connection to ac7c67d58fb74432ba217727e8a5b3a5-35b01046218dccf8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:45:19Z"
    - latency: 7.817242ms
      message: 'load-balancer-api-internal: resolved host name ac7c67d58fb74432ba217727e8a5b3a5-35b01046218dccf8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T16:45:19Z"
    - latency: 5.153893ms
      message: 'load-balancer-api-internal: tcp connection to ac7c67d58fb74432ba217727e8a5b3a5-35b01046218dccf8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:44:19Z"
    - latency: 6.767547ms
      message: 'load-balancer-api-internal: resolved host name ac7c67d58fb74432ba217727e8a5b3a5-35b01046218dccf8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T16:44:19Z"
    - latency: 4.271648ms
      message: 'load-balancer-api-internal: tcp connection to ac7c67d58fb74432ba217727e8a5b3a5-35b01046218dccf8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:43:19Z"
    - latency: 7.495273ms
      message: 'load-balancer-api-internal: resolved host name ac7c67d58fb74432ba217727e8a5b3a5-35b01046218dccf8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T16:43:19Z"
    - latency: 4.953974ms
      message: 'load-balancer-api-internal: tcp connection to ac7c67d58fb74432ba217727e8a5b3a5-35b01046218dccf8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:42:19Z"
    - latency: 6.380653ms
      message: 'load-balancer-api-internal: resolved host name ac7c67d58fb74432ba217727e8a5b3a5-35b01046218dccf8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T16:42:19Z"
    - latency: 4.519973ms
      message: 'load-balancer-api-internal: tcp connection to ac7c67d58fb74432ba217727e8a5b3a5-35b01046218dccf8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:41:19Z"
    - latency: 9.005681ms
      message: 'load-balancer-api-internal: resolved host name ac7c67d58fb74432ba217727e8a5b3a5-35b01046218dccf8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T16:41:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T16:15:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-148-to-network-check-target-ip-10-0-128-81
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-148.ec2.internal
      uid: 81a26236-83ba-4a86-9d63-7b186e1dd308
    resourceVersion: "54256"
    uid: 308a1275-0077-415e-a895-4ecb9d3bc01b
  spec:
    sourcePod: network-check-source-685456655f-jpjpt
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T16:22:19Z"
      message: 'network-check-target-ip-10-0-128-81: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.841947ms
      message: 'network-check-target-ip-10-0-128-81: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:43:19Z"
    - latency: 2.215644ms
      message: 'network-check-target-ip-10-0-128-81: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:42:19Z"
    - latency: 2.119364ms
      message: 'network-check-target-ip-10-0-128-81: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:41:19Z"
    - latency: 2.141671ms
      message: 'network-check-target-ip-10-0-128-81: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:40:19Z"
    - latency: 2.694351ms
      message: 'network-check-target-ip-10-0-128-81: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:39:19Z"
    - latency: 2.450478ms
      message: 'network-check-target-ip-10-0-128-81: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:38:19Z"
    - latency: 2.474244ms
      message: 'network-check-target-ip-10-0-128-81: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:37:19Z"
    - latency: 2.409989ms
      message: 'network-check-target-ip-10-0-128-81: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:36:19Z"
    - latency: 2.48568ms
      message: 'network-check-target-ip-10-0-128-81: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:35:19Z"
    - latency: 2.511105ms
      message: 'network-check-target-ip-10-0-128-81: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:34:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T16:15:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-148-to-network-check-target-ip-10-0-137-117
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-148.ec2.internal
      uid: 81a26236-83ba-4a86-9d63-7b186e1dd308
    resourceVersion: "54257"
    uid: 5b3add0b-dcf0-46c2-a075-cf7ed103ee24
  spec:
    sourcePod: network-check-source-685456655f-jpjpt
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T16:22:19Z"
      message: 'network-check-target-ip-10-0-137-117: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.372688ms
      message: 'network-check-target-ip-10-0-137-117: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:43:19Z"
    - latency: 2.416204ms
      message: 'network-check-target-ip-10-0-137-117: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:42:19Z"
    - latency: 2.396663ms
      message: 'network-check-target-ip-10-0-137-117: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:41:19Z"
    - latency: 2.44032ms
      message: 'network-check-target-ip-10-0-137-117: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:40:19Z"
    - latency: 2.503957ms
      message: 'network-check-target-ip-10-0-137-117: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:39:19Z"
    - latency: 2.095071ms
      message: 'network-check-target-ip-10-0-137-117: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:38:19Z"
    - latency: 2.472105ms
      message: 'network-check-target-ip-10-0-137-117: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:37:19Z"
    - latency: 2.454504ms
      message: 'network-check-target-ip-10-0-137-117: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:36:19Z"
    - latency: 2.571024ms
      message: 'network-check-target-ip-10-0-137-117: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:35:19Z"
    - latency: 2.315567ms
      message: 'network-check-target-ip-10-0-137-117: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:34:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T16:15:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-148-to-network-check-target-ip-10-0-137-148
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-148.ec2.internal
      uid: 81a26236-83ba-4a86-9d63-7b186e1dd308
    resourceVersion: "54255"
    uid: bf0dc186-78f6-434e-97d8-618f7bcde223
  spec:
    sourcePod: network-check-source-685456655f-jpjpt
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T16:22:19Z"
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 856.366µs
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:43:19Z"
    - latency: 1.009894ms
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:42:19Z"
    - latency: 1.26473ms
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:41:19Z"
    - latency: 1.207558ms
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:40:19Z"
    - latency: 875.717µs
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:39:19Z"
    - latency: 1.139694ms
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:38:19Z"
    - latency: 995.313µs
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:37:19Z"
    - latency: 1.214418ms
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:36:19Z"
    - latency: 1.607737ms
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:35:19Z"
    - latency: 1.676855ms
      message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:34:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T16:15:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-148-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-148.ec2.internal
      uid: 81a26236-83ba-4a86-9d63-7b186e1dd308
    resourceVersion: "55824"
    uid: 674c6238-f418-4284-917f-3a5f1fba5857
  spec:
    sourcePod: network-check-source-685456655f-jpjpt
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T16:21:19Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 905.147µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:45:19Z"
    - latency: 2.65212ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T16:45:19Z"
    - latency: 836.46µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:44:19Z"
    - latency: 2.172821ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T16:44:19Z"
    - latency: 881.935µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:43:19Z"
    - latency: 2.416968ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T16:43:19Z"
    - latency: 760.727µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:42:19Z"
    - latency: 1.790856ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T16:42:19Z"
    - latency: 1.450378ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T16:41:19Z"
    - latency: 1.735442ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T16:41:19Z"
kind: List
metadata:
  resourceVersion: ""