apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-29T21:47:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-146-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-146.ec2.internal
      uid: 85ac1322-3c4e-420f-8b26-7d0d3cbf3883
    resourceVersion: "84726"
    uid: e4b5a8fd-2a87-4e5d-8808-6c6c73094e25
  spec:
    sourcePod: network-check-source-6f78d59f99-wq26q
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-29T21:54:51Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.118523ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:15:51Z"
    - latency: 872.841µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:14:51Z"
    - latency: 1.527937ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:13:51Z"
    - latency: 5.860817ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:12:51Z"
    - latency: 199.381784ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:11:51Z"
    - latency: 3.036041ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:10:51Z"
    - latency: 6.500855ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:09:51Z"
    - latency: 18.534805ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:08:51Z"
    - latency: 11.504973ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:07:51Z"
    - latency: 23.928506ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:06:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-29T21:47:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-146-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-146.ec2.internal
      uid: 85ac1322-3c4e-420f-8b26-7d0d3cbf3883
    resourceVersion: "73473"
    uid: 4d421582-0982-42d0-9ad8-27a5ab8bfa48
  spec:
    sourcePod: network-check-source-6f78d59f99-wq26q
    targetEndpoint: a819732efc02a4355afb2ee19675cd95-0cbdf7d5908c2d7a.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-29T21:53:51Z"
      message: 'load-balancer-api-external: tcp connection to a819732efc02a4355afb2ee19675cd95-0cbdf7d5908c2d7a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 118.650227ms
      message: 'load-balancer-api-external: tcp connection to a819732efc02a4355afb2ee19675cd95-0cbdf7d5908c2d7a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:11:52Z"
    - latency: 496.558219ms
      message: 'load-balancer-api-external: resolved host name a819732efc02a4355afb2ee19675cd95-0cbdf7d5908c2d7a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T22:11:51Z"
    - latency: 16.76672ms
      message: 'load-balancer-api-external: tcp connection to a819732efc02a4355afb2ee19675cd95-0cbdf7d5908c2d7a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:10:51Z"
    - latency: 9.427161ms
      message: 'load-balancer-api-external: resolved host name a819732efc02a4355afb2ee19675cd95-0cbdf7d5908c2d7a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T22:10:51Z"
    - latency: 29.838344ms
      message: 'load-balancer-api-external: tcp connection to a819732efc02a4355afb2ee19675cd95-0cbdf7d5908c2d7a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:09:51Z"
    - latency: 20.082004ms
      message: 'load-balancer-api-external: resolved host name a819732efc02a4355afb2ee19675cd95-0cbdf7d5908c2d7a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T22:09:51Z"
    - latency: 18.234984ms
      message: 'load-balancer-api-external: tcp connection to a819732efc02a4355afb2ee19675cd95-0cbdf7d5908c2d7a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:08:51Z"
    - latency: 78.070404ms
      message: 'load-balancer-api-external: resolved host name a819732efc02a4355afb2ee19675cd95-0cbdf7d5908c2d7a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T22:08:51Z"
    - latency: 17.026017ms
      message: 'load-balancer-api-external: tcp connection to a819732efc02a4355afb2ee19675cd95-0cbdf7d5908c2d7a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:07:51Z"
    - latency: 82.198696ms
      message: 'load-balancer-api-external: resolved host name a819732efc02a4355afb2ee19675cd95-0cbdf7d5908c2d7a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T22:07:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-29T21:47:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-146-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-146.ec2.internal
      uid: 85ac1322-3c4e-420f-8b26-7d0d3cbf3883
    resourceVersion: "73474"
    uid: 716ab5f4-3d00-46d3-84a7-110eed479317
  spec:
    sourcePod: network-check-source-6f78d59f99-wq26q
    targetEndpoint: a819732efc02a4355afb2ee19675cd95-0cbdf7d5908c2d7a.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-29T21:53:51Z"
      message: 'load-balancer-api-internal: tcp connection to a819732efc02a4355afb2ee19675cd95-0cbdf7d5908c2d7a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 118.98436ms
      message: 'load-balancer-api-internal: tcp connection to a819732efc02a4355afb2ee19675cd95-0cbdf7d5908c2d7a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:11:52Z"
    - latency: 496.509359ms
      message: 'load-balancer-api-internal: resolved host name a819732efc02a4355afb2ee19675cd95-0cbdf7d5908c2d7a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T22:11:51Z"
    - latency: 16.784498ms
      message: 'load-balancer-api-internal: tcp connection to a819732efc02a4355afb2ee19675cd95-0cbdf7d5908c2d7a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:10:51Z"
    - latency: 9.379711ms
      message: 'load-balancer-api-internal: resolved host name a819732efc02a4355afb2ee19675cd95-0cbdf7d5908c2d7a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T22:10:51Z"
    - latency: 32.73402ms
      message: 'load-balancer-api-internal: tcp connection to a819732efc02a4355afb2ee19675cd95-0cbdf7d5908c2d7a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:09:51Z"
    - latency: 19.855632ms
      message: 'load-balancer-api-internal: resolved host name a819732efc02a4355afb2ee19675cd95-0cbdf7d5908c2d7a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T22:09:51Z"
    - latency: 18.283875ms
      message: 'load-balancer-api-internal: tcp connection to a819732efc02a4355afb2ee19675cd95-0cbdf7d5908c2d7a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:08:51Z"
    - latency: 77.748004ms
      message: 'load-balancer-api-internal: resolved host name a819732efc02a4355afb2ee19675cd95-0cbdf7d5908c2d7a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T22:08:51Z"
    - latency: 19.286781ms
      message: 'load-balancer-api-internal: tcp connection to a819732efc02a4355afb2ee19675cd95-0cbdf7d5908c2d7a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:07:51Z"
    - latency: 81.61754ms
      message: 'load-balancer-api-internal: resolved host name a819732efc02a4355afb2ee19675cd95-0cbdf7d5908c2d7a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T22:07:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-29T21:47:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-146-to-network-check-target-ip-10-0-128-85
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-146.ec2.internal
      uid: 85ac1322-3c4e-420f-8b26-7d0d3cbf3883
    resourceVersion: "84722"
    uid: 7122fe8c-20f8-4a01-9a6c-42c9e2b21691
  spec:
    sourcePod: network-check-source-6f78d59f99-wq26q
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-29T21:54:51Z"
      message: 'network-check-target-ip-10-0-128-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.271322ms
      message: 'network-check-target-ip-10-0-128-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:15:51Z"
    - latency: 2.661828ms
      message: 'network-check-target-ip-10-0-128-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:14:51Z"
    - latency: 2.408996ms
      message: 'network-check-target-ip-10-0-128-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:13:51Z"
    - latency: 7.607793ms
      message: 'network-check-target-ip-10-0-128-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:12:51Z"
    - latency: 39.582361ms
      message: 'network-check-target-ip-10-0-128-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:11:51Z"
    - latency: 2.492638ms
      message: 'network-check-target-ip-10-0-128-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:10:51Z"
    - latency: 7.056475ms
      message: 'network-check-target-ip-10-0-128-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:09:51Z"
    - latency: 17.985043ms
      message: 'network-check-target-ip-10-0-128-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:08:51Z"
    - latency: 5.56189ms
      message: 'network-check-target-ip-10-0-128-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:07:51Z"
    - latency: 24.18736ms
      message: 'network-check-target-ip-10-0-128-85: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:06:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-29T21:47:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-146-to-network-check-target-ip-10-0-129-146
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-146.ec2.internal
      uid: 85ac1322-3c4e-420f-8b26-7d0d3cbf3883
    resourceVersion: "84721"
    uid: ba5a944a-b763-4022-97e9-a8278b5d95ec
  spec:
    sourcePod: network-check-source-6f78d59f99-wq26q
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-29T21:54:51Z"
      message: 'network-check-target-ip-10-0-129-146: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.198398ms
      message: 'network-check-target-ip-10-0-129-146: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:15:51Z"
    - latency: 937.7µs
      message: 'network-check-target-ip-10-0-129-146: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:14:51Z"
    - latency: 1.011359ms
      message: 'network-check-target-ip-10-0-129-146: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:13:51Z"
    - latency: 5.260857ms
      message: 'network-check-target-ip-10-0-129-146: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:12:51Z"
    - latency: 198.41568ms
      message: 'network-check-target-ip-10-0-129-146: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:11:51Z"
    - latency: 2.130992ms
      message: 'network-check-target-ip-10-0-129-146: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:10:51Z"
    - latency: 5.040871ms
      message: 'network-check-target-ip-10-0-129-146: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:09:51Z"
    - latency: 17.760832ms
      message: 'network-check-target-ip-10-0-129-146: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:08:51Z"
    - latency: 10.439834ms
      message: 'network-check-target-ip-10-0-129-146: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:07:51Z"
    - latency: 25.080008ms
      message: 'network-check-target-ip-10-0-129-146: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:06:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-29T21:47:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-146-to-network-check-target-ip-10-0-136-38
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-146.ec2.internal
      uid: 85ac1322-3c4e-420f-8b26-7d0d3cbf3883
    resourceVersion: "84723"
    uid: 2e9d6bc4-7c36-47f5-95b6-4150104d3397
  spec:
    sourcePod: network-check-source-6f78d59f99-wq26q
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-29T21:54:51Z"
      message: 'network-check-target-ip-10-0-136-38: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.88177ms
      message: 'network-check-target-ip-10-0-136-38: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:15:51Z"
    - latency: 2.452037ms
      message: 'network-check-target-ip-10-0-136-38: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:14:51Z"
    - latency: 2.822254ms
      message: 'network-check-target-ip-10-0-136-38: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:13:51Z"
    - latency: 11.162802ms
      message: 'network-check-target-ip-10-0-136-38: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:12:51Z"
    - latency: 263.801511ms
      message: 'network-check-target-ip-10-0-136-38: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:11:51Z"
    - latency: 11.612173ms
      message: 'network-check-target-ip-10-0-136-38: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:10:51Z"
    - latency: 3.797655ms
      message: 'network-check-target-ip-10-0-136-38: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:09:51Z"
    - latency: 18.275592ms
      message: 'network-check-target-ip-10-0-136-38: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:08:51Z"
    - latency: 157.463845ms
      message: 'network-check-target-ip-10-0-136-38: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:07:51Z"
    - latency: 43.589888ms
      message: 'network-check-target-ip-10-0-136-38: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:06:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-29T21:47:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-146-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-146.ec2.internal
      uid: 85ac1322-3c4e-420f-8b26-7d0d3cbf3883
    resourceVersion: "73456"
    uid: 5a8ce27d-0bb2-4b38-86cc-0ef5b2da3774
  spec:
    sourcePod: network-check-source-6f78d59f99-wq26q
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-29T21:53:51Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 12.996716ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:11:51Z"
    - latency: 249.96606ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T22:11:51Z"
    - latency: 1.197528ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:10:51Z"
    - latency: 2.309775ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T22:10:51Z"
    - latency: 1.813634ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:09:51Z"
    - latency: 6.240982ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T22:09:51Z"
    - latency: 12.870137ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:08:51Z"
    - latency: 47.90267ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T22:08:51Z"
    - latency: 15.400754ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T22:07:51Z"
    - latency: 46.492873ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T22:07:51Z"
kind: List
metadata:
  resourceVersion: ""