apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T01:37:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-11-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-11.ec2.internal
      uid: 91bef136-aec9-4822-95af-3386e4a27b8b
    resourceVersion: "69631"
    uid: b84507f0-bac3-4123-9f02-d309d58076aa
  spec:
    sourcePod: network-check-source-6f8b768455-t6qgc
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T01:44:14Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.159864ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:12:14Z"
    - latency: 973.631µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:11:14Z"
    - latency: 1.124242ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:10:14Z"
    - latency: 1.204878ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:09:14Z"
    - latency: 1.270732ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:08:14Z"
    - latency: 1.139527ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:07:14Z"
    - latency: 1.218074ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:06:14Z"
    - latency: 1.089264ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:05:14Z"
    - latency: 1.272923ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:04:14Z"
    - latency: 924.949µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:03:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T01:37:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-11-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-11.ec2.internal
      uid: 91bef136-aec9-4822-95af-3386e4a27b8b
    resourceVersion: "70680"
    uid: e8b0bb4d-cd76-40bb-ae95-59c1fceb12ce
  spec:
    sourcePod: network-check-source-6f8b768455-t6qgc
    targetEndpoint: aa81927db11584f4d9eae30719ecaeb8-5bd0e601d164d4cc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T01:43:14Z"
      message: 'load-balancer-api-external: tcp connection to aa81927db11584f4d9eae30719ecaeb8-5bd0e601d164d4cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.763805ms
      message: 'load-balancer-api-external: tcp connection to aa81927db11584f4d9eae30719ecaeb8-5bd0e601d164d4cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:13:14Z"
    - latency: 8.671073ms
      message: 'load-balancer-api-external: resolved host name aa81927db11584f4d9eae30719ecaeb8-5bd0e601d164d4cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T02:13:14Z"
    - latency: 3.799638ms
      message: 'load-balancer-api-external: tcp connection to aa81927db11584f4d9eae30719ecaeb8-5bd0e601d164d4cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:12:14Z"
    - latency: 9.513378ms
      message: 'load-balancer-api-external: resolved host name aa81927db11584f4d9eae30719ecaeb8-5bd0e601d164d4cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T02:12:14Z"
    - latency: 5.224931ms
      message: 'load-balancer-api-external: tcp connection to aa81927db11584f4d9eae30719ecaeb8-5bd0e601d164d4cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:11:14Z"
    - latency: 9.752019ms
      message: 'load-balancer-api-external: resolved host name aa81927db11584f4d9eae30719ecaeb8-5bd0e601d164d4cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T02:11:14Z"
    - latency: 4.008079ms
      message: 'load-balancer-api-external: tcp connection to aa81927db11584f4d9eae30719ecaeb8-5bd0e601d164d4cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:10:14Z"
    - latency: 8.063563ms
      message: 'load-balancer-api-external: resolved host name aa81927db11584f4d9eae30719ecaeb8-5bd0e601d164d4cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T02:10:14Z"
    - latency: 5.637764ms
      message: 'load-balancer-api-external: tcp connection to aa81927db11584f4d9eae30719ecaeb8-5bd0e601d164d4cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:09:14Z"
    - latency: 8.534272ms
      message: 'load-balancer-api-external: resolved host name aa81927db11584f4d9eae30719ecaeb8-5bd0e601d164d4cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T02:09:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T01:37:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-11-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-11.ec2.internal
      uid: 91bef136-aec9-4822-95af-3386e4a27b8b
    resourceVersion: "70679"
    uid: 67fb2fb3-5eb0-42bd-81d8-cb2eecaa7718
  spec:
    sourcePod: network-check-source-6f8b768455-t6qgc
    targetEndpoint: aa81927db11584f4d9eae30719ecaeb8-5bd0e601d164d4cc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T01:43:14Z"
      message: 'load-balancer-api-internal: tcp connection to aa81927db11584f4d9eae30719ecaeb8-5bd0e601d164d4cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.738353ms
      message: 'load-balancer-api-internal: tcp connection to aa81927db11584f4d9eae30719ecaeb8-5bd0e601d164d4cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:13:14Z"
    - latency: 8.744503ms
      message: 'load-balancer-api-internal: resolved host name aa81927db11584f4d9eae30719ecaeb8-5bd0e601d164d4cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T02:13:14Z"
    - latency: 4.652263ms
      message: 'load-balancer-api-internal: tcp connection to aa81927db11584f4d9eae30719ecaeb8-5bd0e601d164d4cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:12:14Z"
    - latency: 9.479973ms
      message: 'load-balancer-api-internal: resolved host name aa81927db11584f4d9eae30719ecaeb8-5bd0e601d164d4cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T02:12:14Z"
    - latency: 5.376418ms
      message: 'load-balancer-api-internal: tcp connection to aa81927db11584f4d9eae30719ecaeb8-5bd0e601d164d4cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:11:14Z"
    - latency: 9.822237ms
      message: 'load-balancer-api-internal: resolved host name aa81927db11584f4d9eae30719ecaeb8-5bd0e601d164d4cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T02:11:14Z"
    - latency: 4.435077ms
      message: 'load-balancer-api-internal: tcp connection to aa81927db11584f4d9eae30719ecaeb8-5bd0e601d164d4cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:10:14Z"
    - latency: 8.174111ms
      message: 'load-balancer-api-internal: resolved host name aa81927db11584f4d9eae30719ecaeb8-5bd0e601d164d4cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T02:10:14Z"
    - latency: 5.613683ms
      message: 'load-balancer-api-internal: tcp connection to aa81927db11584f4d9eae30719ecaeb8-5bd0e601d164d4cc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:09:14Z"
    - latency: 8.632068ms
      message: 'load-balancer-api-internal: resolved host name aa81927db11584f4d9eae30719ecaeb8-5bd0e601d164d4cc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T02:09:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T01:37:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-11-to-network-check-target-ip-10-0-130-123
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-11.ec2.internal
      uid: 91bef136-aec9-4822-95af-3386e4a27b8b
    resourceVersion: "69629"
    uid: b7aaaa55-d98f-4f9c-a136-eb96bdff461a
  spec:
    sourcePod: network-check-source-6f8b768455-t6qgc
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T01:44:14Z"
      message: 'network-check-target-ip-10-0-130-123: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.209785ms
      message: 'network-check-target-ip-10-0-130-123: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:12:14Z"
    - latency: 2.102606ms
      message: 'network-check-target-ip-10-0-130-123: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:11:14Z"
    - latency: 2.261562ms
      message: 'network-check-target-ip-10-0-130-123: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:10:14Z"
    - latency: 2.016666ms
      message: 'network-check-target-ip-10-0-130-123: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:09:14Z"
    - latency: 2.221947ms
      message: 'network-check-target-ip-10-0-130-123: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:08:14Z"
    - latency: 2.364442ms
      message: 'network-check-target-ip-10-0-130-123: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:07:14Z"
    - latency: 2.597558ms
      message: 'network-check-target-ip-10-0-130-123: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:06:14Z"
    - latency: 2.11282ms
      message: 'network-check-target-ip-10-0-130-123: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:05:14Z"
    - latency: 2.24456ms
      message: 'network-check-target-ip-10-0-130-123: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:04:14Z"
    - latency: 2.261919ms
      message: 'network-check-target-ip-10-0-130-123: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:03:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T01:37:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-11-to-network-check-target-ip-10-0-132-11
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-11.ec2.internal
      uid: 91bef136-aec9-4822-95af-3386e4a27b8b
    resourceVersion: "69628"
    uid: 92d5f3ee-08ce-427e-aa32-758083b85033
  spec:
    sourcePod: network-check-source-6f8b768455-t6qgc
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T01:44:14Z"
      message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 912.682µs
      message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:12:14Z"
    - latency: 961.807µs
      message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:11:14Z"
    - latency: 966.311µs
      message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:10:14Z"
    - latency: 981.562µs
      message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:09:14Z"
    - latency: 838.997µs
      message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:08:14Z"
    - latency: 1.007862ms
      message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:07:14Z"
    - latency: 975.764µs
      message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:06:14Z"
    - latency: 980.017µs
      message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:05:14Z"
    - latency: 998.178µs
      message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:04:14Z"
    - latency: 964.686µs
      message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:03:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T01:37:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-11-to-network-check-target-ip-10-0-132-205
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-11.ec2.internal
      uid: 91bef136-aec9-4822-95af-3386e4a27b8b
    resourceVersion: "69630"
    uid: fe3afeac-c473-4e16-b591-a2d2ef57d34d
  spec:
    sourcePod: network-check-source-6f8b768455-t6qgc
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T01:44:14Z"
      message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.050301ms
      message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:12:14Z"
    - latency: 2.018208ms
      message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:11:14Z"
    - latency: 1.681528ms
      message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:10:14Z"
    - latency: 2.118137ms
      message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:09:14Z"
    - latency: 2.038792ms
      message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:08:14Z"
    - latency: 2.070456ms
      message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:07:14Z"
    - latency: 2.180842ms
      message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:06:14Z"
    - latency: 2.010688ms
      message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:05:14Z"
    - latency: 2.119244ms
      message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:04:14Z"
    - latency: 2.077598ms
      message: 'network-check-target-ip-10-0-132-205: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:03:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T01:37:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-11-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-11.ec2.internal
      uid: 91bef136-aec9-4822-95af-3386e4a27b8b
    resourceVersion: "70678"
    uid: e7243c01-1258-44bb-8034-baec3acd6fc3
  spec:
    sourcePod: network-check-source-6f8b768455-t6qgc
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T01:43:14Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.139601ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:13:14Z"
    - latency: 1.921088ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T02:13:14Z"
    - latency: 1.004137ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:12:14Z"
    - latency: 1.776391ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T02:12:14Z"
    - latency: 890.827µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:11:14Z"
    - latency: 1.649551ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T02:11:14Z"
    - latency: 851.489µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:10:14Z"
    - latency: 1.802961ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T02:10:14Z"
    - latency: 1.011876ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T02:09:14Z"
    - latency: 1.67604ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T02:09:14Z"
kind: List
metadata:
  resourceVersion: ""