apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T04:52:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-238-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-238.ec2.internal
      uid: 3b91913f-2be8-4108-8c06-19aa53d7dfc6
    resourceVersion: "67084"
    uid: c58b96b8-1bc0-4d4c-b647-a5d44421b2a4
  spec:
    sourcePod: network-check-source-6f8b768455-ptzr2
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T04:59:27Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.292314ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:27:27Z"
    - latency: 1.083536ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:26:27Z"
    - latency: 1.367607ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:25:27Z"
    - latency: 1.020257ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:24:27Z"
    - latency: 1.000592ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:23:27Z"
    - latency: 971.739µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:22:27Z"
    - latency: 1.02097ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:21:27Z"
    - latency: 882.479µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:20:27Z"
    - latency: 5.698805ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:19:27Z"
    - latency: 1.543847ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:18:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T04:52:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-238-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-238.ec2.internal
      uid: 3b91913f-2be8-4108-8c06-19aa53d7dfc6
    resourceVersion: "67990"
    uid: be7b8773-4232-409a-8ff5-0fee2249b74a
  spec:
    sourcePod: network-check-source-6f8b768455-ptzr2
    targetEndpoint: af5d20d6e5cdf452c94f0ea39d3b9831-58da2d9518a9f028.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T04:58:27Z"
      message: 'load-balancer-api-external: tcp connection to af5d20d6e5cdf452c94f0ea39d3b9831-58da2d9518a9f028.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.748309ms
      message: 'load-balancer-api-external: tcp connection to af5d20d6e5cdf452c94f0ea39d3b9831-58da2d9518a9f028.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:28:27Z"
    - latency: 8.07653ms
      message: 'load-balancer-api-external: resolved host name af5d20d6e5cdf452c94f0ea39d3b9831-58da2d9518a9f028.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T05:28:27Z"
    - latency: 3.742976ms
      message: 'load-balancer-api-external: tcp connection to af5d20d6e5cdf452c94f0ea39d3b9831-58da2d9518a9f028.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:27:27Z"
    - latency: 7.60428ms
      message: 'load-balancer-api-external: resolved host name af5d20d6e5cdf452c94f0ea39d3b9831-58da2d9518a9f028.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T05:27:27Z"
    - latency: 4.051824ms
      message: 'load-balancer-api-external: tcp connection to af5d20d6e5cdf452c94f0ea39d3b9831-58da2d9518a9f028.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:26:27Z"
    - latency: 6.286557ms
      message: 'load-balancer-api-external: resolved host name af5d20d6e5cdf452c94f0ea39d3b9831-58da2d9518a9f028.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T05:26:27Z"
    - latency: 4.91773ms
      message: 'load-balancer-api-external: tcp connection to af5d20d6e5cdf452c94f0ea39d3b9831-58da2d9518a9f028.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:25:27Z"
    - latency: 7.089258ms
      message: 'load-balancer-api-external: resolved host name af5d20d6e5cdf452c94f0ea39d3b9831-58da2d9518a9f028.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T05:25:27Z"
    - latency: 3.026134ms
      message: 'load-balancer-api-external: tcp connection to af5d20d6e5cdf452c94f0ea39d3b9831-58da2d9518a9f028.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:24:27Z"
    - latency: 6.214409ms
      message: 'load-balancer-api-external: resolved host name af5d20d6e5cdf452c94f0ea39d3b9831-58da2d9518a9f028.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T05:24:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T04:52:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-238-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-238.ec2.internal
      uid: 3b91913f-2be8-4108-8c06-19aa53d7dfc6
    resourceVersion: "67989"
    uid: eeb89741-ee5c-4f82-8cd7-5c7395713374
  spec:
    sourcePod: network-check-source-6f8b768455-ptzr2
    targetEndpoint: af5d20d6e5cdf452c94f0ea39d3b9831-58da2d9518a9f028.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T04:58:27Z"
      message: 'load-balancer-api-internal: tcp connection to af5d20d6e5cdf452c94f0ea39d3b9831-58da2d9518a9f028.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.734799ms
      message: 'load-balancer-api-internal: tcp connection to af5d20d6e5cdf452c94f0ea39d3b9831-58da2d9518a9f028.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:28:27Z"
    - latency: 8.114392ms
      message: 'load-balancer-api-internal: resolved host name af5d20d6e5cdf452c94f0ea39d3b9831-58da2d9518a9f028.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T05:28:27Z"
    - latency: 3.723518ms
      message: 'load-balancer-api-internal: tcp connection to af5d20d6e5cdf452c94f0ea39d3b9831-58da2d9518a9f028.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:27:27Z"
    - latency: 7.641248ms
      message: 'load-balancer-api-internal: resolved host name af5d20d6e5cdf452c94f0ea39d3b9831-58da2d9518a9f028.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T05:27:27Z"
    - latency: 3.323669ms
      message: 'load-balancer-api-internal: tcp connection to af5d20d6e5cdf452c94f0ea39d3b9831-58da2d9518a9f028.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:26:27Z"
    - latency: 6.178745ms
      message: 'load-balancer-api-internal: resolved host name af5d20d6e5cdf452c94f0ea39d3b9831-58da2d9518a9f028.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T05:26:27Z"
    - latency: 4.938896ms
      message: 'load-balancer-api-internal: tcp connection to af5d20d6e5cdf452c94f0ea39d3b9831-58da2d9518a9f028.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:25:27Z"
    - latency: 6.972308ms
      message: 'load-balancer-api-internal: resolved host name af5d20d6e5cdf452c94f0ea39d3b9831-58da2d9518a9f028.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T05:25:27Z"
    - latency: 3.474969ms
      message: 'load-balancer-api-internal: tcp connection to af5d20d6e5cdf452c94f0ea39d3b9831-58da2d9518a9f028.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:24:27Z"
    - latency: 6.130988ms
      message: 'load-balancer-api-internal: resolved host name af5d20d6e5cdf452c94f0ea39d3b9831-58da2d9518a9f028.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T05:24:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T04:52:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-238-to-network-check-target-ip-10-0-132-238
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-238.ec2.internal
      uid: 3b91913f-2be8-4108-8c06-19aa53d7dfc6
    resourceVersion: "67081"
    uid: 6b2b4730-2845-48a2-a223-cc3279d3630a
  spec:
    sourcePod: network-check-source-6f8b768455-ptzr2
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T04:59:27Z"
      message: 'network-check-target-ip-10-0-132-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 990.268µs
      message: 'network-check-target-ip-10-0-132-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:27:27Z"
    - latency: 865.126µs
      message: 'network-check-target-ip-10-0-132-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:26:27Z"
    - latency: 1.036726ms
      message: 'network-check-target-ip-10-0-132-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:25:27Z"
    - latency: 908.184µs
      message: 'network-check-target-ip-10-0-132-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:24:27Z"
    - latency: 1.032344ms
      message: 'network-check-target-ip-10-0-132-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:23:27Z"
    - latency: 1.102887ms
      message: 'network-check-target-ip-10-0-132-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:22:27Z"
    - latency: 757.169µs
      message: 'network-check-target-ip-10-0-132-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:21:27Z"
    - latency: 1.081655ms
      message: 'network-check-target-ip-10-0-132-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:20:27Z"
    - latency: 2.989871ms
      message: 'network-check-target-ip-10-0-132-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:19:27Z"
    - latency: 832.722µs
      message: 'network-check-target-ip-10-0-132-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:18:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T04:52:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-238-to-network-check-target-ip-10-0-133-99
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-238.ec2.internal
      uid: 3b91913f-2be8-4108-8c06-19aa53d7dfc6
    resourceVersion: "67082"
    uid: 4ec5776c-a114-4dfc-be0f-401acd1ba251
  spec:
    sourcePod: network-check-source-6f8b768455-ptzr2
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T04:59:27Z"
      message: 'network-check-target-ip-10-0-133-99: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.474392ms
      message: 'network-check-target-ip-10-0-133-99: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:27:27Z"
    - latency: 2.374678ms
      message: 'network-check-target-ip-10-0-133-99: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:26:27Z"
    - latency: 2.266822ms
      message: 'network-check-target-ip-10-0-133-99: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:25:27Z"
    - latency: 2.42533ms
      message: 'network-check-target-ip-10-0-133-99: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:24:27Z"
    - latency: 2.440764ms
      message: 'network-check-target-ip-10-0-133-99: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:23:27Z"
    - latency: 2.73047ms
      message: 'network-check-target-ip-10-0-133-99: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:22:27Z"
    - latency: 2.168296ms
      message: 'network-check-target-ip-10-0-133-99: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:21:27Z"
    - latency: 2.379631ms
      message: 'network-check-target-ip-10-0-133-99: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:20:27Z"
    - latency: 6.249584ms
      message: 'network-check-target-ip-10-0-133-99: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:19:27Z"
    - latency: 2.770634ms
      message: 'network-check-target-ip-10-0-133-99: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:18:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T04:52:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-238-to-network-check-target-ip-10-0-137-105
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-238.ec2.internal
      uid: 3b91913f-2be8-4108-8c06-19aa53d7dfc6
    resourceVersion: "67083"
    uid: 0cbd6046-d464-43f7-b26f-b44c94695748
  spec:
    sourcePod: network-check-source-6f8b768455-ptzr2
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T04:59:27Z"
      message: 'network-check-target-ip-10-0-137-105: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.621083ms
      message: 'network-check-target-ip-10-0-137-105: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:27:27Z"
    - latency: 2.374516ms
      message: 'network-check-target-ip-10-0-137-105: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:26:27Z"
    - latency: 2.505521ms
      message: 'network-check-target-ip-10-0-137-105: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:25:27Z"
    - latency: 2.284693ms
      message: 'network-check-target-ip-10-0-137-105: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:24:27Z"
    - latency: 2.505061ms
      message: 'network-check-target-ip-10-0-137-105: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:23:27Z"
    - latency: 2.426473ms
      message: 'network-check-target-ip-10-0-137-105: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:22:27Z"
    - latency: 2.529685ms
      message: 'network-check-target-ip-10-0-137-105: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:21:27Z"
    - latency: 2.337447ms
      message: 'network-check-target-ip-10-0-137-105: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:20:27Z"
    - latency: 5.246332ms
      message: 'network-check-target-ip-10-0-137-105: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:19:27Z"
    - latency: 2.778007ms
      message: 'network-check-target-ip-10-0-137-105: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:18:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T04:52:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-238-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-238.ec2.internal
      uid: 3b91913f-2be8-4108-8c06-19aa53d7dfc6
    resourceVersion: "67988"
    uid: 29dc9fd3-be05-4eae-90e9-9ea7a0454953
  spec:
    sourcePod: network-check-source-6f8b768455-ptzr2
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T04:58:27Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.106063ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:28:27Z"
    - latency: 1.954919ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T05:28:27Z"
    - latency: 917.347µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:27:27Z"
    - latency: 1.89866ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T05:27:27Z"
    - latency: 1.01779ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:26:27Z"
    - latency: 1.646334ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T05:26:27Z"
    - latency: 1.3311ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:25:27Z"
    - latency: 1.87036ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T05:25:27Z"
    - latency: 1.525494ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T05:24:27Z"
    - latency: 1.720485ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T05:24:27Z"
kind: List
metadata:
  resourceVersion: ""