apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T23:19:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-57-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-57.us-west-1.compute.internal
      uid: 4877730f-6b67-4211-9223-1dac5e1e0283
    resourceVersion: "27696"
    uid: 631408d9-2fb3-4156-87fd-3354dbb45fcb
  spec:
    sourcePod: network-check-source-6f78d59f99-vgl5w
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T23:26:09Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.70945ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:15:09Z"
    - latency: 1.015046ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:14:09Z"
    - latency: 891.391µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:13:09Z"
    - latency: 1.199621ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:12:09Z"
    - latency: 1.141499ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:11:09Z"
    - latency: 1.309569ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:10:09Z"
    - latency: 1.040862ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:09:09Z"
    - latency: 879.988µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:08:09Z"
    - latency: 1.129423ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:07:09Z"
    - latency: 1.193381ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:06:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T23:19:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-57-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-57.us-west-1.compute.internal
      uid: 4877730f-6b67-4211-9223-1dac5e1e0283
    resourceVersion: "27226"
    uid: d2036c25-59a0-44c3-9af8-92c4a647fb1a
  spec:
    sourcePod: network-check-source-6f78d59f99-vgl5w
    targetEndpoint: ac5e00aa449ee48d79ebca6dd0f2d6b6-437927c0249dc766.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T23:25:09Z"
      message: 'load-balancer-api-external: tcp connection to ac5e00aa449ee48d79ebca6dd0f2d6b6-437927c0249dc766.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 52.406301ms
      message: 'load-balancer-api-external: tcp connection to ac5e00aa449ee48d79ebca6dd0f2d6b6-437927c0249dc766.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:13:09Z"
    - latency: 9.208789ms
      message: 'load-balancer-api-external: resolved host name ac5e00aa449ee48d79ebca6dd0f2d6b6-437927c0249dc766.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:13:09Z"
    - latency: 52.560064ms
      message: 'load-balancer-api-external: tcp connection to ac5e00aa449ee48d79ebca6dd0f2d6b6-437927c0249dc766.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:12:09Z"
    - latency: 9.099607ms
      message: 'load-balancer-api-external: resolved host name ac5e00aa449ee48d79ebca6dd0f2d6b6-437927c0249dc766.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:12:09Z"
    - latency: 53.994466ms
      message: 'load-balancer-api-external: tcp connection to ac5e00aa449ee48d79ebca6dd0f2d6b6-437927c0249dc766.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:11:09Z"
    - latency: 7.532072ms
      message: 'load-balancer-api-external: resolved host name ac5e00aa449ee48d79ebca6dd0f2d6b6-437927c0249dc766.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:11:09Z"
    - latency: 53.728242ms
      message: 'load-balancer-api-external: tcp connection to ac5e00aa449ee48d79ebca6dd0f2d6b6-437927c0249dc766.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:10:09Z"
    - latency: 8.201852ms
      message: 'load-balancer-api-external: resolved host name ac5e00aa449ee48d79ebca6dd0f2d6b6-437927c0249dc766.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:10:09Z"
    - latency: 54.273389ms
      message: 'load-balancer-api-external: tcp connection to ac5e00aa449ee48d79ebca6dd0f2d6b6-437927c0249dc766.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:09:09Z"
    - latency: 7.677124ms
      message: 'load-balancer-api-external: resolved host name ac5e00aa449ee48d79ebca6dd0f2d6b6-437927c0249dc766.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:09:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T23:19:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-57-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-57.us-west-1.compute.internal
      uid: 4877730f-6b67-4211-9223-1dac5e1e0283
    resourceVersion: "27227"
    uid: 7302f24f-886d-49fd-891c-f25adc60e480
  spec:
    sourcePod: network-check-source-6f78d59f99-vgl5w
    targetEndpoint: ac5e00aa449ee48d79ebca6dd0f2d6b6-437927c0249dc766.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T23:25:09Z"
      message: 'load-balancer-api-internal: tcp connection to ac5e00aa449ee48d79ebca6dd0f2d6b6-437927c0249dc766.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 52.982191ms
      message: 'load-balancer-api-internal: tcp connection to ac5e00aa449ee48d79ebca6dd0f2d6b6-437927c0249dc766.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:13:09Z"
    - latency: 9.15367ms
      message: 'load-balancer-api-internal: resolved host name ac5e00aa449ee48d79ebca6dd0f2d6b6-437927c0249dc766.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:13:09Z"
    - latency: 52.149852ms
      message: 'load-balancer-api-internal: tcp connection to ac5e00aa449ee48d79ebca6dd0f2d6b6-437927c0249dc766.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:12:09Z"
    - latency: 9.001298ms
      message: 'load-balancer-api-internal: resolved host name ac5e00aa449ee48d79ebca6dd0f2d6b6-437927c0249dc766.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:12:09Z"
    - latency: 54.027806ms
      message: 'load-balancer-api-internal: tcp connection to ac5e00aa449ee48d79ebca6dd0f2d6b6-437927c0249dc766.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:11:09Z"
    - latency: 7.466939ms
      message: 'load-balancer-api-internal: resolved host name ac5e00aa449ee48d79ebca6dd0f2d6b6-437927c0249dc766.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:11:09Z"
    - latency: 53.389138ms
      message: 'load-balancer-api-internal: tcp connection to ac5e00aa449ee48d79ebca6dd0f2d6b6-437927c0249dc766.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:10:09Z"
    - latency: 8.247722ms
      message: 'load-balancer-api-internal: resolved host name ac5e00aa449ee48d79ebca6dd0f2d6b6-437927c0249dc766.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:10:09Z"
    - latency: 54.283561ms
      message: 'load-balancer-api-internal: tcp connection to ac5e00aa449ee48d79ebca6dd0f2d6b6-437927c0249dc766.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:09:09Z"
    - latency: 7.629212ms
      message: 'load-balancer-api-internal: resolved host name ac5e00aa449ee48d79ebca6dd0f2d6b6-437927c0249dc766.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:09:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T23:19:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-57-to-network-check-target-ip-10-0-131-99
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-57.us-west-1.compute.internal
      uid: 4877730f-6b67-4211-9223-1dac5e1e0283
    resourceVersion: "27693"
    uid: a0d66836-73d4-49a7-a06d-95a8475c406d
  spec:
    sourcePod: network-check-source-6f78d59f99-vgl5w
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T23:26:09Z"
      message: 'network-check-target-ip-10-0-131-99: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.819609ms
      message: 'network-check-target-ip-10-0-131-99: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:15:09Z"
    - latency: 2.491682ms
      message: 'network-check-target-ip-10-0-131-99: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:14:09Z"
    - latency: 1.848577ms
      message: 'network-check-target-ip-10-0-131-99: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:13:09Z"
    - latency: 2.162097ms
      message: 'network-check-target-ip-10-0-131-99: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:12:09Z"
    - latency: 2.35634ms
      message: 'network-check-target-ip-10-0-131-99: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:11:09Z"
    - latency: 2.424027ms
      message: 'network-check-target-ip-10-0-131-99: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:10:09Z"
    - latency: 1.770981ms
      message: 'network-check-target-ip-10-0-131-99: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:09:09Z"
    - latency: 2.081962ms
      message: 'network-check-target-ip-10-0-131-99: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:08:09Z"
    - latency: 2.137195ms
      message: 'network-check-target-ip-10-0-131-99: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:07:09Z"
    - latency: 1.981989ms
      message: 'network-check-target-ip-10-0-131-99: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:06:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T23:19:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-57-to-network-check-target-ip-10-0-133-221
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-57.us-west-1.compute.internal
      uid: 4877730f-6b67-4211-9223-1dac5e1e0283
    resourceVersion: "27694"
    uid: 04f42dd9-741f-4820-ab10-0d905014756f
  spec:
    sourcePod: network-check-source-6f78d59f99-vgl5w
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T23:26:09Z"
      message: 'network-check-target-ip-10-0-133-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.785946ms
      message: 'network-check-target-ip-10-0-133-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:15:09Z"
    - latency: 2.127923ms
      message: 'network-check-target-ip-10-0-133-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:14:09Z"
    - latency: 2.135435ms
      message: 'network-check-target-ip-10-0-133-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:13:09Z"
    - latency: 1.953428ms
      message: 'network-check-target-ip-10-0-133-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:12:09Z"
    - latency: 2.145885ms
      message: 'network-check-target-ip-10-0-133-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:11:09Z"
    - latency: 1.940967ms
      message: 'network-check-target-ip-10-0-133-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:10:09Z"
    - latency: 1.960626ms
      message: 'network-check-target-ip-10-0-133-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:09:09Z"
    - latency: 1.991254ms
      message: 'network-check-target-ip-10-0-133-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:08:09Z"
    - latency: 1.918203ms
      message: 'network-check-target-ip-10-0-133-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:07:09Z"
    - latency: 1.871782ms
      message: 'network-check-target-ip-10-0-133-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:06:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T23:19:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-57-to-network-check-target-ip-10-0-134-57
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-57.us-west-1.compute.internal
      uid: 4877730f-6b67-4211-9223-1dac5e1e0283
    resourceVersion: "27692"
    uid: 61e17cc9-ac13-4229-9fdb-d4688ca5db6e
  spec:
    sourcePod: network-check-source-6f78d59f99-vgl5w
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T23:26:09Z"
      message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 762.136µs
      message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:15:09Z"
    - latency: 856.582µs
      message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:14:09Z"
    - latency: 1.50933ms
      message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:13:09Z"
    - latency: 784.205µs
      message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:12:09Z"
    - latency: 773.665µs
      message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:11:09Z"
    - latency: 1.484853ms
      message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:10:09Z"
    - latency: 805.805µs
      message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:09:09Z"
    - latency: 1.204045ms
      message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:08:09Z"
    - latency: 1.222375ms
      message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:07:09Z"
    - latency: 1.674568ms
      message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:06:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T23:19:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-57-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-57.us-west-1.compute.internal
      uid: 4877730f-6b67-4211-9223-1dac5e1e0283
    resourceVersion: "27225"
    uid: 74b58b31-cc68-4627-bf7d-0c602ae85e0e
  spec:
    sourcePod: network-check-source-6f78d59f99-vgl5w
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T23:25:09Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 930.556µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:13:09Z"
    - latency: 2.456163ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:13:09Z"
    - latency: 813.774µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:12:09Z"
    - latency: 2.224276ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:12:09Z"
    - latency: 904.55µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:11:09Z"
    - latency: 1.744386ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:11:09Z"
    - latency: 1.085159ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:10:09Z"
    - latency: 1.992945ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:10:09Z"
    - latency: 894.489µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:09:09Z"
    - latency: 1.921728ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:09:09Z"
kind: List
metadata:
  resourceVersion: ""