apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:47:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-186-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-186.ec2.internal
      uid: b8accc7d-9bd7-4a2e-ac2f-bdefcaa76e22
    resourceVersion: "23459"
    uid: d144ef48-1d67-4255-ba9d-a550df93cfab
  spec:
    sourcePod: network-check-source-6f8b768455-n7tb4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:54:23Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.192495ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:08:23Z"
    - latency: 971.189µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:07:23Z"
    - latency: 1.047659ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:06:23Z"
    - latency: 1.093792ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:05:23Z"
    - latency: 1.02004ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:04:23Z"
    - latency: 1.281765ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:03:23Z"
    - latency: 1.091612ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:02:23Z"
    - latency: 1.486521ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:01:23Z"
    - latency: 971.266µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:00:23Z"
    - latency: 1.272855ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:59:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:47:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-186-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-186.ec2.internal
      uid: b8accc7d-9bd7-4a2e-ac2f-bdefcaa76e22
    resourceVersion: "22057"
    uid: 62da6373-14be-4dab-a422-45b2a4768ae8
  spec:
    sourcePod: network-check-source-6f8b768455-n7tb4
    targetEndpoint: ae5bd5b47e91e4ad4b6d562df1904140-527aa805ab7a83bd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:53:23Z"
      message: 'load-balancer-api-external: tcp connection to ae5bd5b47e91e4ad4b6d562df1904140-527aa805ab7a83bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.369511ms
      message: 'load-balancer-api-external: tcp connection to ae5bd5b47e91e4ad4b6d562df1904140-527aa805ab7a83bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:05:23Z"
    - latency: 8.889429ms
      message: 'load-balancer-api-external: resolved host name ae5bd5b47e91e4ad4b6d562df1904140-527aa805ab7a83bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:05:23Z"
    - latency: 5.965795ms
      message: 'load-balancer-api-external: tcp connection to ae5bd5b47e91e4ad4b6d562df1904140-527aa805ab7a83bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:04:23Z"
    - latency: 9.203519ms
      message: 'load-balancer-api-external: resolved host name ae5bd5b47e91e4ad4b6d562df1904140-527aa805ab7a83bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:04:23Z"
    - latency: 5.495165ms
      message: 'load-balancer-api-external: tcp connection to ae5bd5b47e91e4ad4b6d562df1904140-527aa805ab7a83bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:03:23Z"
    - latency: 7.996307ms
      message: 'load-balancer-api-external: resolved host name ae5bd5b47e91e4ad4b6d562df1904140-527aa805ab7a83bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:03:23Z"
    - latency: 4.159034ms
      message: 'load-balancer-api-external: tcp connection to ae5bd5b47e91e4ad4b6d562df1904140-527aa805ab7a83bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:02:23Z"
    - latency: 10.118104ms
      message: 'load-balancer-api-external: resolved host name ae5bd5b47e91e4ad4b6d562df1904140-527aa805ab7a83bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:02:23Z"
    - latency: 4.153443ms
      message: 'load-balancer-api-external: tcp connection to ae5bd5b47e91e4ad4b6d562df1904140-527aa805ab7a83bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:01:23Z"
    - latency: 9.339665ms
      message: 'load-balancer-api-external: resolved host name ae5bd5b47e91e4ad4b6d562df1904140-527aa805ab7a83bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:01:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:47:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-186-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-186.ec2.internal
      uid: b8accc7d-9bd7-4a2e-ac2f-bdefcaa76e22
    resourceVersion: "22058"
    uid: 8e9e0350-e43e-4a5b-bc23-9d9e11b2da1d
  spec:
    sourcePod: network-check-source-6f8b768455-n7tb4
    targetEndpoint: ae5bd5b47e91e4ad4b6d562df1904140-527aa805ab7a83bd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:53:23Z"
      message: 'load-balancer-api-internal: tcp connection to ae5bd5b47e91e4ad4b6d562df1904140-527aa805ab7a83bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.293844ms
      message: 'load-balancer-api-internal: tcp connection to ae5bd5b47e91e4ad4b6d562df1904140-527aa805ab7a83bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:05:23Z"
    - latency: 8.933103ms
      message: 'load-balancer-api-internal: resolved host name ae5bd5b47e91e4ad4b6d562df1904140-527aa805ab7a83bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:05:23Z"
    - latency: 4.825678ms
      message: 'load-balancer-api-internal: tcp connection to ae5bd5b47e91e4ad4b6d562df1904140-527aa805ab7a83bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:04:23Z"
    - latency: 9.24101ms
      message: 'load-balancer-api-internal: resolved host name ae5bd5b47e91e4ad4b6d562df1904140-527aa805ab7a83bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:04:23Z"
    - latency: 5.459484ms
      message: 'load-balancer-api-internal: tcp connection to ae5bd5b47e91e4ad4b6d562df1904140-527aa805ab7a83bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:03:23Z"
    - latency: 8.028395ms
      message: 'load-balancer-api-internal: resolved host name ae5bd5b47e91e4ad4b6d562df1904140-527aa805ab7a83bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:03:23Z"
    - latency: 10.773042ms
      message: 'load-balancer-api-internal: tcp connection to ae5bd5b47e91e4ad4b6d562df1904140-527aa805ab7a83bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:02:23Z"
    - latency: 10.160845ms
      message: 'load-balancer-api-internal: resolved host name ae5bd5b47e91e4ad4b6d562df1904140-527aa805ab7a83bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:02:23Z"
    - latency: 5.035944ms
      message: 'load-balancer-api-internal: tcp connection to ae5bd5b47e91e4ad4b6d562df1904140-527aa805ab7a83bd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:01:23Z"
    - latency: 9.395742ms
      message: 'load-balancer-api-internal: resolved host name ae5bd5b47e91e4ad4b6d562df1904140-527aa805ab7a83bd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:01:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:47:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-186-to-network-check-target-ip-10-0-128-253
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-186.ec2.internal
      uid: b8accc7d-9bd7-4a2e-ac2f-bdefcaa76e22
    resourceVersion: "23454"
    uid: 55daecef-6b0a-4ed5-a757-1540303d6b9d
  spec:
    sourcePod: network-check-source-6f8b768455-n7tb4
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:54:23Z"
      message: 'network-check-target-ip-10-0-128-253: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.293514ms
      message: 'network-check-target-ip-10-0-128-253: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:08:23Z"
    - latency: 1.992309ms
      message: 'network-check-target-ip-10-0-128-253: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:07:23Z"
    - latency: 1.825973ms
      message: 'network-check-target-ip-10-0-128-253: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:06:23Z"
    - latency: 2.252466ms
      message: 'network-check-target-ip-10-0-128-253: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:05:23Z"
    - latency: 2.265766ms
      message: 'network-check-target-ip-10-0-128-253: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:04:23Z"
    - latency: 2.327948ms
      message: 'network-check-target-ip-10-0-128-253: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:03:23Z"
    - latency: 2.192589ms
      message: 'network-check-target-ip-10-0-128-253: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:02:23Z"
    - latency: 2.568366ms
      message: 'network-check-target-ip-10-0-128-253: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:01:23Z"
    - latency: 2.207105ms
      message: 'network-check-target-ip-10-0-128-253: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:00:23Z"
    - latency: 2.018824ms
      message: 'network-check-target-ip-10-0-128-253: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:59:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:47:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-186-to-network-check-target-ip-10-0-130-186
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-186.ec2.internal
      uid: b8accc7d-9bd7-4a2e-ac2f-bdefcaa76e22
    resourceVersion: "23457"
    uid: db78b218-fb72-4265-96e1-70621560b963
  spec:
    sourcePod: network-check-source-6f8b768455-n7tb4
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:54:23Z"
      message: 'network-check-target-ip-10-0-130-186: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 808.996µs
      message: 'network-check-target-ip-10-0-130-186: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:08:23Z"
    - latency: 1.604625ms
      message: 'network-check-target-ip-10-0-130-186: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:07:23Z"
    - latency: 1.122083ms
      message: 'network-check-target-ip-10-0-130-186: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:06:23Z"
    - latency: 890.215µs
      message: 'network-check-target-ip-10-0-130-186: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:05:23Z"
    - latency: 864.036µs
      message: 'network-check-target-ip-10-0-130-186: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:04:23Z"
    - latency: 1.137077ms
      message: 'network-check-target-ip-10-0-130-186: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:03:23Z"
    - latency: 809.473µs
      message: 'network-check-target-ip-10-0-130-186: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:02:23Z"
    - latency: 706.402µs
      message: 'network-check-target-ip-10-0-130-186: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:01:23Z"
    - latency: 1.589213ms
      message: 'network-check-target-ip-10-0-130-186: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:00:23Z"
    - latency: 948.38µs
      message: 'network-check-target-ip-10-0-130-186: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:59:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:47:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-186-to-network-check-target-ip-10-0-132-80
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-186.ec2.internal
      uid: b8accc7d-9bd7-4a2e-ac2f-bdefcaa76e22
    resourceVersion: "23455"
    uid: 07cc96e8-1e52-4c6e-8a61-8bcb65bb852a
  spec:
    sourcePod: network-check-source-6f8b768455-n7tb4
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:54:23Z"
      message: 'network-check-target-ip-10-0-132-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.744177ms
      message: 'network-check-target-ip-10-0-132-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:08:23Z"
    - latency: 2.277051ms
      message: 'network-check-target-ip-10-0-132-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:07:23Z"
    - latency: 2.035522ms
      message: 'network-check-target-ip-10-0-132-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:06:23Z"
    - latency: 2.064666ms
      message: 'network-check-target-ip-10-0-132-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:05:23Z"
    - latency: 1.929833ms
      message: 'network-check-target-ip-10-0-132-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:04:23Z"
    - latency: 2.307953ms
      message: 'network-check-target-ip-10-0-132-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:03:23Z"
    - latency: 2.461816ms
      message: 'network-check-target-ip-10-0-132-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:02:23Z"
    - latency: 2.217962ms
      message: 'network-check-target-ip-10-0-132-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:01:23Z"
    - latency: 2.293111ms
      message: 'network-check-target-ip-10-0-132-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:00:23Z"
    - latency: 2.162115ms
      message: 'network-check-target-ip-10-0-132-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:59:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:47:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-186-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-186.ec2.internal
      uid: b8accc7d-9bd7-4a2e-ac2f-bdefcaa76e22
    resourceVersion: "22056"
    uid: ba078f0b-7fa7-428a-9ba9-a9ae62f5ead8
  spec:
    sourcePod: network-check-source-6f8b768455-n7tb4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:53:23Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.119001ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:05:23Z"
    - latency: 1.786558ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:05:23Z"
    - latency: 909.822µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:04:23Z"
    - latency: 1.87959ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:04:23Z"
    - latency: 796.736µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:03:23Z"
    - latency: 1.800188ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:03:23Z"
    - latency: 952.13µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:02:23Z"
    - latency: 2.406238ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:02:23Z"
    - latency: 933.924µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:01:23Z"
    - latency: 2.225048ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:01:23Z"
kind: List
metadata:
  resourceVersion: ""