apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T22:10:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-218-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-218.us-west-1.compute.internal
      uid: 8a9c70c7-6313-402c-a814-dfb01e0dfdc2
    resourceVersion: "33256"
    uid: a71fd932-670b-4c9e-8da4-d80f223ea82d
  spec:
    sourcePod: network-check-source-6f78d59f99-f8tgh
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T22:17:29Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.3859ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:06:29Z"
    - latency: 1.085468ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:05:29Z"
    - latency: 1.115507ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:04:29Z"
    - latency: 1.086418ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:03:29Z"
    - latency: 1.05688ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:02:29Z"
    - latency: 844.083µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:01:29Z"
    - latency: 998.843µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:00:29Z"
    - latency: 1.198303ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:59:29Z"
    - latency: 1.063792ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:58:29Z"
    - latency: 967.307µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:57:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T22:10:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-218-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-218.us-west-1.compute.internal
      uid: 8a9c70c7-6313-402c-a814-dfb01e0dfdc2
    resourceVersion: "35594"
    uid: 86ce6b6e-a109-438a-b3fc-939e97ff9b46
  spec:
    sourcePod: network-check-source-6f78d59f99-f8tgh
    targetEndpoint: a6f4d41d4389f4fb28595b18760ef362-f326b7236f2e3088.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T22:16:29Z"
      message: 'load-balancer-api-external: tcp connection to a6f4d41d4389f4fb28595b18760ef362-f326b7236f2e3088.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 55.149398ms
      message: 'load-balancer-api-external: tcp connection to a6f4d41d4389f4fb28595b18760ef362-f326b7236f2e3088.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:10:29Z"
    - latency: 7.757108ms
      message: 'load-balancer-api-external: resolved host name a6f4d41d4389f4fb28595b18760ef362-f326b7236f2e3088.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:10:29Z"
    - latency: 54.518138ms
      message: 'load-balancer-api-external: tcp connection to a6f4d41d4389f4fb28595b18760ef362-f326b7236f2e3088.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:09:29Z"
    - latency: 7.677586ms
      message: 'load-balancer-api-external: resolved host name a6f4d41d4389f4fb28595b18760ef362-f326b7236f2e3088.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:09:29Z"
    - latency: 54.123805ms
      message: 'load-balancer-api-external: tcp connection to a6f4d41d4389f4fb28595b18760ef362-f326b7236f2e3088.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:08:29Z"
    - latency: 7.875624ms
      message: 'load-balancer-api-external: resolved host name a6f4d41d4389f4fb28595b18760ef362-f326b7236f2e3088.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:08:29Z"
    - latency: 53.684463ms
      message: 'load-balancer-api-external: tcp connection to a6f4d41d4389f4fb28595b18760ef362-f326b7236f2e3088.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:07:29Z"
    - latency: 7.61195ms
      message: 'load-balancer-api-external: resolved host name a6f4d41d4389f4fb28595b18760ef362-f326b7236f2e3088.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:07:29Z"
    - latency: 54.537603ms
      message: 'load-balancer-api-external: tcp connection to a6f4d41d4389f4fb28595b18760ef362-f326b7236f2e3088.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:06:29Z"
    - latency: 7.503375ms
      message: 'load-balancer-api-external: resolved host name a6f4d41d4389f4fb28595b18760ef362-f326b7236f2e3088.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:06:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T22:10:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-218-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-218.us-west-1.compute.internal
      uid: 8a9c70c7-6313-402c-a814-dfb01e0dfdc2
    resourceVersion: "35595"
    uid: 56b13524-26ef-4e02-9210-59cd1b44554c
  spec:
    sourcePod: network-check-source-6f78d59f99-f8tgh
    targetEndpoint: a6f4d41d4389f4fb28595b18760ef362-f326b7236f2e3088.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T22:16:29Z"
      message: 'load-balancer-api-internal: tcp connection to a6f4d41d4389f4fb28595b18760ef362-f326b7236f2e3088.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 55.141333ms
      message: 'load-balancer-api-internal: tcp connection to a6f4d41d4389f4fb28595b18760ef362-f326b7236f2e3088.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:10:29Z"
    - latency: 7.690928ms
      message: 'load-balancer-api-internal: resolved host name a6f4d41d4389f4fb28595b18760ef362-f326b7236f2e3088.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:10:29Z"
    - latency: 55.155073ms
      message: 'load-balancer-api-internal: tcp connection to a6f4d41d4389f4fb28595b18760ef362-f326b7236f2e3088.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:09:29Z"
    - latency: 7.648213ms
      message: 'load-balancer-api-internal: resolved host name a6f4d41d4389f4fb28595b18760ef362-f326b7236f2e3088.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:09:29Z"
    - latency: 54.097535ms
      message: 'load-balancer-api-internal: tcp connection to a6f4d41d4389f4fb28595b18760ef362-f326b7236f2e3088.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:08:29Z"
    - latency: 7.841631ms
      message: 'load-balancer-api-internal: resolved host name a6f4d41d4389f4fb28595b18760ef362-f326b7236f2e3088.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:08:29Z"
    - latency: 53.753795ms
      message: 'load-balancer-api-internal: tcp connection to a6f4d41d4389f4fb28595b18760ef362-f326b7236f2e3088.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:07:29Z"
    - latency: 7.585051ms
      message: 'load-balancer-api-internal: resolved host name a6f4d41d4389f4fb28595b18760ef362-f326b7236f2e3088.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:07:29Z"
    - latency: 54.558215ms
      message: 'load-balancer-api-internal: tcp connection to a6f4d41d4389f4fb28595b18760ef362-f326b7236f2e3088.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:06:29Z"
    - latency: 7.472014ms
      message: 'load-balancer-api-internal: resolved host name a6f4d41d4389f4fb28595b18760ef362-f326b7236f2e3088.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:06:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T22:10:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-218-to-network-check-target-ip-10-0-129-150
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-218.us-west-1.compute.internal
      uid: 8a9c70c7-6313-402c-a814-dfb01e0dfdc2
    resourceVersion: "33255"
    uid: 40d01c01-3ef0-435c-8577-dad87f29b6ae
  spec:
    sourcePod: network-check-source-6f78d59f99-f8tgh
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T22:17:29Z"
      message: 'network-check-target-ip-10-0-129-150: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.692587ms
      message: 'network-check-target-ip-10-0-129-150: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:06:29Z"
    - latency: 2.478206ms
      message: 'network-check-target-ip-10-0-129-150: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:05:29Z"
    - latency: 1.9896ms
      message: 'network-check-target-ip-10-0-129-150: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:04:29Z"
    - latency: 2.154562ms
      message: 'network-check-target-ip-10-0-129-150: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:03:29Z"
    - latency: 1.958935ms
      message: 'network-check-target-ip-10-0-129-150: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:02:29Z"
    - latency: 2.083144ms
      message: 'network-check-target-ip-10-0-129-150: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:01:29Z"
    - latency: 1.900944ms
      message: 'network-check-target-ip-10-0-129-150: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:00:29Z"
    - latency: 2.132132ms
      message: 'network-check-target-ip-10-0-129-150: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:59:29Z"
    - latency: 2.124818ms
      message: 'network-check-target-ip-10-0-129-150: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:58:29Z"
    - latency: 1.992009ms
      message: 'network-check-target-ip-10-0-129-150: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:57:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T22:10:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-218-to-network-check-target-ip-10-0-133-218
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-218.us-west-1.compute.internal
      uid: 8a9c70c7-6313-402c-a814-dfb01e0dfdc2
    resourceVersion: "33253"
    uid: 86892f36-4696-48cd-b65b-dd9f567d12ce
  spec:
    sourcePod: network-check-source-6f78d59f99-f8tgh
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T22:17:29Z"
      message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 744.985µs
      message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:06:29Z"
    - latency: 898.853µs
      message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:05:29Z"
    - latency: 1.164582ms
      message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:04:29Z"
    - latency: 1.425686ms
      message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:03:29Z"
    - latency: 1.445168ms
      message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:02:29Z"
    - latency: 896.7µs
      message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:01:29Z"
    - latency: 1.357798ms
      message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:00:29Z"
    - latency: 988.53µs
      message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:59:29Z"
    - latency: 1.255347ms
      message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:58:29Z"
    - latency: 1.6404ms
      message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:57:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T22:10:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-218-to-network-check-target-ip-10-0-138-202
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-218.us-west-1.compute.internal
      uid: 8a9c70c7-6313-402c-a814-dfb01e0dfdc2
    resourceVersion: "33254"
    uid: 25dfcf36-9ba8-4e1f-ad47-9dc776139082
  spec:
    sourcePod: network-check-source-6f78d59f99-f8tgh
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T22:17:29Z"
      message: 'network-check-target-ip-10-0-138-202: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.660739ms
      message: 'network-check-target-ip-10-0-138-202: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:06:29Z"
    - latency: 1.630962ms
      message: 'network-check-target-ip-10-0-138-202: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:05:29Z"
    - latency: 2.249359ms
      message: 'network-check-target-ip-10-0-138-202: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:04:29Z"
    - latency: 1.432423ms
      message: 'network-check-target-ip-10-0-138-202: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:03:29Z"
    - latency: 1.638338ms
      message: 'network-check-target-ip-10-0-138-202: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:02:29Z"
    - latency: 1.48989ms
      message: 'network-check-target-ip-10-0-138-202: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:01:29Z"
    - latency: 1.385884ms
      message: 'network-check-target-ip-10-0-138-202: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:00:29Z"
    - latency: 1.541465ms
      message: 'network-check-target-ip-10-0-138-202: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:59:29Z"
    - latency: 1.427262ms
      message: 'network-check-target-ip-10-0-138-202: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:58:29Z"
    - latency: 1.472274ms
      message: 'network-check-target-ip-10-0-138-202: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:57:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T22:10:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-218-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-218.us-west-1.compute.internal
      uid: 8a9c70c7-6313-402c-a814-dfb01e0dfdc2
    resourceVersion: "35591"
    uid: 45fdff0c-420f-4777-99b4-1d1d56e8730c
  spec:
    sourcePod: network-check-source-6f78d59f99-f8tgh
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T22:16:29Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.1017ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:10:29Z"
    - latency: 1.931329ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:10:29Z"
    - latency: 893.352µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:09:29Z"
    - latency: 1.889223ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:09:29Z"
    - latency: 841.227µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:08:29Z"
    - latency: 2.076851ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:08:29Z"
    - latency: 1.999071ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:07:29Z"
    - latency: 1.665947ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:07:29Z"
    - latency: 740.202µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:06:29Z"
    - latency: 1.873875ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:06:29Z"
kind: List
metadata:
  resourceVersion: ""