apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T21:56:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-79-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-79.ec2.internal
      uid: 4e3b2529-5947-44c3-bbd8-5300c9cd397a
    resourceVersion: "97373"
    uid: 01bc4f4a-2950-45a3-aebe-da611966acbb
  spec:
    sourcePod: network-check-source-7cbc45fddc-2ddwm
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T22:03:07Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.008608ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:34:07Z"
    - latency: 934.16µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:33:07Z"
    - latency: 893.239µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:32:07Z"
    - latency: 1.064429ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:31:07Z"
    - latency: 1.050042ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:30:07Z"
    - latency: 1.243805ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:29:07Z"
    - latency: 850.118µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:28:07Z"
    - latency: 728.782µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:27:07Z"
    - latency: 937.673µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:26:07Z"
    - latency: 1.124767ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:25:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T21:56:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-79-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-79.ec2.internal
      uid: 4e3b2529-5947-44c3-bbd8-5300c9cd397a
    resourceVersion: "96031"
    uid: cd1f1416-dc4f-4e8b-8c4b-f892f0c9ed56
  spec:
    sourcePod: network-check-source-7cbc45fddc-2ddwm
    targetEndpoint: abc95519c67f9460189748464d737b7a-a75d8cad7bdd6449.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T22:02:07Z"
      message: 'load-balancer-api-external: tcp connection to abc95519c67f9460189748464d737b7a-a75d8cad7bdd6449.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.218562ms
      message: 'load-balancer-api-external: tcp connection to abc95519c67f9460189748464d737b7a-a75d8cad7bdd6449.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:32:07Z"
    - latency: 6.778301ms
      message: 'load-balancer-api-external: resolved host name abc95519c67f9460189748464d737b7a-a75d8cad7bdd6449.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T23:32:07Z"
    - latency: 4.696962ms
      message: 'load-balancer-api-external: tcp connection to abc95519c67f9460189748464d737b7a-a75d8cad7bdd6449.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:31:07Z"
    - latency: 8.582404ms
      message: 'load-balancer-api-external: resolved host name abc95519c67f9460189748464d737b7a-a75d8cad7bdd6449.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T23:31:07Z"
    - latency: 4.900274ms
      message: 'load-balancer-api-external: tcp connection to abc95519c67f9460189748464d737b7a-a75d8cad7bdd6449.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:30:07Z"
    - latency: 8.759451ms
      message: 'load-balancer-api-external: resolved host name abc95519c67f9460189748464d737b7a-a75d8cad7bdd6449.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T23:30:07Z"
    - latency: 5.232313ms
      message: 'load-balancer-api-external: tcp connection to abc95519c67f9460189748464d737b7a-a75d8cad7bdd6449.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:29:07Z"
    - latency: 8.647032ms
      message: 'load-balancer-api-external: resolved host name abc95519c67f9460189748464d737b7a-a75d8cad7bdd6449.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T23:29:07Z"
    - latency: 6.231124ms
      message: 'load-balancer-api-external: tcp connection to abc95519c67f9460189748464d737b7a-a75d8cad7bdd6449.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:28:07Z"
    - latency: 8.224969ms
      message: 'load-balancer-api-external: resolved host name abc95519c67f9460189748464d737b7a-a75d8cad7bdd6449.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T23:28:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T21:56:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-79-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-79.ec2.internal
      uid: 4e3b2529-5947-44c3-bbd8-5300c9cd397a
    resourceVersion: "96030"
    uid: be5249df-5099-4a2e-9953-566abfefef39
  spec:
    sourcePod: network-check-source-7cbc45fddc-2ddwm
    targetEndpoint: abc95519c67f9460189748464d737b7a-a75d8cad7bdd6449.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T22:02:07Z"
      message: 'load-balancer-api-internal: tcp connection to abc95519c67f9460189748464d737b7a-a75d8cad7bdd6449.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.645046ms
      message: 'load-balancer-api-internal: tcp connection to abc95519c67f9460189748464d737b7a-a75d8cad7bdd6449.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:32:07Z"
    - latency: 6.720926ms
      message: 'load-balancer-api-internal: resolved host name abc95519c67f9460189748464d737b7a-a75d8cad7bdd6449.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T23:32:07Z"
    - latency: 4.735073ms
      message: 'load-balancer-api-internal: tcp connection to abc95519c67f9460189748464d737b7a-a75d8cad7bdd6449.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:31:07Z"
    - latency: 8.518264ms
      message: 'load-balancer-api-internal: resolved host name abc95519c67f9460189748464d737b7a-a75d8cad7bdd6449.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T23:31:07Z"
    - latency: 4.872253ms
      message: 'load-balancer-api-internal: tcp connection to abc95519c67f9460189748464d737b7a-a75d8cad7bdd6449.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:30:07Z"
    - latency: 8.743275ms
      message: 'load-balancer-api-internal: resolved host name abc95519c67f9460189748464d737b7a-a75d8cad7bdd6449.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T23:30:07Z"
    - latency: 5.091335ms
      message: 'load-balancer-api-internal: tcp connection to abc95519c67f9460189748464d737b7a-a75d8cad7bdd6449.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:29:07Z"
    - latency: 8.705249ms
      message: 'load-balancer-api-internal: resolved host name abc95519c67f9460189748464d737b7a-a75d8cad7bdd6449.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T23:29:07Z"
    - latency: 6.19619ms
      message: 'load-balancer-api-internal: tcp connection to abc95519c67f9460189748464d737b7a-a75d8cad7bdd6449.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:28:07Z"
    - latency: 8.207904ms
      message: 'load-balancer-api-internal: resolved host name abc95519c67f9460189748464d737b7a-a75d8cad7bdd6449.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T23:28:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T21:56:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-79-to-network-check-target-ip-10-0-130-79
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-79.ec2.internal
      uid: 4e3b2529-5947-44c3-bbd8-5300c9cd397a
    resourceVersion: "97370"
    uid: b525bfcc-93f9-4713-b940-696475d9c0a5
  spec:
    sourcePod: network-check-source-7cbc45fddc-2ddwm
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T22:03:07Z"
      message: 'network-check-target-ip-10-0-130-79: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 824.104µs
      message: 'network-check-target-ip-10-0-130-79: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:34:07Z"
    - latency: 973.744µs
      message: 'network-check-target-ip-10-0-130-79: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:33:07Z"
    - latency: 1.315049ms
      message: 'network-check-target-ip-10-0-130-79: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:32:07Z"
    - latency: 853.138µs
      message: 'network-check-target-ip-10-0-130-79: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:31:07Z"
    - latency: 972.659µs
      message: 'network-check-target-ip-10-0-130-79: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:30:07Z"
    - latency: 925.48µs
      message: 'network-check-target-ip-10-0-130-79: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:29:07Z"
    - latency: 871.064µs
      message: 'network-check-target-ip-10-0-130-79: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:28:07Z"
    - latency: 769.779µs
      message: 'network-check-target-ip-10-0-130-79: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:27:07Z"
    - latency: 924.413µs
      message: 'network-check-target-ip-10-0-130-79: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:26:07Z"
    - latency: 1.337548ms
      message: 'network-check-target-ip-10-0-130-79: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:25:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T21:56:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-79-to-network-check-target-ip-10-0-141-13
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-79.ec2.internal
      uid: 4e3b2529-5947-44c3-bbd8-5300c9cd397a
    resourceVersion: "97372"
    uid: a1ddb6fd-3e0a-47e0-a2e3-62d0a66f264a
  spec:
    sourcePod: network-check-source-7cbc45fddc-2ddwm
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T22:03:07Z"
      message: 'network-check-target-ip-10-0-141-13: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.633385ms
      message: 'network-check-target-ip-10-0-141-13: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:34:07Z"
    - latency: 2.378498ms
      message: 'network-check-target-ip-10-0-141-13: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:33:07Z"
    - latency: 2.388588ms
      message: 'network-check-target-ip-10-0-141-13: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:32:07Z"
    - latency: 2.33706ms
      message: 'network-check-target-ip-10-0-141-13: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:31:07Z"
    - latency: 2.366222ms
      message: 'network-check-target-ip-10-0-141-13: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:30:07Z"
    - latency: 1.997699ms
      message: 'network-check-target-ip-10-0-141-13: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:29:07Z"
    - latency: 1.910171ms
      message: 'network-check-target-ip-10-0-141-13: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:28:07Z"
    - latency: 2.165424ms
      message: 'network-check-target-ip-10-0-141-13: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:27:07Z"
    - latency: 2.415422ms
      message: 'network-check-target-ip-10-0-141-13: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:26:07Z"
    - latency: 2.264888ms
      message: 'network-check-target-ip-10-0-141-13: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:25:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T21:56:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-79-to-network-check-target-ip-10-0-142-209
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-79.ec2.internal
      uid: 4e3b2529-5947-44c3-bbd8-5300c9cd397a
    resourceVersion: "97371"
    uid: 08efe43b-b692-4491-acc7-060f805e1423
  spec:
    sourcePod: network-check-source-7cbc45fddc-2ddwm
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T22:03:07Z"
      message: 'network-check-target-ip-10-0-142-209: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.033283ms
      message: 'network-check-target-ip-10-0-142-209: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:34:07Z"
    - latency: 2.432589ms
      message: 'network-check-target-ip-10-0-142-209: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:33:07Z"
    - latency: 2.489269ms
      message: 'network-check-target-ip-10-0-142-209: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:32:07Z"
    - latency: 2.411067ms
      message: 'network-check-target-ip-10-0-142-209: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:31:07Z"
    - latency: 3.149795ms
      message: 'network-check-target-ip-10-0-142-209: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:30:07Z"
    - latency: 2.059639ms
      message: 'network-check-target-ip-10-0-142-209: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:29:07Z"
    - latency: 2.193496ms
      message: 'network-check-target-ip-10-0-142-209: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:28:07Z"
    - latency: 2.19992ms
      message: 'network-check-target-ip-10-0-142-209: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:27:07Z"
    - latency: 2.503146ms
      message: 'network-check-target-ip-10-0-142-209: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:26:07Z"
    - latency: 2.578565ms
      message: 'network-check-target-ip-10-0-142-209: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:25:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T21:56:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-79-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-79.ec2.internal
      uid: 4e3b2529-5947-44c3-bbd8-5300c9cd397a
    resourceVersion: "96029"
    uid: fa4dcfbd-5d13-40c7-90ae-dc878293afe3
  spec:
    sourcePod: network-check-source-7cbc45fddc-2ddwm
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T22:02:07Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 919.676µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:32:07Z"
    - latency: 1.692498ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T23:32:07Z"
    - latency: 940.299µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:31:07Z"
    - latency: 2.80947ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T23:31:07Z"
    - latency: 1.041802ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:30:07Z"
    - latency: 1.773759ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T23:30:07Z"
    - latency: 853.166µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:29:07Z"
    - latency: 2.006264ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T23:29:07Z"
    - latency: 868.622µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T23:28:07Z"
    - latency: 1.562373ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T23:28:07Z"
kind: List
metadata:
  resourceVersion: ""