apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T18:08:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-59-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-59.ec2.internal
      uid: 30d5c8ac-4125-4e67-bc94-9c956bd7d7fd
    resourceVersion: "22749"
    uid: 1fcb59dc-a846-418d-a32b-b4c444152aba
  spec:
    sourcePod: network-check-source-869dcfcdcd-dv67x
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T18:15:49Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.043435ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:29:49Z"
    - latency: 1.000634ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:28:49Z"
    - latency: 1.118404ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:27:49Z"
    - latency: 1.23959ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:26:49Z"
    - latency: 932.074µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:25:49Z"
    - latency: 1.387042ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:24:49Z"
    - latency: 1.075651ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:23:49Z"
    - latency: 1.279007ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:22:49Z"
    - latency: 1.039287ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:21:49Z"
    - latency: 973.429µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:20:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T18:08:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-59-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-59.ec2.internal
      uid: 30d5c8ac-4125-4e67-bc94-9c956bd7d7fd
    resourceVersion: "21334"
    uid: a86893b5-7007-40e4-b89a-6babe6fbef62
  spec:
    sourcePod: network-check-source-869dcfcdcd-dv67x
    targetEndpoint: adcbd2022efaa459a977d662beea0a7d-c8614b2aa8734dd7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T18:14:49Z"
      message: 'load-balancer-api-external: tcp connection to adcbd2022efaa459a977d662beea0a7d-c8614b2aa8734dd7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.960554ms
      message: 'load-balancer-api-external: tcp connection to adcbd2022efaa459a977d662beea0a7d-c8614b2aa8734dd7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:26:49Z"
    - latency: 8.800301ms
      message: 'load-balancer-api-external: resolved host name adcbd2022efaa459a977d662beea0a7d-c8614b2aa8734dd7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T18:26:49Z"
    - latency: 10.600872ms
      message: 'load-balancer-api-external: tcp connection to adcbd2022efaa459a977d662beea0a7d-c8614b2aa8734dd7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:25:49Z"
    - latency: 9.994227ms
      message: 'load-balancer-api-external: resolved host name adcbd2022efaa459a977d662beea0a7d-c8614b2aa8734dd7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T18:25:49Z"
    - latency: 5.089799ms
      message: 'load-balancer-api-external: tcp connection to adcbd2022efaa459a977d662beea0a7d-c8614b2aa8734dd7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:24:49Z"
    - latency: 9.137553ms
      message: 'load-balancer-api-external: resolved host name adcbd2022efaa459a977d662beea0a7d-c8614b2aa8734dd7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T18:24:49Z"
    - latency: 4.992943ms
      message: 'load-balancer-api-external: tcp connection to adcbd2022efaa459a977d662beea0a7d-c8614b2aa8734dd7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:23:49Z"
    - latency: 9.11946ms
      message: 'load-balancer-api-external: resolved host name adcbd2022efaa459a977d662beea0a7d-c8614b2aa8734dd7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T18:23:49Z"
    - latency: 6.027593ms
      message: 'load-balancer-api-external: tcp connection to adcbd2022efaa459a977d662beea0a7d-c8614b2aa8734dd7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:22:49Z"
    - latency: 9.187046ms
      message: 'load-balancer-api-external: resolved host name adcbd2022efaa459a977d662beea0a7d-c8614b2aa8734dd7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T18:22:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T18:08:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-59-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-59.ec2.internal
      uid: 30d5c8ac-4125-4e67-bc94-9c956bd7d7fd
    resourceVersion: "21335"
    uid: e049fb60-0d1a-4f56-a4fa-8861a386efdc
  spec:
    sourcePod: network-check-source-869dcfcdcd-dv67x
    targetEndpoint: adcbd2022efaa459a977d662beea0a7d-c8614b2aa8734dd7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T18:14:49Z"
      message: 'load-balancer-api-internal: tcp connection to adcbd2022efaa459a977d662beea0a7d-c8614b2aa8734dd7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.009243ms
      message: 'load-balancer-api-internal: tcp connection to adcbd2022efaa459a977d662beea0a7d-c8614b2aa8734dd7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:26:49Z"
    - latency: 8.745164ms
      message: 'load-balancer-api-internal: resolved host name adcbd2022efaa459a977d662beea0a7d-c8614b2aa8734dd7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T18:26:49Z"
    - latency: 4.317304ms
      message: 'load-balancer-api-internal: tcp connection to adcbd2022efaa459a977d662beea0a7d-c8614b2aa8734dd7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:25:49Z"
    - latency: 9.920298ms
      message: 'load-balancer-api-internal: resolved host name adcbd2022efaa459a977d662beea0a7d-c8614b2aa8734dd7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T18:25:49Z"
    - latency: 5.11355ms
      message: 'load-balancer-api-internal: tcp connection to adcbd2022efaa459a977d662beea0a7d-c8614b2aa8734dd7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:24:49Z"
    - latency: 9.037672ms
      message: 'load-balancer-api-internal: resolved host name adcbd2022efaa459a977d662beea0a7d-c8614b2aa8734dd7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T18:24:49Z"
    - latency: 5.064849ms
      message: 'load-balancer-api-internal: tcp connection to adcbd2022efaa459a977d662beea0a7d-c8614b2aa8734dd7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:23:49Z"
    - latency: 9.038512ms
      message: 'load-balancer-api-internal: resolved host name adcbd2022efaa459a977d662beea0a7d-c8614b2aa8734dd7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T18:23:49Z"
    - latency: 6.037172ms
      message: 'load-balancer-api-internal: tcp connection to adcbd2022efaa459a977d662beea0a7d-c8614b2aa8734dd7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:22:49Z"
    - latency: 9.130356ms
      message: 'load-balancer-api-internal: resolved host name adcbd2022efaa459a977d662beea0a7d-c8614b2aa8734dd7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T18:22:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T18:08:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-59-to-network-check-target-ip-10-0-133-59
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-59.ec2.internal
      uid: 30d5c8ac-4125-4e67-bc94-9c956bd7d7fd
    resourceVersion: "22746"
    uid: 5ecdb96f-860f-4b22-b77d-8f22952c0b9a
  spec:
    sourcePod: network-check-source-869dcfcdcd-dv67x
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T18:15:49Z"
      message: 'network-check-target-ip-10-0-133-59: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 933.494µs
      message: 'network-check-target-ip-10-0-133-59: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:29:49Z"
    - latency: 1.412903ms
      message: 'network-check-target-ip-10-0-133-59: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:28:49Z"
    - latency: 1.086912ms
      message: 'network-check-target-ip-10-0-133-59: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:27:49Z"
    - latency: 992.978µs
      message: 'network-check-target-ip-10-0-133-59: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:26:49Z"
    - latency: 880.904µs
      message: 'network-check-target-ip-10-0-133-59: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:25:49Z"
    - latency: 1.00875ms
      message: 'network-check-target-ip-10-0-133-59: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:24:49Z"
    - latency: 1.534975ms
      message: 'network-check-target-ip-10-0-133-59: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:23:49Z"
    - latency: 1.498689ms
      message: 'network-check-target-ip-10-0-133-59: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:22:49Z"
    - latency: 1.051976ms
      message: 'network-check-target-ip-10-0-133-59: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:21:49Z"
    - latency: 1.496694ms
      message: 'network-check-target-ip-10-0-133-59: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:20:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T18:08:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-59-to-network-check-target-ip-10-0-138-186
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-59.ec2.internal
      uid: 30d5c8ac-4125-4e67-bc94-9c956bd7d7fd
    resourceVersion: "22747"
    uid: 77919522-814c-4156-a5e1-46cf8fdb6067
  spec:
    sourcePod: network-check-source-869dcfcdcd-dv67x
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T18:15:49Z"
      message: 'network-check-target-ip-10-0-138-186: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.435443ms
      message: 'network-check-target-ip-10-0-138-186: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:29:49Z"
    - latency: 2.237024ms
      message: 'network-check-target-ip-10-0-138-186: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:28:49Z"
    - latency: 2.351513ms
      message: 'network-check-target-ip-10-0-138-186: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:27:49Z"
    - latency: 2.070712ms
      message: 'network-check-target-ip-10-0-138-186: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:26:49Z"
    - latency: 2.397928ms
      message: 'network-check-target-ip-10-0-138-186: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:25:49Z"
    - latency: 2.281985ms
      message: 'network-check-target-ip-10-0-138-186: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:24:49Z"
    - latency: 2.20886ms
      message: 'network-check-target-ip-10-0-138-186: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:23:49Z"
    - latency: 2.243991ms
      message: 'network-check-target-ip-10-0-138-186: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:22:49Z"
    - latency: 2.234539ms
      message: 'network-check-target-ip-10-0-138-186: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:21:49Z"
    - latency: 2.08173ms
      message: 'network-check-target-ip-10-0-138-186: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:20:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T18:08:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-59-to-network-check-target-ip-10-0-140-229
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-59.ec2.internal
      uid: 30d5c8ac-4125-4e67-bc94-9c956bd7d7fd
    resourceVersion: "22748"
    uid: 525f3340-89ba-40be-a7ec-6388b13048e0
  spec:
    sourcePod: network-check-source-869dcfcdcd-dv67x
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T18:15:49Z"
      message: 'network-check-target-ip-10-0-140-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.510252ms
      message: 'network-check-target-ip-10-0-140-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:29:49Z"
    - latency: 2.402792ms
      message: 'network-check-target-ip-10-0-140-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:28:49Z"
    - latency: 2.137138ms
      message: 'network-check-target-ip-10-0-140-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:27:49Z"
    - latency: 2.564816ms
      message: 'network-check-target-ip-10-0-140-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:26:49Z"
    - latency: 2.263767ms
      message: 'network-check-target-ip-10-0-140-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:25:49Z"
    - latency: 2.557226ms
      message: 'network-check-target-ip-10-0-140-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:24:49Z"
    - latency: 2.706159ms
      message: 'network-check-target-ip-10-0-140-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:23:49Z"
    - latency: 2.795854ms
      message: 'network-check-target-ip-10-0-140-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:22:49Z"
    - latency: 2.533366ms
      message: 'network-check-target-ip-10-0-140-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:21:49Z"
    - latency: 2.568388ms
      message: 'network-check-target-ip-10-0-140-229: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:20:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T18:08:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-59-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-59.ec2.internal
      uid: 30d5c8ac-4125-4e67-bc94-9c956bd7d7fd
    resourceVersion: "21333"
    uid: 4b660553-a0be-47c6-acab-e3f04f144c98
  spec:
    sourcePod: network-check-source-869dcfcdcd-dv67x
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T18:14:49Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 848.963µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:26:49Z"
    - latency: 1.884761ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T18:26:49Z"
    - latency: 969.891µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:25:49Z"
    - latency: 1.780956ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T18:25:49Z"
    - latency: 1.133353ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:24:49Z"
    - latency: 1.967368ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T18:24:49Z"
    - latency: 1.00506ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:23:49Z"
    - latency: 1.982719ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T18:23:49Z"
    - latency: 1.036639ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T18:22:49Z"
    - latency: 1.990525ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T18:22:49Z"
kind: List
metadata:
  resourceVersion: ""