apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T17:02:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-82-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-82.ec2.internal
      uid: 5b70706f-8b29-4ebe-bb53-0811865dda98
    resourceVersion: "28864"
    uid: 90348acf-e673-4268-bcde-a3584fa4fc11
  spec:
    sourcePod: network-check-source-dbd9cf844-pw6n7
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T17:09:18Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.029052ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:16:18Z"
    - latency: 941.309µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:15:18Z"
    - latency: 1.064927ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:14:18Z"
    - latency: 1.014227ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:13:18Z"
    - latency: 917.868µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:12:18Z"
    - latency: 1.10896ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:11:18Z"
    - latency: 1.330345ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:10:18Z"
    - latency: 1.483136ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:09:18Z"
    - latency: 921.144µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:08:18Z"
    - latency: 897.252µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:07:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T17:02:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-82-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-82.ec2.internal
      uid: 5b70706f-8b29-4ebe-bb53-0811865dda98
    resourceVersion: "27876"
    uid: 233547a0-33d2-4bea-8ba1-aed8b5e6549c
  spec:
    sourcePod: network-check-source-dbd9cf844-pw6n7
    targetEndpoint: ae57dda0ba72a4591b639acc1b5b5ec7-417da74ab5cff389.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T17:08:18Z"
      message: 'load-balancer-api-external: tcp connection to ae57dda0ba72a4591b639acc1b5b5ec7-417da74ab5cff389.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.964874ms
      message: 'load-balancer-api-external: tcp connection to ae57dda0ba72a4591b639acc1b5b5ec7-417da74ab5cff389.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:14:18Z"
    - latency: 8.444792ms
      message: 'load-balancer-api-external: resolved host name ae57dda0ba72a4591b639acc1b5b5ec7-417da74ab5cff389.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T17:14:18Z"
    - latency: 5.176127ms
      message: 'load-balancer-api-external: tcp connection to ae57dda0ba72a4591b639acc1b5b5ec7-417da74ab5cff389.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:13:18Z"
    - latency: 8.347289ms
      message: 'load-balancer-api-external: resolved host name ae57dda0ba72a4591b639acc1b5b5ec7-417da74ab5cff389.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T17:13:18Z"
    - latency: 5.061627ms
      message: 'load-balancer-api-external: tcp connection to ae57dda0ba72a4591b639acc1b5b5ec7-417da74ab5cff389.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:12:18Z"
    - latency: 8.856975ms
      message: 'load-balancer-api-external: resolved host name ae57dda0ba72a4591b639acc1b5b5ec7-417da74ab5cff389.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T17:12:18Z"
    - latency: 4.614811ms
      message: 'load-balancer-api-external: tcp connection to ae57dda0ba72a4591b639acc1b5b5ec7-417da74ab5cff389.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:11:18Z"
    - latency: 10.362859ms
      message: 'load-balancer-api-external: resolved host name ae57dda0ba72a4591b639acc1b5b5ec7-417da74ab5cff389.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T17:11:18Z"
    - latency: 6.202131ms
      message: 'load-balancer-api-external: tcp connection to ae57dda0ba72a4591b639acc1b5b5ec7-417da74ab5cff389.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:10:18Z"
    - latency: 8.324414ms
      message: 'load-balancer-api-external: resolved host name ae57dda0ba72a4591b639acc1b5b5ec7-417da74ab5cff389.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T17:10:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T17:02:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-82-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-82.ec2.internal
      uid: 5b70706f-8b29-4ebe-bb53-0811865dda98
    resourceVersion: "27875"
    uid: bad3402f-c726-4246-8cc2-60493fac9609
  spec:
    sourcePod: network-check-source-dbd9cf844-pw6n7
    targetEndpoint: ae57dda0ba72a4591b639acc1b5b5ec7-417da74ab5cff389.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T17:08:18Z"
      message: 'load-balancer-api-internal: tcp connection to ae57dda0ba72a4591b639acc1b5b5ec7-417da74ab5cff389.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.826319ms
      message: 'load-balancer-api-internal: tcp connection to ae57dda0ba72a4591b639acc1b5b5ec7-417da74ab5cff389.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:14:18Z"
    - latency: 8.331698ms
      message: 'load-balancer-api-internal: resolved host name ae57dda0ba72a4591b639acc1b5b5ec7-417da74ab5cff389.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T17:14:18Z"
    - latency: 5.110298ms
      message: 'load-balancer-api-internal: tcp connection to ae57dda0ba72a4591b639acc1b5b5ec7-417da74ab5cff389.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:13:18Z"
    - latency: 8.320637ms
      message: 'load-balancer-api-internal: resolved host name ae57dda0ba72a4591b639acc1b5b5ec7-417da74ab5cff389.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T17:13:18Z"
    - latency: 4.159155ms
      message: 'load-balancer-api-internal: tcp connection to ae57dda0ba72a4591b639acc1b5b5ec7-417da74ab5cff389.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:12:18Z"
    - latency: 8.779701ms
      message: 'load-balancer-api-internal: resolved host name ae57dda0ba72a4591b639acc1b5b5ec7-417da74ab5cff389.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T17:12:18Z"
    - latency: 4.559087ms
      message: 'load-balancer-api-internal: tcp connection to ae57dda0ba72a4591b639acc1b5b5ec7-417da74ab5cff389.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:11:18Z"
    - latency: 10.26936ms
      message: 'load-balancer-api-internal: resolved host name ae57dda0ba72a4591b639acc1b5b5ec7-417da74ab5cff389.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T17:11:18Z"
    - latency: 6.336042ms
      message: 'load-balancer-api-internal: tcp connection to ae57dda0ba72a4591b639acc1b5b5ec7-417da74ab5cff389.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:10:18Z"
    - latency: 8.238024ms
      message: 'load-balancer-api-internal: resolved host name ae57dda0ba72a4591b639acc1b5b5ec7-417da74ab5cff389.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T17:10:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T17:02:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-82-to-network-check-target-ip-10-0-130-110
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-82.ec2.internal
      uid: 5b70706f-8b29-4ebe-bb53-0811865dda98
    resourceVersion: "28865"
    uid: 22a8e96c-1768-4aaa-b04d-2625fdade4e8
  spec:
    sourcePod: network-check-source-dbd9cf844-pw6n7
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T17:09:18Z"
      message: 'network-check-target-ip-10-0-130-110: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.551706ms
      message: 'network-check-target-ip-10-0-130-110: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:16:18Z"
    - latency: 2.364115ms
      message: 'network-check-target-ip-10-0-130-110: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:15:18Z"
    - latency: 2.412463ms
      message: 'network-check-target-ip-10-0-130-110: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:14:18Z"
    - latency: 2.521739ms
      message: 'network-check-target-ip-10-0-130-110: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:13:18Z"
    - latency: 2.141164ms
      message: 'network-check-target-ip-10-0-130-110: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:12:18Z"
    - latency: 2.444532ms
      message: 'network-check-target-ip-10-0-130-110: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:11:18Z"
    - latency: 2.504848ms
      message: 'network-check-target-ip-10-0-130-110: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:10:18Z"
    - latency: 2.47025ms
      message: 'network-check-target-ip-10-0-130-110: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:09:18Z"
    - latency: 2.472454ms
      message: 'network-check-target-ip-10-0-130-110: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:08:18Z"
    - latency: 2.407427ms
      message: 'network-check-target-ip-10-0-130-110: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:07:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T17:02:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-82-to-network-check-target-ip-10-0-132-142
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-82.ec2.internal
      uid: 5b70706f-8b29-4ebe-bb53-0811865dda98
    resourceVersion: "28863"
    uid: fb9fc1a2-3d4f-4b36-b3fa-9cc648b3f69d
  spec:
    sourcePod: network-check-source-dbd9cf844-pw6n7
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T17:09:18Z"
      message: 'network-check-target-ip-10-0-132-142: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.22858ms
      message: 'network-check-target-ip-10-0-132-142: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:16:18Z"
    - latency: 2.304257ms
      message: 'network-check-target-ip-10-0-132-142: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:15:18Z"
    - latency: 2.442275ms
      message: 'network-check-target-ip-10-0-132-142: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:14:18Z"
    - latency: 2.736488ms
      message: 'network-check-target-ip-10-0-132-142: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:13:18Z"
    - latency: 2.293298ms
      message: 'network-check-target-ip-10-0-132-142: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:12:18Z"
    - latency: 2.679709ms
      message: 'network-check-target-ip-10-0-132-142: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:11:18Z"
    - latency: 2.540544ms
      message: 'network-check-target-ip-10-0-132-142: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:10:18Z"
    - latency: 2.487348ms
      message: 'network-check-target-ip-10-0-132-142: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:09:18Z"
    - latency: 2.434119ms
      message: 'network-check-target-ip-10-0-132-142: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:08:18Z"
    - latency: 2.528665ms
      message: 'network-check-target-ip-10-0-132-142: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:07:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T17:02:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-82-to-network-check-target-ip-10-0-133-82
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-82.ec2.internal
      uid: 5b70706f-8b29-4ebe-bb53-0811865dda98
    resourceVersion: "28862"
    uid: fed8ba76-5ed6-44ac-ba20-5b12bd34e024
  spec:
    sourcePod: network-check-source-dbd9cf844-pw6n7
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T17:09:18Z"
      message: 'network-check-target-ip-10-0-133-82: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.21442ms
      message: 'network-check-target-ip-10-0-133-82: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:16:18Z"
    - latency: 935.142µs
      message: 'network-check-target-ip-10-0-133-82: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:15:18Z"
    - latency: 985.449µs
      message: 'network-check-target-ip-10-0-133-82: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:14:18Z"
    - latency: 945.118µs
      message: 'network-check-target-ip-10-0-133-82: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:13:18Z"
    - latency: 939.624µs
      message: 'network-check-target-ip-10-0-133-82: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:12:18Z"
    - latency: 1.083355ms
      message: 'network-check-target-ip-10-0-133-82: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:11:18Z"
    - latency: 823.731µs
      message: 'network-check-target-ip-10-0-133-82: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:10:18Z"
    - latency: 1.686469ms
      message: 'network-check-target-ip-10-0-133-82: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:09:18Z"
    - latency: 1.013566ms
      message: 'network-check-target-ip-10-0-133-82: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:08:18Z"
    - latency: 943.877µs
      message: 'network-check-target-ip-10-0-133-82: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:07:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T17:02:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-82-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-82.ec2.internal
      uid: 5b70706f-8b29-4ebe-bb53-0811865dda98
    resourceVersion: "27874"
    uid: cbe52e87-95be-4ce6-ada5-5c40968aa64d
  spec:
    sourcePod: network-check-source-dbd9cf844-pw6n7
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T17:08:18Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.118532ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:14:18Z"
    - latency: 1.841941ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T17:14:18Z"
    - latency: 997.23µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:13:18Z"
    - latency: 1.865979ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T17:13:18Z"
    - latency: 891.306µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:12:18Z"
    - latency: 1.755712ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T17:12:18Z"
    - latency: 889.989µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:11:18Z"
    - latency: 1.562513ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T17:11:18Z"
    - latency: 939.101µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T17:10:18Z"
    - latency: 1.646799ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T17:10:18Z"
kind: List
metadata:
  resourceVersion: ""