apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T16:37:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-142-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-142.ec2.internal
      uid: d3a189ec-c035-4688-b96a-f2703e800ca9
    resourceVersion: "21462"
    uid: 3c148c55-02f6-4ce9-bcf0-e20bbf28b74b
  spec:
    sourcePod: network-check-source-989f8b8dc-wcls4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T16:44:41Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.101055ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:58:41Z"
    - latency: 946.372µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:57:41Z"
    - latency: 1.346896ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:56:41Z"
    - latency: 851.301µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:55:41Z"
    - latency: 1.30889ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:54:41Z"
    - latency: 1.433246ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:53:41Z"
    - latency: 1.674715ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:52:41Z"
    - latency: 1.344526ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:51:41Z"
    - latency: 1.104961ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:50:41Z"
    - latency: 874.233µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:49:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T16:37:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-142-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-142.ec2.internal
      uid: d3a189ec-c035-4688-b96a-f2703e800ca9
    resourceVersion: "20124"
    uid: a58b3828-1c06-416e-98ea-fa9011d3df02
  spec:
    sourcePod: network-check-source-989f8b8dc-wcls4
    targetEndpoint: aa2bbf3bcf11e4d9d9e175f6e6194e00-040542b9a4fbfa9f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T16:43:41Z"
      message: 'load-balancer-api-external: tcp connection to aa2bbf3bcf11e4d9d9e175f6e6194e00-040542b9a4fbfa9f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.540216ms
      message: 'load-balancer-api-external: tcp connection to aa2bbf3bcf11e4d9d9e175f6e6194e00-040542b9a4fbfa9f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:55:41Z"
    - latency: 6.52721ms
      message: 'load-balancer-api-external: resolved host name aa2bbf3bcf11e4d9d9e175f6e6194e00-040542b9a4fbfa9f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T16:55:41Z"
    - latency: 6.799626ms
      message: 'load-balancer-api-external: tcp connection to aa2bbf3bcf11e4d9d9e175f6e6194e00-040542b9a4fbfa9f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:54:41Z"
    - latency: 6.484054ms
      message: 'load-balancer-api-external: resolved host name aa2bbf3bcf11e4d9d9e175f6e6194e00-040542b9a4fbfa9f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T16:54:41Z"
    - latency: 5.846949ms
      message: 'load-balancer-api-external: tcp connection to aa2bbf3bcf11e4d9d9e175f6e6194e00-040542b9a4fbfa9f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:53:41Z"
    - latency: 6.222794ms
      message: 'load-balancer-api-external: resolved host name aa2bbf3bcf11e4d9d9e175f6e6194e00-040542b9a4fbfa9f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T16:53:41Z"
    - latency: 5.360168ms
      message: 'load-balancer-api-external: tcp connection to aa2bbf3bcf11e4d9d9e175f6e6194e00-040542b9a4fbfa9f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:52:41Z"
    - latency: 7.041799ms
      message: 'load-balancer-api-external: resolved host name aa2bbf3bcf11e4d9d9e175f6e6194e00-040542b9a4fbfa9f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T16:52:41Z"
    - latency: 5.72781ms
      message: 'load-balancer-api-external: tcp connection to aa2bbf3bcf11e4d9d9e175f6e6194e00-040542b9a4fbfa9f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:51:41Z"
    - latency: 6.82242ms
      message: 'load-balancer-api-external: resolved host name aa2bbf3bcf11e4d9d9e175f6e6194e00-040542b9a4fbfa9f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T16:51:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T16:37:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-142-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-142.ec2.internal
      uid: d3a189ec-c035-4688-b96a-f2703e800ca9
    resourceVersion: "20123"
    uid: 12f4d5a7-0389-4ae8-9fd6-fe38555be0e6
  spec:
    sourcePod: network-check-source-989f8b8dc-wcls4
    targetEndpoint: aa2bbf3bcf11e4d9d9e175f6e6194e00-040542b9a4fbfa9f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T16:43:41Z"
      message: 'load-balancer-api-internal: tcp connection to aa2bbf3bcf11e4d9d9e175f6e6194e00-040542b9a4fbfa9f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.583405ms
      message: 'load-balancer-api-internal: tcp connection to aa2bbf3bcf11e4d9d9e175f6e6194e00-040542b9a4fbfa9f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:55:41Z"
    - latency: 6.495458ms
      message: 'load-balancer-api-internal: resolved host name aa2bbf3bcf11e4d9d9e175f6e6194e00-040542b9a4fbfa9f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T16:55:41Z"
    - latency: 6.882705ms
      message: 'load-balancer-api-internal: tcp connection to aa2bbf3bcf11e4d9d9e175f6e6194e00-040542b9a4fbfa9f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:54:41Z"
    - latency: 6.434797ms
      message: 'load-balancer-api-internal: resolved host name aa2bbf3bcf11e4d9d9e175f6e6194e00-040542b9a4fbfa9f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T16:54:41Z"
    - latency: 5.802649ms
      message: 'load-balancer-api-internal: tcp connection to aa2bbf3bcf11e4d9d9e175f6e6194e00-040542b9a4fbfa9f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:53:41Z"
    - latency: 6.261612ms
      message: 'load-balancer-api-internal: resolved host name aa2bbf3bcf11e4d9d9e175f6e6194e00-040542b9a4fbfa9f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T16:53:41Z"
    - latency: 4.890956ms
      message: 'load-balancer-api-internal: tcp connection to aa2bbf3bcf11e4d9d9e175f6e6194e00-040542b9a4fbfa9f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:52:41Z"
    - latency: 6.986631ms
      message: 'load-balancer-api-internal: resolved host name aa2bbf3bcf11e4d9d9e175f6e6194e00-040542b9a4fbfa9f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T16:52:41Z"
    - latency: 5.758266ms
      message: 'load-balancer-api-internal: tcp connection to aa2bbf3bcf11e4d9d9e175f6e6194e00-040542b9a4fbfa9f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:51:41Z"
    - latency: 6.717019ms
      message: 'load-balancer-api-internal: resolved host name aa2bbf3bcf11e4d9d9e175f6e6194e00-040542b9a4fbfa9f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T16:51:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T16:37:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-142-to-network-check-target-ip-10-0-132-142
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-142.ec2.internal
      uid: d3a189ec-c035-4688-b96a-f2703e800ca9
    resourceVersion: "21459"
    uid: 11f94b9c-ebb5-4aea-8ab8-d430c871ee74
  spec:
    sourcePod: network-check-source-989f8b8dc-wcls4
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T16:44:41Z"
      message: 'network-check-target-ip-10-0-132-142: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 903.728µs
      message: 'network-check-target-ip-10-0-132-142: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:58:41Z"
    - latency: 1.336888ms
      message: 'network-check-target-ip-10-0-132-142: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:57:41Z"
    - latency: 921.44µs
      message: 'network-check-target-ip-10-0-132-142: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:56:41Z"
    - latency: 789.169µs
      message: 'network-check-target-ip-10-0-132-142: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:55:41Z"
    - latency: 927.554µs
      message: 'network-check-target-ip-10-0-132-142: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:54:41Z"
    - latency: 1.011112ms
      message: 'network-check-target-ip-10-0-132-142: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:53:41Z"
    - latency: 1.117584ms
      message: 'network-check-target-ip-10-0-132-142: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:52:41Z"
    - latency: 1.56236ms
      message: 'network-check-target-ip-10-0-132-142: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:51:41Z"
    - latency: 956.756µs
      message: 'network-check-target-ip-10-0-132-142: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:50:41Z"
    - latency: 854.694µs
      message: 'network-check-target-ip-10-0-132-142: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:49:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T16:37:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-142-to-network-check-target-ip-10-0-134-45
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-142.ec2.internal
      uid: d3a189ec-c035-4688-b96a-f2703e800ca9
    resourceVersion: "21461"
    uid: a02b6295-a153-4cf0-b73d-6b8bc632cb9a
  spec:
    sourcePod: network-check-source-989f8b8dc-wcls4
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T16:44:41Z"
      message: 'network-check-target-ip-10-0-134-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.403919ms
      message: 'network-check-target-ip-10-0-134-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:58:41Z"
    - latency: 2.1642ms
      message: 'network-check-target-ip-10-0-134-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:57:41Z"
    - latency: 2.165902ms
      message: 'network-check-target-ip-10-0-134-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:56:41Z"
    - latency: 1.94223ms
      message: 'network-check-target-ip-10-0-134-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:55:41Z"
    - latency: 2.077185ms
      message: 'network-check-target-ip-10-0-134-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:54:41Z"
    - latency: 2.37ms
      message: 'network-check-target-ip-10-0-134-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:53:41Z"
    - latency: 2.179252ms
      message: 'network-check-target-ip-10-0-134-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:52:41Z"
    - latency: 2.167187ms
      message: 'network-check-target-ip-10-0-134-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:51:41Z"
    - latency: 2.333077ms
      message: 'network-check-target-ip-10-0-134-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:50:41Z"
    - latency: 2.133349ms
      message: 'network-check-target-ip-10-0-134-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:49:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T16:37:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-142-to-network-check-target-ip-10-0-137-118
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-142.ec2.internal
      uid: d3a189ec-c035-4688-b96a-f2703e800ca9
    resourceVersion: "21460"
    uid: 61d51435-c005-4ce3-a4f9-60ac779df63f
  spec:
    sourcePod: network-check-source-989f8b8dc-wcls4
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T16:44:41Z"
      message: 'network-check-target-ip-10-0-137-118: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.910661ms
      message: 'network-check-target-ip-10-0-137-118: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:58:41Z"
    - latency: 1.825811ms
      message: 'network-check-target-ip-10-0-137-118: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:57:41Z"
    - latency: 1.654925ms
      message: 'network-check-target-ip-10-0-137-118: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:56:41Z"
    - latency: 1.535232ms
      message: 'network-check-target-ip-10-0-137-118: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:55:41Z"
    - latency: 1.919295ms
      message: 'network-check-target-ip-10-0-137-118: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:54:41Z"
    - latency: 1.898397ms
      message: 'network-check-target-ip-10-0-137-118: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:53:41Z"
    - latency: 1.792441ms
      message: 'network-check-target-ip-10-0-137-118: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:52:41Z"
    - latency: 1.971034ms
      message: 'network-check-target-ip-10-0-137-118: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:51:41Z"
    - latency: 1.935494ms
      message: 'network-check-target-ip-10-0-137-118: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:50:41Z"
    - latency: 1.833334ms
      message: 'network-check-target-ip-10-0-137-118: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:49:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T16:37:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-142-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-142.ec2.internal
      uid: d3a189ec-c035-4688-b96a-f2703e800ca9
    resourceVersion: "20122"
    uid: 29d658ba-8492-4caa-a3f1-fc49f0c42d84
  spec:
    sourcePod: network-check-source-989f8b8dc-wcls4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T16:43:41Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 887.408µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:55:41Z"
    - latency: 1.975804ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T16:55:41Z"
    - latency: 829.53µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:54:41Z"
    - latency: 1.557346ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T16:54:41Z"
    - latency: 833.204µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:53:41Z"
    - latency: 1.646577ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T16:53:41Z"
    - latency: 862.995µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:52:41Z"
    - latency: 1.853496ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T16:52:41Z"
    - latency: 1.047123ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T16:51:41Z"
    - latency: 1.973701ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T16:51:41Z"
kind: List
metadata:
  resourceVersion: ""