apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-13T01:02:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-107-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-107.ec2.internal
      uid: 1c2f9280-2bf8-4202-936e-31e40cf97098
    resourceVersion: "44821"
    uid: 9af20c4b-316f-47cf-acda-bcd3b6a99014
  spec:
    sourcePod: network-check-source-6947749cfc-797xq
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-13T01:09:23Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.140315ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:30:23Z"
    - latency: 1.10568ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:29:23Z"
    - latency: 1.087535ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:28:23Z"
    - latency: 812.025µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:27:23Z"
    - latency: 1.011774ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:26:23Z"
    - latency: 829.578µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:25:23Z"
    - latency: 871.966µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:24:23Z"
    - latency: 1.063124ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:23:23Z"
    - latency: 906.8µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:22:23Z"
    - latency: 1.225847ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:21:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-13T01:02:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-107-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-107.ec2.internal
      uid: 1c2f9280-2bf8-4202-936e-31e40cf97098
    resourceVersion: "46786"
    uid: e367cd59-6f63-4659-8da8-bea1a8c23fe1
  spec:
    sourcePod: network-check-source-6947749cfc-797xq
    targetEndpoint: ad333aab85fc74a22ab50bd4cbacc174-41430da7dfb1a19b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-13T01:08:23Z"
      message: 'load-balancer-api-external: tcp connection to ad333aab85fc74a22ab50bd4cbacc174-41430da7dfb1a19b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.719285ms
      message: 'load-balancer-api-external: tcp connection to ad333aab85fc74a22ab50bd4cbacc174-41430da7dfb1a19b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:32:23Z"
    - latency: 6.710334ms
      message: 'load-balancer-api-external: resolved host name ad333aab85fc74a22ab50bd4cbacc174-41430da7dfb1a19b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T01:32:23Z"
    - latency: 5.778174ms
      message: 'load-balancer-api-external: tcp connection to ad333aab85fc74a22ab50bd4cbacc174-41430da7dfb1a19b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:31:23Z"
    - latency: 7.695339ms
      message: 'load-balancer-api-external: resolved host name ad333aab85fc74a22ab50bd4cbacc174-41430da7dfb1a19b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T01:31:23Z"
    - latency: 6.40865ms
      message: 'load-balancer-api-external: tcp connection to ad333aab85fc74a22ab50bd4cbacc174-41430da7dfb1a19b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:30:23Z"
    - latency: 6.653329ms
      message: 'load-balancer-api-external: resolved host name ad333aab85fc74a22ab50bd4cbacc174-41430da7dfb1a19b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T01:30:23Z"
    - latency: 14.865837ms
      message: 'load-balancer-api-external: tcp connection to ad333aab85fc74a22ab50bd4cbacc174-41430da7dfb1a19b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:29:23Z"
    - latency: 6.297841ms
      message: 'load-balancer-api-external: resolved host name ad333aab85fc74a22ab50bd4cbacc174-41430da7dfb1a19b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T01:29:23Z"
    - latency: 4.17537ms
      message: 'load-balancer-api-external: tcp connection to ad333aab85fc74a22ab50bd4cbacc174-41430da7dfb1a19b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:28:23Z"
    - latency: 5.865633ms
      message: 'load-balancer-api-external: resolved host name ad333aab85fc74a22ab50bd4cbacc174-41430da7dfb1a19b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T01:28:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-13T01:02:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-107-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-107.ec2.internal
      uid: 1c2f9280-2bf8-4202-936e-31e40cf97098
    resourceVersion: "46787"
    uid: 9f1ac0db-60f4-4182-84bf-1974f5ab318a
  spec:
    sourcePod: network-check-source-6947749cfc-797xq
    targetEndpoint: ad333aab85fc74a22ab50bd4cbacc174-41430da7dfb1a19b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-13T01:08:23Z"
      message: 'load-balancer-api-internal: tcp connection to ad333aab85fc74a22ab50bd4cbacc174-41430da7dfb1a19b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.074716ms
      message: 'load-balancer-api-internal: tcp connection to ad333aab85fc74a22ab50bd4cbacc174-41430da7dfb1a19b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:32:23Z"
    - latency: 6.656714ms
      message: 'load-balancer-api-internal: resolved host name ad333aab85fc74a22ab50bd4cbacc174-41430da7dfb1a19b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T01:32:23Z"
    - latency: 5.731806ms
      message: 'load-balancer-api-internal: tcp connection to ad333aab85fc74a22ab50bd4cbacc174-41430da7dfb1a19b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:31:23Z"
    - latency: 7.752558ms
      message: 'load-balancer-api-internal: resolved host name ad333aab85fc74a22ab50bd4cbacc174-41430da7dfb1a19b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T01:31:23Z"
    - latency: 6.431435ms
      message: 'load-balancer-api-internal: tcp connection to ad333aab85fc74a22ab50bd4cbacc174-41430da7dfb1a19b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:30:23Z"
    - latency: 6.802095ms
      message: 'load-balancer-api-internal: resolved host name ad333aab85fc74a22ab50bd4cbacc174-41430da7dfb1a19b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T01:30:23Z"
    - latency: 6.32522ms
      message: 'load-balancer-api-internal: tcp connection to ad333aab85fc74a22ab50bd4cbacc174-41430da7dfb1a19b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:29:23Z"
    - latency: 6.362731ms
      message: 'load-balancer-api-internal: resolved host name ad333aab85fc74a22ab50bd4cbacc174-41430da7dfb1a19b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T01:29:23Z"
    - latency: 4.238842ms
      message: 'load-balancer-api-internal: tcp connection to ad333aab85fc74a22ab50bd4cbacc174-41430da7dfb1a19b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:28:23Z"
    - latency: 5.822157ms
      message: 'load-balancer-api-internal: resolved host name ad333aab85fc74a22ab50bd4cbacc174-41430da7dfb1a19b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T01:28:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-13T01:02:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-107-to-network-check-target-ip-10-0-129-95
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-107.ec2.internal
      uid: 1c2f9280-2bf8-4202-936e-31e40cf97098
    resourceVersion: "44819"
    uid: c016be56-0a07-49d6-94b7-89ad19482422
  spec:
    sourcePod: network-check-source-6947749cfc-797xq
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-13T01:09:23Z"
      message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.45826ms
      message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:30:23Z"
    - latency: 2.493622ms
      message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:29:23Z"
    - latency: 2.149359ms
      message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:28:23Z"
    - latency: 2.598368ms
      message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:27:23Z"
    - latency: 2.362558ms
      message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:26:23Z"
    - latency: 2.884793ms
      message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:25:23Z"
    - latency: 2.325337ms
      message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:24:23Z"
    - latency: 2.330415ms
      message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:23:23Z"
    - latency: 2.148492ms
      message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:22:23Z"
    - latency: 2.320024ms
      message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:21:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-13T01:02:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-107-to-network-check-target-ip-10-0-136-30
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-107.ec2.internal
      uid: 1c2f9280-2bf8-4202-936e-31e40cf97098
    resourceVersion: "44820"
    uid: ece17c0a-6315-409b-8f0f-fd5f39dc02de
  spec:
    sourcePod: network-check-source-6947749cfc-797xq
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-13T01:09:23Z"
      message: 'network-check-target-ip-10-0-136-30: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.50567ms
      message: 'network-check-target-ip-10-0-136-30: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:30:23Z"
    - latency: 2.371504ms
      message: 'network-check-target-ip-10-0-136-30: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:29:23Z"
    - latency: 2.760802ms
      message: 'network-check-target-ip-10-0-136-30: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:28:23Z"
    - latency: 2.234064ms
      message: 'network-check-target-ip-10-0-136-30: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:27:23Z"
    - latency: 2.272873ms
      message: 'network-check-target-ip-10-0-136-30: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:26:23Z"
    - latency: 2.080658ms
      message: 'network-check-target-ip-10-0-136-30: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:25:23Z"
    - latency: 2.00935ms
      message: 'network-check-target-ip-10-0-136-30: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:24:23Z"
    - latency: 2.393441ms
      message: 'network-check-target-ip-10-0-136-30: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:23:23Z"
    - latency: 2.213831ms
      message: 'network-check-target-ip-10-0-136-30: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:22:23Z"
    - latency: 2.093488ms
      message: 'network-check-target-ip-10-0-136-30: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:21:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-13T01:02:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-107-to-network-check-target-ip-10-0-137-107
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-107.ec2.internal
      uid: 1c2f9280-2bf8-4202-936e-31e40cf97098
    resourceVersion: "44818"
    uid: 570449ba-80c2-48f7-beb7-5859a230ba0a
  spec:
    sourcePod: network-check-source-6947749cfc-797xq
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-13T01:09:23Z"
      message: 'network-check-target-ip-10-0-137-107: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.016636ms
      message: 'network-check-target-ip-10-0-137-107: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:30:23Z"
    - latency: 789.184µs
      message: 'network-check-target-ip-10-0-137-107: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:29:23Z"
    - latency: 1.173096ms
      message: 'network-check-target-ip-10-0-137-107: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:28:23Z"
    - latency: 745.584µs
      message: 'network-check-target-ip-10-0-137-107: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:27:23Z"
    - latency: 964.787µs
      message: 'network-check-target-ip-10-0-137-107: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:26:23Z"
    - latency: 1.460049ms
      message: 'network-check-target-ip-10-0-137-107: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:25:23Z"
    - latency: 870.092µs
      message: 'network-check-target-ip-10-0-137-107: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:24:23Z"
    - latency: 1.495518ms
      message: 'network-check-target-ip-10-0-137-107: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:23:23Z"
    - latency: 1.015239ms
      message: 'network-check-target-ip-10-0-137-107: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:22:23Z"
    - latency: 945.723µs
      message: 'network-check-target-ip-10-0-137-107: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:21:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-13T01:02:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-107-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-107.ec2.internal
      uid: 1c2f9280-2bf8-4202-936e-31e40cf97098
    resourceVersion: "46785"
    uid: 2c4c1f8c-3fbe-4169-bde9-c43185d62df6
  spec:
    sourcePod: network-check-source-6947749cfc-797xq
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-13T01:08:23Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.120259ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:32:23Z"
    - latency: 1.752949ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T01:32:23Z"
    - latency: 984.329µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:31:23Z"
    - latency: 2.416967ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T01:31:23Z"
    - latency: 1.522301ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:30:23Z"
    - latency: 1.887319ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T01:30:23Z"
    - latency: 753.315µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:29:23Z"
    - latency: 1.519507ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T01:29:23Z"
    - latency: 909.762µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:28:23Z"
    - latency: 1.887823ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T01:28:23Z"
kind: List
metadata:
  resourceVersion: ""