apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T17:05:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-238-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-238.ec2.internal
      uid: d6189d79-314b-4e99-91aa-9526bf8de063
    resourceVersion: "60380"
    uid: af491b4f-692c-472a-b88b-9b73a02c386c
  spec:
    sourcePod: network-check-source-869dcfcdcd-2f6bt
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T17:12:47Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.025345ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:47:47Z"
    - latency: 831.172µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:46:47Z"
    - latency: 1.192064ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:45:47Z"
    - latency: 928.19µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:44:47Z"
    - latency: 1.021157ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:43:47Z"
    - latency: 996.092µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:42:47Z"
    - latency: 1.178057ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:41:47Z"
    - latency: 947.6µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:40:47Z"
    - latency: 1.077899ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:39:47Z"
    - latency: 930.48µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:38:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T17:05:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-238-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-238.ec2.internal
      uid: d6189d79-314b-4e99-91aa-9526bf8de063
    resourceVersion: "60382"
    uid: dd0c8846-6821-4cb5-b46f-f93a1bf913f5
  spec:
    sourcePod: network-check-source-869dcfcdcd-2f6bt
    targetEndpoint: a83934e53b24f4146a07e30a49e15d03-3e70af1eef129046.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T17:11:47Z"
      message: 'load-balancer-api-external: tcp connection to a83934e53b24f4146a07e30a49e15d03-3e70af1eef129046.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.784457ms
      message: 'load-balancer-api-external: tcp connection to a83934e53b24f4146a07e30a49e15d03-3e70af1eef129046.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:47:47Z"
    - latency: 6.825078ms
      message: 'load-balancer-api-external: resolved host name a83934e53b24f4146a07e30a49e15d03-3e70af1eef129046.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T17:47:47Z"
    - latency: 5.266475ms
      message: 'load-balancer-api-external: tcp connection to a83934e53b24f4146a07e30a49e15d03-3e70af1eef129046.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:46:47Z"
    - latency: 6.474206ms
      message: 'load-balancer-api-external: resolved host name a83934e53b24f4146a07e30a49e15d03-3e70af1eef129046.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T17:46:47Z"
    - latency: 4.213457ms
      message: 'load-balancer-api-external: tcp connection to a83934e53b24f4146a07e30a49e15d03-3e70af1eef129046.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:45:47Z"
    - latency: 6.936631ms
      message: 'load-balancer-api-external: resolved host name a83934e53b24f4146a07e30a49e15d03-3e70af1eef129046.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T17:45:47Z"
    - latency: 3.862871ms
      message: 'load-balancer-api-external: tcp connection to a83934e53b24f4146a07e30a49e15d03-3e70af1eef129046.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:44:47Z"
    - latency: 7.383026ms
      message: 'load-balancer-api-external: resolved host name a83934e53b24f4146a07e30a49e15d03-3e70af1eef129046.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T17:44:47Z"
    - latency: 5.851705ms
      message: 'load-balancer-api-external: tcp connection to a83934e53b24f4146a07e30a49e15d03-3e70af1eef129046.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:43:47Z"
    - latency: 6.638745ms
      message: 'load-balancer-api-external: resolved host name a83934e53b24f4146a07e30a49e15d03-3e70af1eef129046.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T17:43:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T17:05:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-238-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-238.ec2.internal
      uid: d6189d79-314b-4e99-91aa-9526bf8de063
    resourceVersion: "60381"
    uid: 1e751e93-38ef-47bf-b679-c22588f33f4f
  spec:
    sourcePod: network-check-source-869dcfcdcd-2f6bt
    targetEndpoint: a83934e53b24f4146a07e30a49e15d03-3e70af1eef129046.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T17:11:47Z"
      message: 'load-balancer-api-internal: tcp connection to a83934e53b24f4146a07e30a49e15d03-3e70af1eef129046.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.787502ms
      message: 'load-balancer-api-internal: tcp connection to a83934e53b24f4146a07e30a49e15d03-3e70af1eef129046.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:47:47Z"
    - latency: 6.926774ms
      message: 'load-balancer-api-internal: resolved host name a83934e53b24f4146a07e30a49e15d03-3e70af1eef129046.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T17:47:47Z"
    - latency: 5.250017ms
      message: 'load-balancer-api-internal: tcp connection to a83934e53b24f4146a07e30a49e15d03-3e70af1eef129046.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:46:47Z"
    - latency: 6.362272ms
      message: 'load-balancer-api-internal: resolved host name a83934e53b24f4146a07e30a49e15d03-3e70af1eef129046.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T17:46:47Z"
    - latency: 4.217653ms
      message: 'load-balancer-api-internal: tcp connection to a83934e53b24f4146a07e30a49e15d03-3e70af1eef129046.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:45:47Z"
    - latency: 6.99589ms
      message: 'load-balancer-api-internal: resolved host name a83934e53b24f4146a07e30a49e15d03-3e70af1eef129046.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T17:45:47Z"
    - latency: 3.856618ms
      message: 'load-balancer-api-internal: tcp connection to a83934e53b24f4146a07e30a49e15d03-3e70af1eef129046.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:44:47Z"
    - latency: 7.475998ms
      message: 'load-balancer-api-internal: resolved host name a83934e53b24f4146a07e30a49e15d03-3e70af1eef129046.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T17:44:47Z"
    - latency: 5.822147ms
      message: 'load-balancer-api-internal: tcp connection to a83934e53b24f4146a07e30a49e15d03-3e70af1eef129046.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:43:47Z"
    - latency: 6.702351ms
      message: 'load-balancer-api-internal: resolved host name a83934e53b24f4146a07e30a49e15d03-3e70af1eef129046.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T17:43:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T17:05:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-238-to-network-check-target-ip-10-0-133-238
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-238.ec2.internal
      uid: d6189d79-314b-4e99-91aa-9526bf8de063
    resourceVersion: "60377"
    uid: 9869a435-f906-4cde-88bc-6e4139c5066b
  spec:
    sourcePod: network-check-source-869dcfcdcd-2f6bt
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T17:12:47Z"
      message: 'network-check-target-ip-10-0-133-238: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.336224ms
      message: 'network-check-target-ip-10-0-133-238: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:47:47Z"
    - latency: 1.072236ms
      message: 'network-check-target-ip-10-0-133-238: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:46:47Z"
    - latency: 1.357027ms
      message: 'network-check-target-ip-10-0-133-238: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:45:47Z"
    - latency: 1.033129ms
      message: 'network-check-target-ip-10-0-133-238: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:44:47Z"
    - latency: 949.457µs
      message: 'network-check-target-ip-10-0-133-238: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:43:47Z"
    - latency: 779.541µs
      message: 'network-check-target-ip-10-0-133-238: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:42:47Z"
    - latency: 936.892µs
      message: 'network-check-target-ip-10-0-133-238: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:41:47Z"
    - latency: 1.146326ms
      message: 'network-check-target-ip-10-0-133-238: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:40:47Z"
    - latency: 1.263752ms
      message: 'network-check-target-ip-10-0-133-238: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:39:47Z"
    - latency: 852.905µs
      message: 'network-check-target-ip-10-0-133-238: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:38:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T17:05:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-238-to-network-check-target-ip-10-0-139-89
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-238.ec2.internal
      uid: d6189d79-314b-4e99-91aa-9526bf8de063
    resourceVersion: "60378"
    uid: 8cf2e6de-ac83-4389-92b2-63498d68168a
  spec:
    sourcePod: network-check-source-869dcfcdcd-2f6bt
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T17:12:47Z"
      message: 'network-check-target-ip-10-0-139-89: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.376404ms
      message: 'network-check-target-ip-10-0-139-89: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:47:47Z"
    - latency: 2.039053ms
      message: 'network-check-target-ip-10-0-139-89: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:46:47Z"
    - latency: 2.066164ms
      message: 'network-check-target-ip-10-0-139-89: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:45:47Z"
    - latency: 2.171389ms
      message: 'network-check-target-ip-10-0-139-89: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:44:47Z"
    - latency: 2.363794ms
      message: 'network-check-target-ip-10-0-139-89: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:43:47Z"
    - latency: 1.98456ms
      message: 'network-check-target-ip-10-0-139-89: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:42:47Z"
    - latency: 2.244834ms
      message: 'network-check-target-ip-10-0-139-89: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:41:47Z"
    - latency: 2.286436ms
      message: 'network-check-target-ip-10-0-139-89: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:40:47Z"
    - latency: 2.043787ms
      message: 'network-check-target-ip-10-0-139-89: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:39:47Z"
    - latency: 2.237935ms
      message: 'network-check-target-ip-10-0-139-89: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:38:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T17:05:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-238-to-network-check-target-ip-10-0-141-94
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-238.ec2.internal
      uid: d6189d79-314b-4e99-91aa-9526bf8de063
    resourceVersion: "60376"
    uid: 64e73ed7-aab5-486c-82fc-926f84417583
  spec:
    sourcePod: network-check-source-869dcfcdcd-2f6bt
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T17:12:47Z"
      message: 'network-check-target-ip-10-0-141-94: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.075683ms
      message: 'network-check-target-ip-10-0-141-94: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:47:47Z"
    - latency: 1.878878ms
      message: 'network-check-target-ip-10-0-141-94: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:46:47Z"
    - latency: 1.875283ms
      message: 'network-check-target-ip-10-0-141-94: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:45:47Z"
    - latency: 1.885135ms
      message: 'network-check-target-ip-10-0-141-94: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:44:47Z"
    - latency: 1.78052ms
      message: 'network-check-target-ip-10-0-141-94: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:43:47Z"
    - latency: 2.011158ms
      message: 'network-check-target-ip-10-0-141-94: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:42:47Z"
    - latency: 1.857112ms
      message: 'network-check-target-ip-10-0-141-94: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:41:47Z"
    - latency: 2.027159ms
      message: 'network-check-target-ip-10-0-141-94: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:40:47Z"
    - latency: 1.830904ms
      message: 'network-check-target-ip-10-0-141-94: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:39:47Z"
    - latency: 2.02573ms
      message: 'network-check-target-ip-10-0-141-94: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:38:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T17:05:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-238-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-238.ec2.internal
      uid: d6189d79-314b-4e99-91aa-9526bf8de063
    resourceVersion: "60379"
    uid: d3614399-e47e-4aaf-9e8b-0cdb010356d1
  spec:
    sourcePod: network-check-source-869dcfcdcd-2f6bt
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T17:11:47Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 891.746µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:47:47Z"
    - latency: 2.145284ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T17:47:47Z"
    - latency: 840.449µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:46:47Z"
    - latency: 1.948491ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T17:46:47Z"
    - latency: 1.016928ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:45:47Z"
    - latency: 2.076834ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T17:45:47Z"
    - latency: 985.555µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:44:47Z"
    - latency: 1.736649ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T17:44:47Z"
    - latency: 821.992µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T17:43:47Z"
    - latency: 1.652962ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T17:43:47Z"
kind: List
metadata:
  resourceVersion: ""