apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T05:57:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-31-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-31.ec2.internal
      uid: b802feb0-55df-4cf2-bd12-9159e5f48a40
    resourceVersion: "157240"
    uid: c9baae65-ccc0-49f3-9e1e-cdba8d38527c
  spec:
    sourcePod: network-check-source-6f78d59f99-7jsft
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T06:04:32Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.600599ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:00:30Z"
    - latency: 1.058248ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:59:30Z"
    - latency: 1.367677ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:58:30Z"
    - latency: 981.092µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:57:30Z"
    - latency: 1.568083ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:56:30Z"
    - latency: 1.458433ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:55:30Z"
    - latency: 1.565411ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:54:30Z"
    - latency: 14.245309ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:53:30Z"
    - latency: 1.515619ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:52:30Z"
    - latency: 5.633925ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:51:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T05:57:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-31-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-31.ec2.internal
      uid: b802feb0-55df-4cf2-bd12-9159e5f48a40
    resourceVersion: "148498"
    uid: 36880ba3-9b7c-4ae6-bb8f-0b4e4242ee35
  spec:
    sourcePod: network-check-source-6f78d59f99-7jsft
    targetEndpoint: a17c8a4b539814f7d866a3f7f93832ea-84532d42246569fd.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T06:03:30Z"
      message: 'load-balancer-api-external: tcp connection to a17c8a4b539814f7d866a3f7f93832ea-84532d42246569fd.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 18.870506ms
      message: 'load-balancer-api-external: tcp connection to a17c8a4b539814f7d866a3f7f93832ea-84532d42246569fd.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:57:30Z"
    - latency: 10.260301ms
      message: 'load-balancer-api-external: resolved host name a17c8a4b539814f7d866a3f7f93832ea-84532d42246569fd.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:57:30Z"
    - latency: 15.424754ms
      message: 'load-balancer-api-external: tcp connection to a17c8a4b539814f7d866a3f7f93832ea-84532d42246569fd.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:56:30Z"
    - latency: 6.776646ms
      message: 'load-balancer-api-external: resolved host name a17c8a4b539814f7d866a3f7f93832ea-84532d42246569fd.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:56:30Z"
    - latency: 16.326993ms
      message: 'load-balancer-api-external: tcp connection to a17c8a4b539814f7d866a3f7f93832ea-84532d42246569fd.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:55:30Z"
    - latency: 13.636456ms
      message: 'load-balancer-api-external: resolved host name a17c8a4b539814f7d866a3f7f93832ea-84532d42246569fd.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:55:30Z"
    - latency: 15.342684ms
      message: 'load-balancer-api-external: tcp connection to a17c8a4b539814f7d866a3f7f93832ea-84532d42246569fd.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:54:30Z"
    - latency: 7.079119ms
      message: 'load-balancer-api-external: resolved host name a17c8a4b539814f7d866a3f7f93832ea-84532d42246569fd.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:54:30Z"
    - latency: 43.162502ms
      message: 'load-balancer-api-external: tcp connection to a17c8a4b539814f7d866a3f7f93832ea-84532d42246569fd.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:53:30Z"
    - latency: 73.713669ms
      message: 'load-balancer-api-external: resolved host name a17c8a4b539814f7d866a3f7f93832ea-84532d42246569fd.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:53:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T05:57:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-31-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-31.ec2.internal
      uid: b802feb0-55df-4cf2-bd12-9159e5f48a40
    resourceVersion: "148497"
    uid: f65698f2-4970-4e66-9ccd-f28368706542
  spec:
    sourcePod: network-check-source-6f78d59f99-7jsft
    targetEndpoint: a17c8a4b539814f7d866a3f7f93832ea-84532d42246569fd.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T06:03:30Z"
      message: 'load-balancer-api-internal: tcp connection to a17c8a4b539814f7d866a3f7f93832ea-84532d42246569fd.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 19.326793ms
      message: 'load-balancer-api-internal: tcp connection to a17c8a4b539814f7d866a3f7f93832ea-84532d42246569fd.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:57:30Z"
    - latency: 10.290066ms
      message: 'load-balancer-api-internal: resolved host name a17c8a4b539814f7d866a3f7f93832ea-84532d42246569fd.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:57:30Z"
    - latency: 16.044276ms
      message: 'load-balancer-api-internal: tcp connection to a17c8a4b539814f7d866a3f7f93832ea-84532d42246569fd.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:56:30Z"
    - latency: 6.666108ms
      message: 'load-balancer-api-internal: resolved host name a17c8a4b539814f7d866a3f7f93832ea-84532d42246569fd.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:56:30Z"
    - latency: 16.3983ms
      message: 'load-balancer-api-internal: tcp connection to a17c8a4b539814f7d866a3f7f93832ea-84532d42246569fd.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:55:30Z"
    - latency: 13.733142ms
      message: 'load-balancer-api-internal: resolved host name a17c8a4b539814f7d866a3f7f93832ea-84532d42246569fd.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:55:30Z"
    - latency: 15.804615ms
      message: 'load-balancer-api-internal: tcp connection to a17c8a4b539814f7d866a3f7f93832ea-84532d42246569fd.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:54:30Z"
    - latency: 6.922124ms
      message: 'load-balancer-api-internal: resolved host name a17c8a4b539814f7d866a3f7f93832ea-84532d42246569fd.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:54:30Z"
    - latency: 55.541407ms
      message: 'load-balancer-api-internal: tcp connection to a17c8a4b539814f7d866a3f7f93832ea-84532d42246569fd.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:53:30Z"
    - latency: 72.999755ms
      message: 'load-balancer-api-internal: resolved host name a17c8a4b539814f7d866a3f7f93832ea-84532d42246569fd.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:53:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T05:57:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-31-to-network-check-target-ip-10-0-128-31
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-31.ec2.internal
      uid: b802feb0-55df-4cf2-bd12-9159e5f48a40
    resourceVersion: "157236"
    uid: 9efd79e7-a233-4a7c-87ff-c0e08916d209
  spec:
    sourcePod: network-check-source-6f78d59f99-7jsft
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T06:04:30Z"
      message: 'network-check-target-ip-10-0-128-31: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.175605ms
      message: 'network-check-target-ip-10-0-128-31: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:00:30Z"
    - latency: 1.731018ms
      message: 'network-check-target-ip-10-0-128-31: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:59:30Z"
    - latency: 1.051756ms
      message: 'network-check-target-ip-10-0-128-31: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:58:30Z"
    - latency: 1.168574ms
      message: 'network-check-target-ip-10-0-128-31: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:57:30Z"
    - latency: 1.256116ms
      message: 'network-check-target-ip-10-0-128-31: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:56:30Z"
    - latency: 1.699668ms
      message: 'network-check-target-ip-10-0-128-31: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:55:30Z"
    - latency: 1.897645ms
      message: 'network-check-target-ip-10-0-128-31: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:54:30Z"
    - latency: 14.654965ms
      message: 'network-check-target-ip-10-0-128-31: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:53:30Z"
    - latency: 2.284973ms
      message: 'network-check-target-ip-10-0-128-31: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:52:30Z"
    - latency: 15.689909ms
      message: 'network-check-target-ip-10-0-128-31: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:51:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T05:57:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-31-to-network-check-target-ip-10-0-131-226
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-31.ec2.internal
      uid: b802feb0-55df-4cf2-bd12-9159e5f48a40
    resourceVersion: "157239"
    uid: ec51424a-bb9e-412e-9081-55564d0a64b2
  spec:
    sourcePod: network-check-source-6f78d59f99-7jsft
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T06:04:30Z"
      message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.656766ms
      message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:00:30Z"
    - latency: 2.232316ms
      message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:59:30Z"
    - latency: 2.431097ms
      message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:58:30Z"
    - latency: 2.481374ms
      message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:57:30Z"
    - latency: 2.874469ms
      message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:56:30Z"
    - latency: 2.897351ms
      message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:55:30Z"
    - latency: 3.060395ms
      message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:54:30Z"
    - latency: 19.0372ms
      message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:53:30Z"
    - latency: 3.404338ms
      message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:52:30Z"
    - latency: 13.987153ms
      message: 'network-check-target-ip-10-0-131-226: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:51:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T05:57:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-31-to-network-check-target-ip-10-0-136-123
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-31.ec2.internal
      uid: b802feb0-55df-4cf2-bd12-9159e5f48a40
    resourceVersion: "157237"
    uid: 167d0e4d-d912-484d-84f5-97c4bc934cbb
  spec:
    sourcePod: network-check-source-6f78d59f99-7jsft
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T06:04:30Z"
      message: 'network-check-target-ip-10-0-136-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.535546ms
      message: 'network-check-target-ip-10-0-136-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T07:00:30Z"
    - latency: 2.478426ms
      message: 'network-check-target-ip-10-0-136-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:59:30Z"
    - latency: 2.776689ms
      message: 'network-check-target-ip-10-0-136-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:58:30Z"
    - latency: 2.452984ms
      message: 'network-check-target-ip-10-0-136-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:57:30Z"
    - latency: 2.50871ms
      message: 'network-check-target-ip-10-0-136-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:56:30Z"
    - latency: 2.850646ms
      message: 'network-check-target-ip-10-0-136-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:55:30Z"
    - latency: 2.609268ms
      message: 'network-check-target-ip-10-0-136-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:54:30Z"
    - latency: 19.056994ms
      message: 'network-check-target-ip-10-0-136-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:53:30Z"
    - latency: 3.113779ms
      message: 'network-check-target-ip-10-0-136-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:52:30Z"
    - latency: 17.683214ms
      message: 'network-check-target-ip-10-0-136-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:51:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T05:57:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-31-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-31.ec2.internal
      uid: b802feb0-55df-4cf2-bd12-9159e5f48a40
    resourceVersion: "148496"
    uid: 2c2be202-34c2-4023-a8e8-718d77cd0ff1
  spec:
    sourcePod: network-check-source-6f78d59f99-7jsft
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T06:03:30Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.286919ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:57:30Z"
    - latency: 2.137888ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:57:30Z"
    - latency: 1.444472ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:56:30Z"
    - latency: 2.039717ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:56:30Z"
    - latency: 1.071971ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:55:30Z"
    - latency: 2.097157ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:55:30Z"
    - latency: 1.647331ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:54:30Z"
    - latency: 2.257959ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:54:30Z"
    - latency: 10.521703ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T06:53:30Z"
    - latency: 26.563802ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T06:53:30Z"
kind: List
metadata:
  resourceVersion: ""