apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T02:42:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-238-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-238.ec2.internal
      uid: 37deca83-43a8-46f1-833a-49f10a43883e
    resourceVersion: "144524"
    uid: d31cb388-44ec-4e0f-993d-a732b275e189
  spec:
    sourcePod: network-check-source-6f78d59f99-tngw9
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T02:50:00Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 949.834µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:46:00Z"
    - latency: 875.45µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:45:00Z"
    - latency: 1.184347ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:44:00Z"
    - latency: 1.380139ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:43:00Z"
    - latency: 1.577867ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:42:00Z"
    - latency: 1.044773ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:41:00Z"
    - latency: 1.026705ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:40:00Z"
    - latency: 943.723µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:39:00Z"
    - latency: 1.617752ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:38:00Z"
    - latency: 1.783725ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:37:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T02:42:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-238-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-238.ec2.internal
      uid: 37deca83-43a8-46f1-833a-49f10a43883e
    resourceVersion: "141904"
    uid: 0ebc9a85-d09a-4e41-ab39-db285b0d5b38
  spec:
    sourcePod: network-check-source-6f78d59f99-tngw9
    targetEndpoint: a6d4cef1d031a4ec3b651d41b88aa695-b30f8d557198ac4b.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T02:49:00Z"
      message: 'load-balancer-api-external: tcp connection to a6d4cef1d031a4ec3b651d41b88aa695-b30f8d557198ac4b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 15.266092ms
      message: 'load-balancer-api-external: tcp connection to a6d4cef1d031a4ec3b651d41b88aa695-b30f8d557198ac4b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:43:00Z"
    - latency: 7.395861ms
      message: 'load-balancer-api-external: resolved host name a6d4cef1d031a4ec3b651d41b88aa695-b30f8d557198ac4b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T03:43:00Z"
    - latency: 16.257452ms
      message: 'load-balancer-api-external: tcp connection to a6d4cef1d031a4ec3b651d41b88aa695-b30f8d557198ac4b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:42:00Z"
    - latency: 7.314021ms
      message: 'load-balancer-api-external: resolved host name a6d4cef1d031a4ec3b651d41b88aa695-b30f8d557198ac4b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T03:42:00Z"
    - latency: 19.543242ms
      message: 'load-balancer-api-external: tcp connection to a6d4cef1d031a4ec3b651d41b88aa695-b30f8d557198ac4b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:41:00Z"
    - latency: 8.465132ms
      message: 'load-balancer-api-external: resolved host name a6d4cef1d031a4ec3b651d41b88aa695-b30f8d557198ac4b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T03:41:00Z"
    - latency: 17.046256ms
      message: 'load-balancer-api-external: tcp connection to a6d4cef1d031a4ec3b651d41b88aa695-b30f8d557198ac4b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:40:00Z"
    - latency: 6.502464ms
      message: 'load-balancer-api-external: resolved host name a6d4cef1d031a4ec3b651d41b88aa695-b30f8d557198ac4b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T03:40:00Z"
    - latency: 17.813084ms
      message: 'load-balancer-api-external: tcp connection to a6d4cef1d031a4ec3b651d41b88aa695-b30f8d557198ac4b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:39:00Z"
    - latency: 7.39377ms
      message: 'load-balancer-api-external: resolved host name a6d4cef1d031a4ec3b651d41b88aa695-b30f8d557198ac4b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T03:39:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T02:42:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-238-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-238.ec2.internal
      uid: 37deca83-43a8-46f1-833a-49f10a43883e
    resourceVersion: "141905"
    uid: eff85c95-d73e-477b-a6c7-f75ae9e14cd6
  spec:
    sourcePod: network-check-source-6f78d59f99-tngw9
    targetEndpoint: a6d4cef1d031a4ec3b651d41b88aa695-b30f8d557198ac4b.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T02:49:00Z"
      message: 'load-balancer-api-internal: tcp connection to a6d4cef1d031a4ec3b651d41b88aa695-b30f8d557198ac4b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 19.245133ms
      message: 'load-balancer-api-internal: tcp connection to a6d4cef1d031a4ec3b651d41b88aa695-b30f8d557198ac4b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:43:00Z"
    - latency: 7.484277ms
      message: 'load-balancer-api-internal: resolved host name a6d4cef1d031a4ec3b651d41b88aa695-b30f8d557198ac4b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T03:43:00Z"
    - latency: 17.855103ms
      message: 'load-balancer-api-internal: tcp connection to a6d4cef1d031a4ec3b651d41b88aa695-b30f8d557198ac4b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:42:00Z"
    - latency: 7.371041ms
      message: 'load-balancer-api-internal: resolved host name a6d4cef1d031a4ec3b651d41b88aa695-b30f8d557198ac4b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T03:42:00Z"
    - latency: 19.554159ms
      message: 'load-balancer-api-internal: tcp connection to a6d4cef1d031a4ec3b651d41b88aa695-b30f8d557198ac4b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:41:00Z"
    - latency: 8.443978ms
      message: 'load-balancer-api-internal: resolved host name a6d4cef1d031a4ec3b651d41b88aa695-b30f8d557198ac4b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T03:41:00Z"
    - latency: 17.81623ms
      message: 'load-balancer-api-internal: tcp connection to a6d4cef1d031a4ec3b651d41b88aa695-b30f8d557198ac4b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:40:00Z"
    - latency: 6.43997ms
      message: 'load-balancer-api-internal: resolved host name a6d4cef1d031a4ec3b651d41b88aa695-b30f8d557198ac4b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T03:40:00Z"
    - latency: 16.433731ms
      message: 'load-balancer-api-internal: tcp connection to a6d4cef1d031a4ec3b651d41b88aa695-b30f8d557198ac4b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:39:00Z"
    - latency: 7.418836ms
      message: 'load-balancer-api-internal: resolved host name a6d4cef1d031a4ec3b651d41b88aa695-b30f8d557198ac4b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T03:39:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T02:42:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-238-to-network-check-target-ip-10-0-128-214
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-238.ec2.internal
      uid: 37deca83-43a8-46f1-833a-49f10a43883e
    resourceVersion: "144522"
    uid: b0551cd8-e97d-4525-b5ef-e984a5785225
  spec:
    sourcePod: network-check-source-6f78d59f99-tngw9
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T02:50:00Z"
      message: 'network-check-target-ip-10-0-128-214: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.261492ms
      message: 'network-check-target-ip-10-0-128-214: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:46:00Z"
    - latency: 2.141686ms
      message: 'network-check-target-ip-10-0-128-214: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:45:00Z"
    - latency: 2.213293ms
      message: 'network-check-target-ip-10-0-128-214: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:44:00Z"
    - latency: 1.839057ms
      message: 'network-check-target-ip-10-0-128-214: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:43:00Z"
    - latency: 2.238621ms
      message: 'network-check-target-ip-10-0-128-214: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:42:00Z"
    - latency: 2.395699ms
      message: 'network-check-target-ip-10-0-128-214: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:41:00Z"
    - latency: 1.870597ms
      message: 'network-check-target-ip-10-0-128-214: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:40:00Z"
    - latency: 2.342579ms
      message: 'network-check-target-ip-10-0-128-214: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:39:00Z"
    - latency: 2.533727ms
      message: 'network-check-target-ip-10-0-128-214: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:38:00Z"
    - latency: 2.046825ms
      message: 'network-check-target-ip-10-0-128-214: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:37:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T02:42:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-238-to-network-check-target-ip-10-0-136-171
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-238.ec2.internal
      uid: 37deca83-43a8-46f1-833a-49f10a43883e
    resourceVersion: "144523"
    uid: 7b05cf0c-b932-460a-ae2b-a04a38ba48de
  spec:
    sourcePod: network-check-source-6f78d59f99-tngw9
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T02:50:00Z"
      message: 'network-check-target-ip-10-0-136-171: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.393245ms
      message: 'network-check-target-ip-10-0-136-171: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:46:00Z"
    - latency: 2.646414ms
      message: 'network-check-target-ip-10-0-136-171: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:45:00Z"
    - latency: 2.58962ms
      message: 'network-check-target-ip-10-0-136-171: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:44:00Z"
    - latency: 2.739685ms
      message: 'network-check-target-ip-10-0-136-171: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:43:00Z"
    - latency: 2.177378ms
      message: 'network-check-target-ip-10-0-136-171: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:42:00Z"
    - latency: 2.639766ms
      message: 'network-check-target-ip-10-0-136-171: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:41:00Z"
    - latency: 2.387804ms
      message: 'network-check-target-ip-10-0-136-171: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:40:00Z"
    - latency: 2.368882ms
      message: 'network-check-target-ip-10-0-136-171: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:39:00Z"
    - latency: 2.055992ms
      message: 'network-check-target-ip-10-0-136-171: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:38:00Z"
    - latency: 2.194123ms
      message: 'network-check-target-ip-10-0-136-171: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:37:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T02:42:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-238-to-network-check-target-ip-10-0-136-238
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-238.ec2.internal
      uid: 37deca83-43a8-46f1-833a-49f10a43883e
    resourceVersion: "144521"
    uid: 6e182928-d117-495a-9133-deeb57ed94cd
  spec:
    sourcePod: network-check-source-6f78d59f99-tngw9
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T02:50:00Z"
      message: 'network-check-target-ip-10-0-136-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 968.901µs
      message: 'network-check-target-ip-10-0-136-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:46:00Z"
    - latency: 1.583222ms
      message: 'network-check-target-ip-10-0-136-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:45:00Z"
    - latency: 1.61753ms
      message: 'network-check-target-ip-10-0-136-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:44:00Z"
    - latency: 969.595µs
      message: 'network-check-target-ip-10-0-136-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:43:00Z"
    - latency: 995.233µs
      message: 'network-check-target-ip-10-0-136-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:42:00Z"
    - latency: 1.425677ms
      message: 'network-check-target-ip-10-0-136-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:41:00Z"
    - latency: 1.163386ms
      message: 'network-check-target-ip-10-0-136-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:40:00Z"
    - latency: 1.167458ms
      message: 'network-check-target-ip-10-0-136-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:39:00Z"
    - latency: 1.050999ms
      message: 'network-check-target-ip-10-0-136-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:38:00Z"
    - latency: 1.171929ms
      message: 'network-check-target-ip-10-0-136-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:37:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T02:42:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-238-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-238.ec2.internal
      uid: 37deca83-43a8-46f1-833a-49f10a43883e
    resourceVersion: "141902"
    uid: 8359d70b-12c7-45a2-89be-866604d227a3
  spec:
    sourcePod: network-check-source-6f78d59f99-tngw9
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T02:49:00Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.18491ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:43:00Z"
    - latency: 2.049825ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T03:43:00Z"
    - latency: 1.134091ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:42:00Z"
    - latency: 2.063923ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T03:42:00Z"
    - latency: 1.142438ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:41:00Z"
    - latency: 1.846813ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T03:41:00Z"
    - latency: 1.279921ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:40:00Z"
    - latency: 1.893101ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T03:40:00Z"
    - latency: 1.246805ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:39:00Z"
    - latency: 2.174831ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T03:39:00Z"
kind: List
metadata:
  resourceVersion: ""