apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-12T00:23:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-187-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-187.ec2.internal
      uid: 336552ec-ae47-4bd7-9f22-c9257c1a7ee7
    resourceVersion: "69207"
    uid: 60bb2539-0bc0-490f-bb94-7373105a99ee
  spec:
    sourcePod: network-check-source-6f8b768455-tmqft
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-12T00:30:56Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.213048ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:58:56Z"
    - latency: 855.335µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:57:56Z"
    - latency: 980.685µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:56:56Z"
    - latency: 936.211µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:55:56Z"
    - latency: 984.129µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:54:56Z"
    - latency: 1.063909ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:53:56Z"
    - latency: 987.972µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:52:56Z"
    - latency: 1.179514ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:51:56Z"
    - latency: 1.183377ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:50:56Z"
    - latency: 1.152773ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:49:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-12T00:23:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-187-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-187.ec2.internal
      uid: 336552ec-ae47-4bd7-9f22-c9257c1a7ee7
    resourceVersion: "64848"
    uid: ab654c1d-b66a-4ac6-8652-c28475bf970b
  spec:
    sourcePod: network-check-source-6f8b768455-tmqft
    targetEndpoint: a53fa64530fdb49ff97ff0882fe22dc6-cac38b439bc9e9a9.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-12T00:29:56Z"
      message: 'load-balancer-api-external: tcp connection to a53fa64530fdb49ff97ff0882fe22dc6-cac38b439bc9e9a9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.278366ms
      message: 'load-balancer-api-external: tcp connection to a53fa64530fdb49ff97ff0882fe22dc6-cac38b439bc9e9a9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:53:56Z"
    - latency: 6.085114ms
      message: 'load-balancer-api-external: resolved host name a53fa64530fdb49ff97ff0882fe22dc6-cac38b439bc9e9a9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T00:53:56Z"
    - latency: 4.711577ms
      message: 'load-balancer-api-external: tcp connection to a53fa64530fdb49ff97ff0882fe22dc6-cac38b439bc9e9a9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:52:56Z"
    - latency: 6.715897ms
      message: 'load-balancer-api-external: resolved host name a53fa64530fdb49ff97ff0882fe22dc6-cac38b439bc9e9a9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T00:52:56Z"
    - latency: 5.352223ms
      message: 'load-balancer-api-external: tcp connection to a53fa64530fdb49ff97ff0882fe22dc6-cac38b439bc9e9a9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:51:56Z"
    - latency: 6.17737ms
      message: 'load-balancer-api-external: resolved host name a53fa64530fdb49ff97ff0882fe22dc6-cac38b439bc9e9a9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T00:51:56Z"
    - latency: 4.397008ms
      message: 'load-balancer-api-external: tcp connection to a53fa64530fdb49ff97ff0882fe22dc6-cac38b439bc9e9a9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:50:56Z"
    - latency: 6.714417ms
      message: 'load-balancer-api-external: resolved host name a53fa64530fdb49ff97ff0882fe22dc6-cac38b439bc9e9a9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T00:50:56Z"
    - latency: 4.364291ms
      message: 'load-balancer-api-external: tcp connection to a53fa64530fdb49ff97ff0882fe22dc6-cac38b439bc9e9a9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:49:56Z"
    - latency: 6.798483ms
      message: 'load-balancer-api-external: resolved host name a53fa64530fdb49ff97ff0882fe22dc6-cac38b439bc9e9a9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T00:49:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-12T00:23:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-187-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-187.ec2.internal
      uid: 336552ec-ae47-4bd7-9f22-c9257c1a7ee7
    resourceVersion: "64849"
    uid: f8dc13ef-23fa-4730-a213-2f5ceedf7dd0
  spec:
    sourcePod: network-check-source-6f8b768455-tmqft
    targetEndpoint: a53fa64530fdb49ff97ff0882fe22dc6-cac38b439bc9e9a9.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-12T00:29:56Z"
      message: 'load-balancer-api-internal: tcp connection to a53fa64530fdb49ff97ff0882fe22dc6-cac38b439bc9e9a9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.287754ms
      message: 'load-balancer-api-internal: tcp connection to a53fa64530fdb49ff97ff0882fe22dc6-cac38b439bc9e9a9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:53:56Z"
    - latency: 6.265119ms
      message: 'load-balancer-api-internal: resolved host name a53fa64530fdb49ff97ff0882fe22dc6-cac38b439bc9e9a9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T00:53:56Z"
    - latency: 4.721645ms
      message: 'load-balancer-api-internal: tcp connection to a53fa64530fdb49ff97ff0882fe22dc6-cac38b439bc9e9a9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:52:56Z"
    - latency: 6.775575ms
      message: 'load-balancer-api-internal: resolved host name a53fa64530fdb49ff97ff0882fe22dc6-cac38b439bc9e9a9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T00:52:56Z"
    - latency: 5.339256ms
      message: 'load-balancer-api-internal: tcp connection to a53fa64530fdb49ff97ff0882fe22dc6-cac38b439bc9e9a9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:51:56Z"
    - latency: 6.216908ms
      message: 'load-balancer-api-internal: resolved host name a53fa64530fdb49ff97ff0882fe22dc6-cac38b439bc9e9a9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T00:51:56Z"
    - latency: 4.403747ms
      message: 'load-balancer-api-internal: tcp connection to a53fa64530fdb49ff97ff0882fe22dc6-cac38b439bc9e9a9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:50:56Z"
    - latency: 6.604118ms
      message: 'load-balancer-api-internal: resolved host name a53fa64530fdb49ff97ff0882fe22dc6-cac38b439bc9e9a9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T00:50:56Z"
    - latency: 4.32521ms
      message: 'load-balancer-api-internal: tcp connection to a53fa64530fdb49ff97ff0882fe22dc6-cac38b439bc9e9a9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:49:56Z"
    - latency: 6.882101ms
      message: 'load-balancer-api-internal: resolved host name a53fa64530fdb49ff97ff0882fe22dc6-cac38b439bc9e9a9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T00:49:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-12T00:23:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-187-to-network-check-target-ip-10-0-134-179
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-187.ec2.internal
      uid: 336552ec-ae47-4bd7-9f22-c9257c1a7ee7
    resourceVersion: "69205"
    uid: 10d9bd84-231a-4289-860c-2757af5873ac
  spec:
    sourcePod: network-check-source-6f8b768455-tmqft
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-12T00:30:56Z"
      message: 'network-check-target-ip-10-0-134-179: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.157753ms
      message: 'network-check-target-ip-10-0-134-179: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:58:56Z"
    - latency: 2.493645ms
      message: 'network-check-target-ip-10-0-134-179: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:57:56Z"
    - latency: 2.664948ms
      message: 'network-check-target-ip-10-0-134-179: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:56:56Z"
    - latency: 2.293008ms
      message: 'network-check-target-ip-10-0-134-179: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:55:56Z"
    - latency: 2.345251ms
      message: 'network-check-target-ip-10-0-134-179: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:54:56Z"
    - latency: 2.352932ms
      message: 'network-check-target-ip-10-0-134-179: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:53:56Z"
    - latency: 2.368183ms
      message: 'network-check-target-ip-10-0-134-179: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:52:56Z"
    - latency: 2.505023ms
      message: 'network-check-target-ip-10-0-134-179: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:51:56Z"
    - latency: 2.958373ms
      message: 'network-check-target-ip-10-0-134-179: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:50:56Z"
    - latency: 2.212912ms
      message: 'network-check-target-ip-10-0-134-179: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:49:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-12T00:23:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-187-to-network-check-target-ip-10-0-140-187
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-187.ec2.internal
      uid: 336552ec-ae47-4bd7-9f22-c9257c1a7ee7
    resourceVersion: "69204"
    uid: ac3952f7-f9c0-408f-9ffd-4fec4b2bb9f7
  spec:
    sourcePod: network-check-source-6f8b768455-tmqft
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-12T00:30:56Z"
      message: 'network-check-target-ip-10-0-140-187: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.376495ms
      message: 'network-check-target-ip-10-0-140-187: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:58:56Z"
    - latency: 1.106344ms
      message: 'network-check-target-ip-10-0-140-187: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:57:56Z"
    - latency: 1.460777ms
      message: 'network-check-target-ip-10-0-140-187: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:56:56Z"
    - latency: 998.87µs
      message: 'network-check-target-ip-10-0-140-187: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:55:56Z"
    - latency: 952.503µs
      message: 'network-check-target-ip-10-0-140-187: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:54:56Z"
    - latency: 1.162385ms
      message: 'network-check-target-ip-10-0-140-187: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:53:56Z"
    - latency: 1.417829ms
      message: 'network-check-target-ip-10-0-140-187: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:52:56Z"
    - latency: 1.011501ms
      message: 'network-check-target-ip-10-0-140-187: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:51:56Z"
    - latency: 982.098µs
      message: 'network-check-target-ip-10-0-140-187: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:50:56Z"
    - latency: 1.045738ms
      message: 'network-check-target-ip-10-0-140-187: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:49:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-12T00:23:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-187-to-network-check-target-ip-10-0-141-128
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-187.ec2.internal
      uid: 336552ec-ae47-4bd7-9f22-c9257c1a7ee7
    resourceVersion: "69206"
    uid: 7081fa21-07fe-4a72-8d0b-36432bb2d2d4
  spec:
    sourcePod: network-check-source-6f8b768455-tmqft
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-12T00:30:56Z"
      message: 'network-check-target-ip-10-0-141-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.682272ms
      message: 'network-check-target-ip-10-0-141-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:58:56Z"
    - latency: 2.364802ms
      message: 'network-check-target-ip-10-0-141-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:57:56Z"
    - latency: 2.417869ms
      message: 'network-check-target-ip-10-0-141-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:56:56Z"
    - latency: 2.749139ms
      message: 'network-check-target-ip-10-0-141-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:55:56Z"
    - latency: 2.263688ms
      message: 'network-check-target-ip-10-0-141-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:54:56Z"
    - latency: 2.854865ms
      message: 'network-check-target-ip-10-0-141-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:53:56Z"
    - latency: 2.478638ms
      message: 'network-check-target-ip-10-0-141-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:52:56Z"
    - latency: 2.342082ms
      message: 'network-check-target-ip-10-0-141-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:51:56Z"
    - latency: 2.279018ms
      message: 'network-check-target-ip-10-0-141-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:50:56Z"
    - latency: 2.506797ms
      message: 'network-check-target-ip-10-0-141-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:49:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-12T00:23:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-187-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-187.ec2.internal
      uid: 336552ec-ae47-4bd7-9f22-c9257c1a7ee7
    resourceVersion: "64846"
    uid: ce7cac32-890f-4ee0-9401-07db97cc6eb9
  spec:
    sourcePod: network-check-source-6f8b768455-tmqft
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-12T00:29:56Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 909.333µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:53:56Z"
    - latency: 1.941418ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T00:53:56Z"
    - latency: 1.076798ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:52:56Z"
    - latency: 2.068846ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T00:52:56Z"
    - latency: 1.048301ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:51:56Z"
    - latency: 1.672423ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T00:51:56Z"
    - latency: 1.095359ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:50:56Z"
    - latency: 1.867127ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T00:50:56Z"
    - latency: 1.013457ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-12T00:49:56Z"
    - latency: 2.081251ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-12T00:49:56Z"
kind: List
metadata:
  resourceVersion: ""