apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T13:09:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-18-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-18.ec2.internal
      uid: 374e27f7-6cf2-43b5-b2af-d6d7682c2d02
    resourceVersion: "42353"
    uid: 427aaaa3-ef78-42e6-aa5f-ae378e7fa44b
  spec:
    sourcePod: network-check-source-7f44b6dd87-ltm7d
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T13:16:46Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.116264ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:12:46Z"
    - latency: 874.769µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:11:46Z"
    - latency: 1.077006ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:10:46Z"
    - latency: 851.818µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:09:46Z"
    - latency: 840.862µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:08:46Z"
    - latency: 881.166µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:07:46Z"
    - latency: 973.158µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:06:46Z"
    - latency: 756.308µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:05:46Z"
    - latency: 945.056µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:04:46Z"
    - latency: 1.035265ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:03:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T13:09:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-18-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-18.ec2.internal
      uid: 374e27f7-6cf2-43b5-b2af-d6d7682c2d02
    resourceVersion: "43992"
    uid: df8a29a0-dadc-42a9-8a6a-7bbf5628b154
  spec:
    sourcePod: network-check-source-7f44b6dd87-ltm7d
    targetEndpoint: ab03792d3934a4d1e82cff6f2e6ed53e-21893a0925b5f6e3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T13:15:46Z"
      message: 'load-balancer-api-external: tcp connection to ab03792d3934a4d1e82cff6f2e6ed53e-21893a0925b5f6e3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.224252ms
      message: 'load-balancer-api-external: tcp connection to ab03792d3934a4d1e82cff6f2e6ed53e-21893a0925b5f6e3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:15:46Z"
    - latency: 6.734193ms
      message: 'load-balancer-api-external: resolved host name ab03792d3934a4d1e82cff6f2e6ed53e-21893a0925b5f6e3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T14:15:46Z"
    - latency: 5.701881ms
      message: 'load-balancer-api-external: tcp connection to ab03792d3934a4d1e82cff6f2e6ed53e-21893a0925b5f6e3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:14:46Z"
    - latency: 6.369685ms
      message: 'load-balancer-api-external: resolved host name ab03792d3934a4d1e82cff6f2e6ed53e-21893a0925b5f6e3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T14:14:46Z"
    - latency: 5.06305ms
      message: 'load-balancer-api-external: tcp connection to ab03792d3934a4d1e82cff6f2e6ed53e-21893a0925b5f6e3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:13:46Z"
    - latency: 6.51228ms
      message: 'load-balancer-api-external: resolved host name ab03792d3934a4d1e82cff6f2e6ed53e-21893a0925b5f6e3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T14:13:46Z"
    - latency: 14.359026ms
      message: 'load-balancer-api-external: tcp connection to ab03792d3934a4d1e82cff6f2e6ed53e-21893a0925b5f6e3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:12:46Z"
    - latency: 6.664409ms
      message: 'load-balancer-api-external: resolved host name ab03792d3934a4d1e82cff6f2e6ed53e-21893a0925b5f6e3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T14:12:46Z"
    - latency: 3.482559ms
      message: 'load-balancer-api-external: tcp connection to ab03792d3934a4d1e82cff6f2e6ed53e-21893a0925b5f6e3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:11:46Z"
    - latency: 6.611117ms
      message: 'load-balancer-api-external: resolved host name ab03792d3934a4d1e82cff6f2e6ed53e-21893a0925b5f6e3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T14:11:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T13:09:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-18-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-18.ec2.internal
      uid: 374e27f7-6cf2-43b5-b2af-d6d7682c2d02
    resourceVersion: "43993"
    uid: a1924a5c-210e-4584-b3ce-25917c2818c9
  spec:
    sourcePod: network-check-source-7f44b6dd87-ltm7d
    targetEndpoint: ab03792d3934a4d1e82cff6f2e6ed53e-21893a0925b5f6e3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T13:15:46Z"
      message: 'load-balancer-api-internal: tcp connection to ab03792d3934a4d1e82cff6f2e6ed53e-21893a0925b5f6e3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.830961ms
      message: 'load-balancer-api-internal: tcp connection to ab03792d3934a4d1e82cff6f2e6ed53e-21893a0925b5f6e3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:15:46Z"
    - latency: 6.850274ms
      message: 'load-balancer-api-internal: resolved host name ab03792d3934a4d1e82cff6f2e6ed53e-21893a0925b5f6e3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T14:15:46Z"
    - latency: 5.752704ms
      message: 'load-balancer-api-internal: tcp connection to ab03792d3934a4d1e82cff6f2e6ed53e-21893a0925b5f6e3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:14:46Z"
    - latency: 6.30833ms
      message: 'load-balancer-api-internal: resolved host name ab03792d3934a4d1e82cff6f2e6ed53e-21893a0925b5f6e3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T14:14:46Z"
    - latency: 5.074117ms
      message: 'load-balancer-api-internal: tcp connection to ab03792d3934a4d1e82cff6f2e6ed53e-21893a0925b5f6e3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:13:46Z"
    - latency: 6.481071ms
      message: 'load-balancer-api-internal: resolved host name ab03792d3934a4d1e82cff6f2e6ed53e-21893a0925b5f6e3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T14:13:46Z"
    - latency: 4.552622ms
      message: 'load-balancer-api-internal: tcp connection to ab03792d3934a4d1e82cff6f2e6ed53e-21893a0925b5f6e3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:12:46Z"
    - latency: 6.63673ms
      message: 'load-balancer-api-internal: resolved host name ab03792d3934a4d1e82cff6f2e6ed53e-21893a0925b5f6e3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T14:12:46Z"
    - latency: 4.264846ms
      message: 'load-balancer-api-internal: tcp connection to ab03792d3934a4d1e82cff6f2e6ed53e-21893a0925b5f6e3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:11:46Z"
    - latency: 6.725363ms
      message: 'load-balancer-api-internal: resolved host name ab03792d3934a4d1e82cff6f2e6ed53e-21893a0925b5f6e3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T14:11:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T13:09:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-18-to-network-check-target-ip-10-0-129-55
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-18.ec2.internal
      uid: 374e27f7-6cf2-43b5-b2af-d6d7682c2d02
    resourceVersion: "42352"
    uid: 739207ff-7084-436e-8e7a-c572abc4fb6f
  spec:
    sourcePod: network-check-source-7f44b6dd87-ltm7d
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T13:16:46Z"
      message: 'network-check-target-ip-10-0-129-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.188424ms
      message: 'network-check-target-ip-10-0-129-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:12:46Z"
    - latency: 2.171097ms
      message: 'network-check-target-ip-10-0-129-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:11:46Z"
    - latency: 2.448607ms
      message: 'network-check-target-ip-10-0-129-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:10:46Z"
    - latency: 1.950676ms
      message: 'network-check-target-ip-10-0-129-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:09:46Z"
    - latency: 2.383602ms
      message: 'network-check-target-ip-10-0-129-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:08:46Z"
    - latency: 2.064208ms
      message: 'network-check-target-ip-10-0-129-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:07:46Z"
    - latency: 2.100798ms
      message: 'network-check-target-ip-10-0-129-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:06:46Z"
    - latency: 2.001899ms
      message: 'network-check-target-ip-10-0-129-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:05:46Z"
    - latency: 2.056685ms
      message: 'network-check-target-ip-10-0-129-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:04:46Z"
    - latency: 2.217615ms
      message: 'network-check-target-ip-10-0-129-55: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:03:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T13:09:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-18-to-network-check-target-ip-10-0-131-161
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-18.ec2.internal
      uid: 374e27f7-6cf2-43b5-b2af-d6d7682c2d02
    resourceVersion: "42351"
    uid: aff682e2-0388-4e90-b87d-6f2e6fb997ad
  spec:
    sourcePod: network-check-source-7f44b6dd87-ltm7d
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T13:16:46Z"
      message: 'network-check-target-ip-10-0-131-161: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.226764ms
      message: 'network-check-target-ip-10-0-131-161: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:12:46Z"
    - latency: 2.217649ms
      message: 'network-check-target-ip-10-0-131-161: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:11:46Z"
    - latency: 2.481204ms
      message: 'network-check-target-ip-10-0-131-161: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:10:46Z"
    - latency: 1.936217ms
      message: 'network-check-target-ip-10-0-131-161: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:09:46Z"
    - latency: 2.393498ms
      message: 'network-check-target-ip-10-0-131-161: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:08:46Z"
    - latency: 2.162087ms
      message: 'network-check-target-ip-10-0-131-161: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:07:46Z"
    - latency: 1.854868ms
      message: 'network-check-target-ip-10-0-131-161: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:06:46Z"
    - latency: 2.239528ms
      message: 'network-check-target-ip-10-0-131-161: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:05:46Z"
    - latency: 2.127846ms
      message: 'network-check-target-ip-10-0-131-161: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:04:46Z"
    - latency: 2.227405ms
      message: 'network-check-target-ip-10-0-131-161: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:03:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T13:09:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-18-to-network-check-target-ip-10-0-139-18
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-18.ec2.internal
      uid: 374e27f7-6cf2-43b5-b2af-d6d7682c2d02
    resourceVersion: "42350"
    uid: 778a2af8-5b2a-40c2-aaad-81d0aacc5ba4
  spec:
    sourcePod: network-check-source-7f44b6dd87-ltm7d
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T13:16:46Z"
      message: 'network-check-target-ip-10-0-139-18: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 866.242µs
      message: 'network-check-target-ip-10-0-139-18: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:12:46Z"
    - latency: 798.405µs
      message: 'network-check-target-ip-10-0-139-18: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:11:46Z"
    - latency: 801.649µs
      message: 'network-check-target-ip-10-0-139-18: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:10:46Z"
    - latency: 995.924µs
      message: 'network-check-target-ip-10-0-139-18: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:09:46Z"
    - latency: 763.598µs
      message: 'network-check-target-ip-10-0-139-18: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:08:46Z"
    - latency: 800.64µs
      message: 'network-check-target-ip-10-0-139-18: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:07:46Z"
    - latency: 1.200807ms
      message: 'network-check-target-ip-10-0-139-18: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:06:46Z"
    - latency: 851.024µs
      message: 'network-check-target-ip-10-0-139-18: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:05:46Z"
    - latency: 783.139µs
      message: 'network-check-target-ip-10-0-139-18: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:04:46Z"
    - latency: 1.35108ms
      message: 'network-check-target-ip-10-0-139-18: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:03:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-25T13:09:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-18-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-18.ec2.internal
      uid: 374e27f7-6cf2-43b5-b2af-d6d7682c2d02
    resourceVersion: "43991"
    uid: 7fd22f4a-91fa-420c-a2b8-134699b1df5a
  spec:
    sourcePod: network-check-source-7f44b6dd87-ltm7d
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-25T13:15:46Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.394519ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:15:46Z"
    - latency: 1.767238ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T14:15:46Z"
    - latency: 1.0496ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:14:46Z"
    - latency: 1.628559ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T14:14:46Z"
    - latency: 851.738µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:13:46Z"
    - latency: 1.801646ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T14:13:46Z"
    - latency: 1.110607ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:12:46Z"
    - latency: 1.593428ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T14:12:46Z"
    - latency: 1.165518ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-25T14:11:46Z"
    - latency: 1.620274ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-25T14:11:46Z"
kind: List
metadata:
  resourceVersion: ""