apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T14:52:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-143-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-143.ec2.internal
      uid: b96380dd-0dad-42ed-8aed-80ccca5aa2ad
    resourceVersion: "79800"
    uid: 8e1515e7-14c9-4c83-924d-677d681f6b3b
  spec:
    sourcePod: network-check-source-65bdbbff45-6hfhk
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T14:59:36Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.258621ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:48:36Z"
    - latency: 1.28924ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:47:36Z"
    - latency: 905.144µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:46:36Z"
    - latency: 1.164456ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:45:36Z"
    - latency: 979.556µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:44:36Z"
    - latency: 1.09871ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:43:36Z"
    - latency: 1.317483ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:42:36Z"
    - latency: 944.415µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:41:36Z"
    - latency: 1.696485ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:40:36Z"
    - latency: 1.175524ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:39:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T14:52:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-143-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-143.ec2.internal
      uid: b96380dd-0dad-42ed-8aed-80ccca5aa2ad
    resourceVersion: "78040"
    uid: 22cdf412-814a-4ead-af22-b70102e5d622
  spec:
    sourcePod: network-check-source-65bdbbff45-6hfhk
    targetEndpoint: a71a7cfc761d94332b961f5b95338c7c-7d45063f29537bda.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T14:58:36Z"
      message: 'load-balancer-api-external: tcp connection to a71a7cfc761d94332b961f5b95338c7c-7d45063f29537bda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.780121ms
      message: 'load-balancer-api-external: tcp connection to a71a7cfc761d94332b961f5b95338c7c-7d45063f29537bda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:46:36Z"
    - latency: 8.887814ms
      message: 'load-balancer-api-external: resolved host name a71a7cfc761d94332b961f5b95338c7c-7d45063f29537bda.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T15:46:36Z"
    - latency: 5.371824ms
      message: 'load-balancer-api-external: tcp connection to a71a7cfc761d94332b961f5b95338c7c-7d45063f29537bda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:45:36Z"
    - latency: 7.810099ms
      message: 'load-balancer-api-external: resolved host name a71a7cfc761d94332b961f5b95338c7c-7d45063f29537bda.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T15:45:36Z"
    - latency: 5.460942ms
      message: 'load-balancer-api-external: tcp connection to a71a7cfc761d94332b961f5b95338c7c-7d45063f29537bda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:44:36Z"
    - latency: 8.268972ms
      message: 'load-balancer-api-external: resolved host name a71a7cfc761d94332b961f5b95338c7c-7d45063f29537bda.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T15:44:36Z"
    - latency: 5.021441ms
      message: 'load-balancer-api-external: tcp connection to a71a7cfc761d94332b961f5b95338c7c-7d45063f29537bda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:43:36Z"
    - latency: 8.582249ms
      message: 'load-balancer-api-external: resolved host name a71a7cfc761d94332b961f5b95338c7c-7d45063f29537bda.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T15:43:36Z"
    - latency: 4.636394ms
      message: 'load-balancer-api-external: tcp connection to a71a7cfc761d94332b961f5b95338c7c-7d45063f29537bda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:42:36Z"
    - latency: 8.314768ms
      message: 'load-balancer-api-external: resolved host name a71a7cfc761d94332b961f5b95338c7c-7d45063f29537bda.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T15:42:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T14:52:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-143-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-143.ec2.internal
      uid: b96380dd-0dad-42ed-8aed-80ccca5aa2ad
    resourceVersion: "78041"
    uid: 2d16b35f-3946-485f-a98c-19f8d940777c
  spec:
    sourcePod: network-check-source-65bdbbff45-6hfhk
    targetEndpoint: a71a7cfc761d94332b961f5b95338c7c-7d45063f29537bda.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T14:58:36Z"
      message: 'load-balancer-api-internal: tcp connection to a71a7cfc761d94332b961f5b95338c7c-7d45063f29537bda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.855116ms
      message: 'load-balancer-api-internal: tcp connection to a71a7cfc761d94332b961f5b95338c7c-7d45063f29537bda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:46:36Z"
    - latency: 8.788659ms
      message: 'load-balancer-api-internal: resolved host name a71a7cfc761d94332b961f5b95338c7c-7d45063f29537bda.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T15:46:36Z"
    - latency: 5.202033ms
      message: 'load-balancer-api-internal: tcp connection to a71a7cfc761d94332b961f5b95338c7c-7d45063f29537bda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:45:36Z"
    - latency: 7.830428ms
      message: 'load-balancer-api-internal: resolved host name a71a7cfc761d94332b961f5b95338c7c-7d45063f29537bda.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T15:45:36Z"
    - latency: 5.522977ms
      message: 'load-balancer-api-internal: tcp connection to a71a7cfc761d94332b961f5b95338c7c-7d45063f29537bda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:44:36Z"
    - latency: 8.1769ms
      message: 'load-balancer-api-internal: resolved host name a71a7cfc761d94332b961f5b95338c7c-7d45063f29537bda.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T15:44:36Z"
    - latency: 4.908287ms
      message: 'load-balancer-api-internal: tcp connection to a71a7cfc761d94332b961f5b95338c7c-7d45063f29537bda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:43:36Z"
    - latency: 8.479473ms
      message: 'load-balancer-api-internal: resolved host name a71a7cfc761d94332b961f5b95338c7c-7d45063f29537bda.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T15:43:36Z"
    - latency: 4.647666ms
      message: 'load-balancer-api-internal: tcp connection to a71a7cfc761d94332b961f5b95338c7c-7d45063f29537bda.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:42:36Z"
    - latency: 8.086691ms
      message: 'load-balancer-api-internal: resolved host name a71a7cfc761d94332b961f5b95338c7c-7d45063f29537bda.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T15:42:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T14:52:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-143-to-network-check-target-ip-10-0-133-32
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-143.ec2.internal
      uid: b96380dd-0dad-42ed-8aed-80ccca5aa2ad
    resourceVersion: "79798"
    uid: 3fd53b64-dbe7-4e9d-8343-62a7d550298c
  spec:
    sourcePod: network-check-source-65bdbbff45-6hfhk
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T14:59:36Z"
      message: 'network-check-target-ip-10-0-133-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.268988ms
      message: 'network-check-target-ip-10-0-133-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:48:36Z"
    - latency: 2.436994ms
      message: 'network-check-target-ip-10-0-133-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:47:36Z"
    - latency: 2.218181ms
      message: 'network-check-target-ip-10-0-133-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:46:36Z"
    - latency: 2.651019ms
      message: 'network-check-target-ip-10-0-133-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:45:36Z"
    - latency: 2.423717ms
      message: 'network-check-target-ip-10-0-133-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:44:36Z"
    - latency: 2.291063ms
      message: 'network-check-target-ip-10-0-133-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:43:36Z"
    - latency: 2.598172ms
      message: 'network-check-target-ip-10-0-133-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:42:36Z"
    - latency: 2.820099ms
      message: 'network-check-target-ip-10-0-133-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:41:36Z"
    - latency: 2.38375ms
      message: 'network-check-target-ip-10-0-133-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:40:36Z"
    - latency: 2.960827ms
      message: 'network-check-target-ip-10-0-133-32: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:39:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T14:52:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-143-to-network-check-target-ip-10-0-135-143
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-143.ec2.internal
      uid: b96380dd-0dad-42ed-8aed-80ccca5aa2ad
    resourceVersion: "79797"
    uid: fbbd26e4-e35b-4c2c-8642-83180c147501
  spec:
    sourcePod: network-check-source-65bdbbff45-6hfhk
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T14:59:36Z"
      message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 966.629µs
      message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:48:36Z"
    - latency: 1.443487ms
      message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:47:36Z"
    - latency: 985.699µs
      message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:46:36Z"
    - latency: 1.279397ms
      message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:45:36Z"
    - latency: 1.427844ms
      message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:44:36Z"
    - latency: 1.112105ms
      message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:43:36Z"
    - latency: 1.676581ms
      message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:42:36Z"
    - latency: 1.354226ms
      message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:41:36Z"
    - latency: 1.029386ms
      message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:40:36Z"
    - latency: 972.351µs
      message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:39:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T14:52:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-143-to-network-check-target-ip-10-0-137-96
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-143.ec2.internal
      uid: b96380dd-0dad-42ed-8aed-80ccca5aa2ad
    resourceVersion: "79799"
    uid: 82af8a85-92fb-4df3-ae50-965731ad19e9
  spec:
    sourcePod: network-check-source-65bdbbff45-6hfhk
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T14:59:36Z"
      message: 'network-check-target-ip-10-0-137-96: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.898579ms
      message: 'network-check-target-ip-10-0-137-96: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:48:36Z"
    - latency: 2.691738ms
      message: 'network-check-target-ip-10-0-137-96: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:47:36Z"
    - latency: 2.66908ms
      message: 'network-check-target-ip-10-0-137-96: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:46:36Z"
    - latency: 2.527706ms
      message: 'network-check-target-ip-10-0-137-96: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:45:36Z"
    - latency: 2.626183ms
      message: 'network-check-target-ip-10-0-137-96: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:44:36Z"
    - latency: 2.29847ms
      message: 'network-check-target-ip-10-0-137-96: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:43:36Z"
    - latency: 3.447422ms
      message: 'network-check-target-ip-10-0-137-96: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:42:36Z"
    - latency: 2.297465ms
      message: 'network-check-target-ip-10-0-137-96: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:41:36Z"
    - latency: 2.643428ms
      message: 'network-check-target-ip-10-0-137-96: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:40:36Z"
    - latency: 2.291409ms
      message: 'network-check-target-ip-10-0-137-96: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:39:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T14:52:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-143-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-143.ec2.internal
      uid: b96380dd-0dad-42ed-8aed-80ccca5aa2ad
    resourceVersion: "78038"
    uid: 3dcaf8a5-fef7-4076-be45-2b994296ee50
  spec:
    sourcePod: network-check-source-65bdbbff45-6hfhk
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T14:58:36Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 827.031µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:46:36Z"
    - latency: 2.608472ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T15:46:36Z"
    - latency: 1.121057ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:45:36Z"
    - latency: 2.04251ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T15:45:36Z"
    - latency: 1.045926ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:44:36Z"
    - latency: 2.657791ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T15:44:36Z"
    - latency: 986.018µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:43:36Z"
    - latency: 2.066689ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T15:43:36Z"
    - latency: 870.241µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:42:36Z"
    - latency: 1.937521ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T15:42:36Z"
kind: List
metadata:
  resourceVersion: ""