apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T14:47:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-78-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-78.ec2.internal
      uid: 67584cd8-5ca1-4348-8387-40f411c3f037
    resourceVersion: "48549"
    uid: 6b6c7b0e-1fad-44fd-b878-e6f3f77534cf
  spec:
    sourcePod: network-check-source-869dcfcdcd-6vzg5
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T14:54:58Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.112292ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:15:58Z"
    - latency: 1.063015ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:14:58Z"
    - latency: 779.284µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:13:58Z"
    - latency: 1.142214ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:12:58Z"
    - latency: 1.251038ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:11:58Z"
    - latency: 1.051365ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:10:58Z"
    - latency: 848.629µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:09:58Z"
    - latency: 1.554031ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:08:58Z"
    - latency: 1.468688ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:07:58Z"
    - latency: 839.302µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:06:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T14:47:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-78-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-78.ec2.internal
      uid: 67584cd8-5ca1-4348-8387-40f411c3f037
    resourceVersion: "51082"
    uid: 07631f1a-bd0e-4152-93c3-f9e09044dd9e
  spec:
    sourcePod: network-check-source-869dcfcdcd-6vzg5
    targetEndpoint: a5d63446ba3ba4f15977beae49e0c366-5f342a271cafbd23.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T14:53:58Z"
      message: 'load-balancer-api-external: tcp connection to a5d63446ba3ba4f15977beae49e0c366-5f342a271cafbd23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.891867ms
      message: 'load-balancer-api-external: tcp connection to a5d63446ba3ba4f15977beae49e0c366-5f342a271cafbd23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:17:58Z"
    - latency: 8.279961ms
      message: 'load-balancer-api-external: resolved host name a5d63446ba3ba4f15977beae49e0c366-5f342a271cafbd23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T15:17:58Z"
    - latency: 5.090185ms
      message: 'load-balancer-api-external: tcp connection to a5d63446ba3ba4f15977beae49e0c366-5f342a271cafbd23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:16:58Z"
    - latency: 6.433338ms
      message: 'load-balancer-api-external: resolved host name a5d63446ba3ba4f15977beae49e0c366-5f342a271cafbd23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T15:16:58Z"
    - latency: 5.057788ms
      message: 'load-balancer-api-external: tcp connection to a5d63446ba3ba4f15977beae49e0c366-5f342a271cafbd23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:15:58Z"
    - latency: 6.6687ms
      message: 'load-balancer-api-external: resolved host name a5d63446ba3ba4f15977beae49e0c366-5f342a271cafbd23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T15:15:58Z"
    - latency: 3.753372ms
      message: 'load-balancer-api-external: tcp connection to a5d63446ba3ba4f15977beae49e0c366-5f342a271cafbd23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:14:58Z"
    - latency: 8.404209ms
      message: 'load-balancer-api-external: resolved host name a5d63446ba3ba4f15977beae49e0c366-5f342a271cafbd23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T15:14:58Z"
    - latency: 34.611602ms
      message: 'load-balancer-api-external: tcp connection to a5d63446ba3ba4f15977beae49e0c366-5f342a271cafbd23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:13:58Z"
    - latency: 8.028204ms
      message: 'load-balancer-api-external: resolved host name a5d63446ba3ba4f15977beae49e0c366-5f342a271cafbd23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T15:13:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T14:47:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-78-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-78.ec2.internal
      uid: 67584cd8-5ca1-4348-8387-40f411c3f037
    resourceVersion: "51081"
    uid: 1fa3512e-ffa5-4ad6-a207-42f273ce1247
  spec:
    sourcePod: network-check-source-869dcfcdcd-6vzg5
    targetEndpoint: a5d63446ba3ba4f15977beae49e0c366-5f342a271cafbd23.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T14:53:58Z"
      message: 'load-balancer-api-internal: tcp connection to a5d63446ba3ba4f15977beae49e0c366-5f342a271cafbd23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.863418ms
      message: 'load-balancer-api-internal: tcp connection to a5d63446ba3ba4f15977beae49e0c366-5f342a271cafbd23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:17:58Z"
    - latency: 8.311846ms
      message: 'load-balancer-api-internal: resolved host name a5d63446ba3ba4f15977beae49e0c366-5f342a271cafbd23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T15:17:58Z"
    - latency: 5.109998ms
      message: 'load-balancer-api-internal: tcp connection to a5d63446ba3ba4f15977beae49e0c366-5f342a271cafbd23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:16:58Z"
    - latency: 6.368987ms
      message: 'load-balancer-api-internal: resolved host name a5d63446ba3ba4f15977beae49e0c366-5f342a271cafbd23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T15:16:58Z"
    - latency: 5.019654ms
      message: 'load-balancer-api-internal: tcp connection to a5d63446ba3ba4f15977beae49e0c366-5f342a271cafbd23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:15:58Z"
    - latency: 6.714047ms
      message: 'load-balancer-api-internal: resolved host name a5d63446ba3ba4f15977beae49e0c366-5f342a271cafbd23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T15:15:58Z"
    - latency: 4.123878ms
      message: 'load-balancer-api-internal: tcp connection to a5d63446ba3ba4f15977beae49e0c366-5f342a271cafbd23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:14:58Z"
    - latency: 8.389118ms
      message: 'load-balancer-api-internal: resolved host name a5d63446ba3ba4f15977beae49e0c366-5f342a271cafbd23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T15:14:58Z"
    - latency: 9.593204ms
      message: 'load-balancer-api-internal: tcp connection to a5d63446ba3ba4f15977beae49e0c366-5f342a271cafbd23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:13:58Z"
    - latency: 8.070995ms
      message: 'load-balancer-api-internal: resolved host name a5d63446ba3ba4f15977beae49e0c366-5f342a271cafbd23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T15:13:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T14:47:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-78-to-network-check-target-ip-10-0-136-241
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-78.ec2.internal
      uid: 67584cd8-5ca1-4348-8387-40f411c3f037
    resourceVersion: "48547"
    uid: f1cca86d-1667-438a-9ac7-2e2b7cb8a473
  spec:
    sourcePod: network-check-source-869dcfcdcd-6vzg5
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T14:54:58Z"
      message: 'network-check-target-ip-10-0-136-241: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.807968ms
      message: 'network-check-target-ip-10-0-136-241: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:15:58Z"
    - latency: 1.673257ms
      message: 'network-check-target-ip-10-0-136-241: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:14:58Z"
    - latency: 1.597292ms
      message: 'network-check-target-ip-10-0-136-241: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:13:58Z"
    - latency: 1.835298ms
      message: 'network-check-target-ip-10-0-136-241: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:12:58Z"
    - latency: 1.742213ms
      message: 'network-check-target-ip-10-0-136-241: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:11:58Z"
    - latency: 1.834806ms
      message: 'network-check-target-ip-10-0-136-241: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:10:58Z"
    - latency: 1.665687ms
      message: 'network-check-target-ip-10-0-136-241: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:09:58Z"
    - latency: 1.701061ms
      message: 'network-check-target-ip-10-0-136-241: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:08:58Z"
    - latency: 2.097004ms
      message: 'network-check-target-ip-10-0-136-241: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:07:58Z"
    - latency: 1.609851ms
      message: 'network-check-target-ip-10-0-136-241: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:06:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T14:47:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-78-to-network-check-target-ip-10-0-139-143
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-78.ec2.internal
      uid: 67584cd8-5ca1-4348-8387-40f411c3f037
    resourceVersion: "48548"
    uid: 6a0cd97a-0417-463c-9ecf-1e7b1565821e
  spec:
    sourcePod: network-check-source-869dcfcdcd-6vzg5
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T14:54:58Z"
      message: 'network-check-target-ip-10-0-139-143: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.399881ms
      message: 'network-check-target-ip-10-0-139-143: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:15:58Z"
    - latency: 2.253138ms
      message: 'network-check-target-ip-10-0-139-143: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:14:58Z"
    - latency: 2.121221ms
      message: 'network-check-target-ip-10-0-139-143: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:13:58Z"
    - latency: 2.293675ms
      message: 'network-check-target-ip-10-0-139-143: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:12:58Z"
    - latency: 2.06552ms
      message: 'network-check-target-ip-10-0-139-143: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:11:58Z"
    - latency: 2.201683ms
      message: 'network-check-target-ip-10-0-139-143: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:10:58Z"
    - latency: 2.159522ms
      message: 'network-check-target-ip-10-0-139-143: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:09:58Z"
    - latency: 1.936088ms
      message: 'network-check-target-ip-10-0-139-143: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:08:58Z"
    - latency: 2.398773ms
      message: 'network-check-target-ip-10-0-139-143: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:07:58Z"
    - latency: 2.377092ms
      message: 'network-check-target-ip-10-0-139-143: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:06:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T14:47:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-78-to-network-check-target-ip-10-0-142-78
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-78.ec2.internal
      uid: 67584cd8-5ca1-4348-8387-40f411c3f037
    resourceVersion: "48546"
    uid: 23a7e076-397f-40d3-8cd1-fe8430d1bc6a
  spec:
    sourcePod: network-check-source-869dcfcdcd-6vzg5
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T14:54:58Z"
      message: 'network-check-target-ip-10-0-142-78: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 868.335µs
      message: 'network-check-target-ip-10-0-142-78: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:15:58Z"
    - latency: 916.984µs
      message: 'network-check-target-ip-10-0-142-78: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:14:58Z"
    - latency: 1.336148ms
      message: 'network-check-target-ip-10-0-142-78: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:13:58Z"
    - latency: 924.496µs
      message: 'network-check-target-ip-10-0-142-78: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:12:58Z"
    - latency: 845.657µs
      message: 'network-check-target-ip-10-0-142-78: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:11:58Z"
    - latency: 860.747µs
      message: 'network-check-target-ip-10-0-142-78: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:10:58Z"
    - latency: 1.093816ms
      message: 'network-check-target-ip-10-0-142-78: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:09:58Z"
    - latency: 760.067µs
      message: 'network-check-target-ip-10-0-142-78: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:08:58Z"
    - latency: 990.067µs
      message: 'network-check-target-ip-10-0-142-78: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:07:58Z"
    - latency: 789.046µs
      message: 'network-check-target-ip-10-0-142-78: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:06:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T14:47:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-78-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-78.ec2.internal
      uid: 67584cd8-5ca1-4348-8387-40f411c3f037
    resourceVersion: "51079"
    uid: 28a6dff3-b045-4253-b509-174cb69ba7ed
  spec:
    sourcePod: network-check-source-869dcfcdcd-6vzg5
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T14:53:58Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 834.293µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:17:58Z"
    - latency: 1.806398ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T15:17:58Z"
    - latency: 873.471µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:16:58Z"
    - latency: 1.609059ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T15:16:58Z"
    - latency: 1.096064ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:15:58Z"
    - latency: 1.740883ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T15:15:58Z"
    - latency: 798.465µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:14:58Z"
    - latency: 1.649208ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T15:14:58Z"
    - latency: 1.142919ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:13:58Z"
    - latency: 1.425093ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T15:13:58Z"
kind: List
metadata:
  resourceVersion: ""