apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T14:24:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-70-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-70.ec2.internal
      uid: 3f07ccea-3342-479b-a0d0-a8fe3d605d2f
    resourceVersion: "51473"
    uid: 894df0a9-2c08-4818-9a98-0e8cd0680884
  spec:
    sourcePod: network-check-source-869dcfcdcd-p6ch2
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T14:31:06Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 713.666µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T14:59:06Z"
    - latency: 1.093088ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T14:58:06Z"
    - latency: 1.061182ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T14:57:06Z"
    - latency: 883.772µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T14:56:06Z"
    - latency: 1.082476ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T14:55:06Z"
    - latency: 1.128231ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T14:54:06Z"
    - latency: 1.080875ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T14:53:06Z"
    - latency: 1.135994ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T14:52:06Z"
    - latency: 1.00015ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T14:51:06Z"
    - latency: 1.120019ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T14:50:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T14:24:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-70-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-70.ec2.internal
      uid: 3f07ccea-3342-479b-a0d0-a8fe3d605d2f
    resourceVersion: "52471"
    uid: abab07d1-f158-40f5-844f-5b00f44f8fb2
  spec:
    sourcePod: network-check-source-869dcfcdcd-p6ch2
    targetEndpoint: a530e7b0c4b24482f96eebe6235ba057-7a035369c52ca0e7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T14:30:06Z"
      message: 'load-balancer-api-external: tcp connection to a530e7b0c4b24482f96eebe6235ba057-7a035369c52ca0e7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.484208ms
      message: 'load-balancer-api-external: tcp connection to a530e7b0c4b24482f96eebe6235ba057-7a035369c52ca0e7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:00:06Z"
    - latency: 6.767616ms
      message: 'load-balancer-api-external: resolved host name a530e7b0c4b24482f96eebe6235ba057-7a035369c52ca0e7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T15:00:06Z"
    - latency: 3.523932ms
      message: 'load-balancer-api-external: tcp connection to a530e7b0c4b24482f96eebe6235ba057-7a035369c52ca0e7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T14:59:06Z"
    - latency: 6.577318ms
      message: 'load-balancer-api-external: resolved host name a530e7b0c4b24482f96eebe6235ba057-7a035369c52ca0e7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T14:59:06Z"
    - latency: 4.893522ms
      message: 'load-balancer-api-external: tcp connection to a530e7b0c4b24482f96eebe6235ba057-7a035369c52ca0e7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T14:58:06Z"
    - latency: 10.104579ms
      message: 'load-balancer-api-external: resolved host name a530e7b0c4b24482f96eebe6235ba057-7a035369c52ca0e7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T14:58:06Z"
    - latency: 4.363027ms
      message: 'load-balancer-api-external: tcp connection to a530e7b0c4b24482f96eebe6235ba057-7a035369c52ca0e7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T14:57:06Z"
    - latency: 8.805625ms
      message: 'load-balancer-api-external: resolved host name a530e7b0c4b24482f96eebe6235ba057-7a035369c52ca0e7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T14:57:06Z"
    - latency: 4.07275ms
      message: 'load-balancer-api-external: tcp connection to a530e7b0c4b24482f96eebe6235ba057-7a035369c52ca0e7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T14:56:06Z"
    - latency: 7.800601ms
      message: 'load-balancer-api-external: resolved host name a530e7b0c4b24482f96eebe6235ba057-7a035369c52ca0e7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T14:56:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T14:24:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-70-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-70.ec2.internal
      uid: 3f07ccea-3342-479b-a0d0-a8fe3d605d2f
    resourceVersion: "52470"
    uid: 34cc1c0b-335f-47e2-b263-476d51b001e7
  spec:
    sourcePod: network-check-source-869dcfcdcd-p6ch2
    targetEndpoint: a530e7b0c4b24482f96eebe6235ba057-7a035369c52ca0e7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T14:30:06Z"
      message: 'load-balancer-api-internal: tcp connection to a530e7b0c4b24482f96eebe6235ba057-7a035369c52ca0e7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.462413ms
      message: 'load-balancer-api-internal: tcp connection to a530e7b0c4b24482f96eebe6235ba057-7a035369c52ca0e7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:00:06Z"
    - latency: 6.855775ms
      message: 'load-balancer-api-internal: resolved host name a530e7b0c4b24482f96eebe6235ba057-7a035369c52ca0e7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T15:00:06Z"
    - latency: 3.473092ms
      message: 'load-balancer-api-internal: tcp connection to a530e7b0c4b24482f96eebe6235ba057-7a035369c52ca0e7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T14:59:06Z"
    - latency: 6.638642ms
      message: 'load-balancer-api-internal: resolved host name a530e7b0c4b24482f96eebe6235ba057-7a035369c52ca0e7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T14:59:06Z"
    - latency: 4.890032ms
      message: 'load-balancer-api-internal: tcp connection to a530e7b0c4b24482f96eebe6235ba057-7a035369c52ca0e7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T14:58:06Z"
    - latency: 10.178342ms
      message: 'load-balancer-api-internal: resolved host name a530e7b0c4b24482f96eebe6235ba057-7a035369c52ca0e7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T14:58:06Z"
    - latency: 4.508908ms
      message: 'load-balancer-api-internal: tcp connection to a530e7b0c4b24482f96eebe6235ba057-7a035369c52ca0e7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T14:57:06Z"
    - latency: 8.774141ms
      message: 'load-balancer-api-internal: resolved host name a530e7b0c4b24482f96eebe6235ba057-7a035369c52ca0e7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T14:57:06Z"
    - latency: 5.104791ms
      message: 'load-balancer-api-internal: tcp connection to a530e7b0c4b24482f96eebe6235ba057-7a035369c52ca0e7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T14:56:06Z"
    - latency: 7.90818ms
      message: 'load-balancer-api-internal: resolved host name a530e7b0c4b24482f96eebe6235ba057-7a035369c52ca0e7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T14:56:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T14:24:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-70-to-network-check-target-ip-10-0-131-188
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-70.ec2.internal
      uid: 3f07ccea-3342-479b-a0d0-a8fe3d605d2f
    resourceVersion: "51471"
    uid: 96a68c8f-ca5b-4472-8402-6e651f661197
  spec:
    sourcePod: network-check-source-869dcfcdcd-p6ch2
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T14:31:06Z"
      message: 'network-check-target-ip-10-0-131-188: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.931191ms
      message: 'network-check-target-ip-10-0-131-188: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T14:59:06Z"
    - latency: 2.452172ms
      message: 'network-check-target-ip-10-0-131-188: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T14:58:06Z"
    - latency: 2.172064ms
      message: 'network-check-target-ip-10-0-131-188: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T14:57:06Z"
    - latency: 2.200735ms
      message: 'network-check-target-ip-10-0-131-188: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T14:56:06Z"
    - latency: 2.214593ms
      message: 'network-check-target-ip-10-0-131-188: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T14:55:06Z"
    - latency: 2.182964ms
      message: 'network-check-target-ip-10-0-131-188: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T14:54:06Z"
    - latency: 2.001487ms
      message: 'network-check-target-ip-10-0-131-188: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T14:53:06Z"
    - latency: 2.15886ms
      message: 'network-check-target-ip-10-0-131-188: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T14:52:06Z"
    - latency: 2.425163ms
      message: 'network-check-target-ip-10-0-131-188: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T14:51:06Z"
    - latency: 2.555027ms
      message: 'network-check-target-ip-10-0-131-188: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T14:50:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T14:24:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-70-to-network-check-target-ip-10-0-138-70
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-70.ec2.internal
      uid: 3f07ccea-3342-479b-a0d0-a8fe3d605d2f
    resourceVersion: "51470"
    uid: 7e325193-8208-4dd1-b04c-27f8871dced0
  spec:
    sourcePod: network-check-source-869dcfcdcd-p6ch2
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T14:31:06Z"
      message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 783.416µs
      message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T14:59:06Z"
    - latency: 1.114953ms
      message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T14:58:06Z"
    - latency: 1.010017ms
      message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T14:57:06Z"
    - latency: 1.044309ms
      message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T14:56:06Z"
    - latency: 1.123097ms
      message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T14:55:06Z"
    - latency: 1.55837ms
      message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T14:54:06Z"
    - latency: 1.186312ms
      message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T14:53:06Z"
    - latency: 855.146µs
      message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T14:52:06Z"
    - latency: 1.426989ms
      message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T14:51:06Z"
    - latency: 1.474283ms
      message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T14:50:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T14:24:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-70-to-network-check-target-ip-10-0-140-7
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-70.ec2.internal
      uid: 3f07ccea-3342-479b-a0d0-a8fe3d605d2f
    resourceVersion: "51472"
    uid: 70f9ae28-fa6c-42e4-9d77-1381478e3660
  spec:
    sourcePod: network-check-source-869dcfcdcd-p6ch2
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T14:31:06Z"
      message: 'network-check-target-ip-10-0-140-7: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.643109ms
      message: 'network-check-target-ip-10-0-140-7: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T14:59:06Z"
    - latency: 1.916111ms
      message: 'network-check-target-ip-10-0-140-7: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T14:58:06Z"
    - latency: 2.003152ms
      message: 'network-check-target-ip-10-0-140-7: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T14:57:06Z"
    - latency: 1.884939ms
      message: 'network-check-target-ip-10-0-140-7: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T14:56:06Z"
    - latency: 2.250667ms
      message: 'network-check-target-ip-10-0-140-7: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T14:55:06Z"
    - latency: 1.774996ms
      message: 'network-check-target-ip-10-0-140-7: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T14:54:06Z"
    - latency: 2.056169ms
      message: 'network-check-target-ip-10-0-140-7: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T14:53:06Z"
    - latency: 1.971277ms
      message: 'network-check-target-ip-10-0-140-7: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T14:52:06Z"
    - latency: 1.842736ms
      message: 'network-check-target-ip-10-0-140-7: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T14:51:06Z"
    - latency: 1.935116ms
      message: 'network-check-target-ip-10-0-140-7: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T14:50:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T14:24:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-70-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-70.ec2.internal
      uid: 3f07ccea-3342-479b-a0d0-a8fe3d605d2f
    resourceVersion: "52468"
    uid: 7b9a69e0-a129-4b41-95a5-f6cf61eb0181
  spec:
    sourcePod: network-check-source-869dcfcdcd-p6ch2
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T14:30:06Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 953.048µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T15:00:06Z"
    - latency: 2.011564ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T15:00:06Z"
    - latency: 944.854µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T14:59:06Z"
    - latency: 1.785967ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T14:59:06Z"
    - latency: 1.168135ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T14:58:06Z"
    - latency: 1.866751ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T14:58:06Z"
    - latency: 970.747µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T14:57:06Z"
    - latency: 2.005043ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T14:57:06Z"
    - latency: 920.294µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T14:56:06Z"
    - latency: 1.607678ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T14:56:06Z"
kind: List
metadata:
  resourceVersion: ""