apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T19:08:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-171-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-171.ec2.internal
      uid: 96fc5b2b-a711-4892-8eae-80a878f1e8e0
    resourceVersion: "74707"
    uid: 6cc4ac05-6580-4c4c-8556-1cd2e532d92b
  spec:
    sourcePod: network-check-source-7d88cb55d8-ght27
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T19:15:22Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.218453ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:57:22Z"
    - latency: 1.035061ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:56:22Z"
    - latency: 1.177116ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:55:22Z"
    - latency: 1.035672ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:54:22Z"
    - latency: 1.191836ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:53:22Z"
    - latency: 1.319951ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:52:22Z"
    - latency: 1.263431ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:51:22Z"
    - latency: 1.112818ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:50:22Z"
    - latency: 941.563µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:49:22Z"
    - latency: 1.275847ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:48:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T19:08:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-171-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-171.ec2.internal
      uid: 96fc5b2b-a711-4892-8eae-80a878f1e8e0
    resourceVersion: "72576"
    uid: b3c7f6d2-3b2c-4c4a-8fa4-bfda34dd617b
  spec:
    sourcePod: network-check-source-7d88cb55d8-ght27
    targetEndpoint: a82669798d5934033bcdc3cd78de0236-cf195a13caca6ff9.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T19:14:22Z"
      message: 'load-balancer-api-external: tcp connection to a82669798d5934033bcdc3cd78de0236-cf195a13caca6ff9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.34776ms
      message: 'load-balancer-api-external: tcp connection to a82669798d5934033bcdc3cd78de0236-cf195a13caca6ff9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:56:22Z"
    - latency: 7.055855ms
      message: 'load-balancer-api-external: resolved host name a82669798d5934033bcdc3cd78de0236-cf195a13caca6ff9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T19:56:22Z"
    - latency: 5.819029ms
      message: 'load-balancer-api-external: tcp connection to a82669798d5934033bcdc3cd78de0236-cf195a13caca6ff9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:55:22Z"
    - latency: 7.433654ms
      message: 'load-balancer-api-external: resolved host name a82669798d5934033bcdc3cd78de0236-cf195a13caca6ff9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T19:55:22Z"
    - latency: 4.451309ms
      message: 'load-balancer-api-external: tcp connection to a82669798d5934033bcdc3cd78de0236-cf195a13caca6ff9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:54:22Z"
    - latency: 6.869304ms
      message: 'load-balancer-api-external: resolved host name a82669798d5934033bcdc3cd78de0236-cf195a13caca6ff9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T19:54:22Z"
    - latency: 6.049624ms
      message: 'load-balancer-api-external: tcp connection to a82669798d5934033bcdc3cd78de0236-cf195a13caca6ff9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:53:22Z"
    - latency: 7.473501ms
      message: 'load-balancer-api-external: resolved host name a82669798d5934033bcdc3cd78de0236-cf195a13caca6ff9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T19:53:22Z"
    - latency: 5.420584ms
      message: 'load-balancer-api-external: tcp connection to a82669798d5934033bcdc3cd78de0236-cf195a13caca6ff9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:52:22Z"
    - latency: 7.652167ms
      message: 'load-balancer-api-external: resolved host name a82669798d5934033bcdc3cd78de0236-cf195a13caca6ff9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T19:52:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T19:08:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-171-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-171.ec2.internal
      uid: 96fc5b2b-a711-4892-8eae-80a878f1e8e0
    resourceVersion: "72575"
    uid: eec3c7a1-c463-445f-bc67-99268c165a01
  spec:
    sourcePod: network-check-source-7d88cb55d8-ght27
    targetEndpoint: a82669798d5934033bcdc3cd78de0236-cf195a13caca6ff9.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T19:14:22Z"
      message: 'load-balancer-api-internal: tcp connection to a82669798d5934033bcdc3cd78de0236-cf195a13caca6ff9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.266226ms
      message: 'load-balancer-api-internal: tcp connection to a82669798d5934033bcdc3cd78de0236-cf195a13caca6ff9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:56:22Z"
    - latency: 7.169138ms
      message: 'load-balancer-api-internal: resolved host name a82669798d5934033bcdc3cd78de0236-cf195a13caca6ff9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T19:56:22Z"
    - latency: 6.630515ms
      message: 'load-balancer-api-internal: tcp connection to a82669798d5934033bcdc3cd78de0236-cf195a13caca6ff9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:55:22Z"
    - latency: 7.400343ms
      message: 'load-balancer-api-internal: resolved host name a82669798d5934033bcdc3cd78de0236-cf195a13caca6ff9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T19:55:22Z"
    - latency: 4.327722ms
      message: 'load-balancer-api-internal: tcp connection to a82669798d5934033bcdc3cd78de0236-cf195a13caca6ff9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:54:22Z"
    - latency: 6.920187ms
      message: 'load-balancer-api-internal: resolved host name a82669798d5934033bcdc3cd78de0236-cf195a13caca6ff9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T19:54:22Z"
    - latency: 5.623203ms
      message: 'load-balancer-api-internal: tcp connection to a82669798d5934033bcdc3cd78de0236-cf195a13caca6ff9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:53:22Z"
    - latency: 7.437764ms
      message: 'load-balancer-api-internal: resolved host name a82669798d5934033bcdc3cd78de0236-cf195a13caca6ff9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T19:53:22Z"
    - latency: 5.45557ms
      message: 'load-balancer-api-internal: tcp connection to a82669798d5934033bcdc3cd78de0236-cf195a13caca6ff9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:52:22Z"
    - latency: 7.563054ms
      message: 'load-balancer-api-internal: resolved host name a82669798d5934033bcdc3cd78de0236-cf195a13caca6ff9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T19:52:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T19:08:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-171-to-network-check-target-ip-10-0-132-61
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-171.ec2.internal
      uid: 96fc5b2b-a711-4892-8eae-80a878f1e8e0
    resourceVersion: "74705"
    uid: 5f33e197-4aa3-4696-87ba-295894cc6a87
  spec:
    sourcePod: network-check-source-7d88cb55d8-ght27
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T19:15:22Z"
      message: 'network-check-target-ip-10-0-132-61: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.431175ms
      message: 'network-check-target-ip-10-0-132-61: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:57:22Z"
    - latency: 2.584985ms
      message: 'network-check-target-ip-10-0-132-61: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:56:22Z"
    - latency: 2.343997ms
      message: 'network-check-target-ip-10-0-132-61: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:55:22Z"
    - latency: 2.668816ms
      message: 'network-check-target-ip-10-0-132-61: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:54:22Z"
    - latency: 2.635534ms
      message: 'network-check-target-ip-10-0-132-61: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:53:22Z"
    - latency: 2.344332ms
      message: 'network-check-target-ip-10-0-132-61: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:52:22Z"
    - latency: 2.454752ms
      message: 'network-check-target-ip-10-0-132-61: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:51:22Z"
    - latency: 2.320668ms
      message: 'network-check-target-ip-10-0-132-61: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:50:22Z"
    - latency: 2.155462ms
      message: 'network-check-target-ip-10-0-132-61: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:49:22Z"
    - latency: 2.265087ms
      message: 'network-check-target-ip-10-0-132-61: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:48:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T19:08:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-171-to-network-check-target-ip-10-0-140-57
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-171.ec2.internal
      uid: 96fc5b2b-a711-4892-8eae-80a878f1e8e0
    resourceVersion: "74706"
    uid: 85368830-8850-49f6-a0ed-665fae1b3429
  spec:
    sourcePod: network-check-source-7d88cb55d8-ght27
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T19:15:22Z"
      message: 'network-check-target-ip-10-0-140-57: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.525106ms
      message: 'network-check-target-ip-10-0-140-57: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:57:22Z"
    - latency: 2.673189ms
      message: 'network-check-target-ip-10-0-140-57: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:56:22Z"
    - latency: 2.136944ms
      message: 'network-check-target-ip-10-0-140-57: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:55:22Z"
    - latency: 2.01006ms
      message: 'network-check-target-ip-10-0-140-57: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:54:22Z"
    - latency: 2.596361ms
      message: 'network-check-target-ip-10-0-140-57: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:53:22Z"
    - latency: 2.917785ms
      message: 'network-check-target-ip-10-0-140-57: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:52:22Z"
    - latency: 2.452227ms
      message: 'network-check-target-ip-10-0-140-57: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:51:22Z"
    - latency: 2.440233ms
      message: 'network-check-target-ip-10-0-140-57: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:50:22Z"
    - latency: 2.52808ms
      message: 'network-check-target-ip-10-0-140-57: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:49:22Z"
    - latency: 2.639964ms
      message: 'network-check-target-ip-10-0-140-57: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:48:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T19:08:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-171-to-network-check-target-ip-10-0-142-171
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-171.ec2.internal
      uid: 96fc5b2b-a711-4892-8eae-80a878f1e8e0
    resourceVersion: "74704"
    uid: 9cd7cc4e-418a-418a-af8e-4277491e8231
  spec:
    sourcePod: network-check-source-7d88cb55d8-ght27
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T19:15:22Z"
      message: 'network-check-target-ip-10-0-142-171: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.164309ms
      message: 'network-check-target-ip-10-0-142-171: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:57:22Z"
    - latency: 1.132723ms
      message: 'network-check-target-ip-10-0-142-171: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:56:22Z"
    - latency: 1.034623ms
      message: 'network-check-target-ip-10-0-142-171: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:55:22Z"
    - latency: 1.117982ms
      message: 'network-check-target-ip-10-0-142-171: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:54:22Z"
    - latency: 1.052971ms
      message: 'network-check-target-ip-10-0-142-171: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:53:22Z"
    - latency: 1.617911ms
      message: 'network-check-target-ip-10-0-142-171: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:52:22Z"
    - latency: 1.146979ms
      message: 'network-check-target-ip-10-0-142-171: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:51:22Z"
    - latency: 1.459239ms
      message: 'network-check-target-ip-10-0-142-171: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:50:22Z"
    - latency: 1.276788ms
      message: 'network-check-target-ip-10-0-142-171: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:49:22Z"
    - latency: 1.212294ms
      message: 'network-check-target-ip-10-0-142-171: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:48:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T19:08:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-171-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-171.ec2.internal
      uid: 96fc5b2b-a711-4892-8eae-80a878f1e8e0
    resourceVersion: "72572"
    uid: e927b1c9-7ac2-4eed-a93a-64d4a3d2d860
  spec:
    sourcePod: network-check-source-7d88cb55d8-ght27
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T19:14:22Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 897.777µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:56:22Z"
    - latency: 1.956895ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T19:56:22Z"
    - latency: 1.006995ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:55:22Z"
    - latency: 1.871402ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T19:55:22Z"
    - latency: 1.271319ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:54:22Z"
    - latency: 1.993876ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T19:54:22Z"
    - latency: 1.475656ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:53:22Z"
    - latency: 1.889842ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T19:53:22Z"
    - latency: 1.366229ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T19:52:22Z"
    - latency: 1.941264ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T19:52:22Z"
kind: List
metadata:
  resourceVersion: ""