apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T15:11:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-215-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-215.ec2.internal
      uid: 1fa77dda-6ee7-4e01-b700-0ea8dcd63153
    resourceVersion: "58255"
    uid: af636d0d-ced1-43da-915c-65442838feb9
  spec:
    sourcePod: network-check-source-6f8b768455-qm4lg
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T15:18:58Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.126578ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:39:58Z"
    - latency: 956.849µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:38:58Z"
    - latency: 891.827µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:37:58Z"
    - latency: 1.179813ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:36:58Z"
    - latency: 839.93µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:35:58Z"
    - latency: 1.427428ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:34:58Z"
    - latency: 1.042902ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:33:58Z"
    - latency: 938.755µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:32:58Z"
    - latency: 940.587µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:31:58Z"
    - latency: 990.205µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:30:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T15:11:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-215-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-215.ec2.internal
      uid: 1fa77dda-6ee7-4e01-b700-0ea8dcd63153
    resourceVersion: "59986"
    uid: 1e4b741a-6357-4f17-96d3-d44372a2ffdf
  spec:
    sourcePod: network-check-source-6f8b768455-qm4lg
    targetEndpoint: adcda812868e94021a91f69527677a14-bfdfe5aed3c461ce.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T15:17:58Z"
      message: 'load-balancer-api-external: tcp connection to adcda812868e94021a91f69527677a14-bfdfe5aed3c461ce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.359418ms
      message: 'load-balancer-api-external: tcp connection to adcda812868e94021a91f69527677a14-bfdfe5aed3c461ce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:41:58Z"
    - latency: 7.123457ms
      message: 'load-balancer-api-external: resolved host name adcda812868e94021a91f69527677a14-bfdfe5aed3c461ce.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T15:41:58Z"
    - latency: 5.491374ms
      message: 'load-balancer-api-external: tcp connection to adcda812868e94021a91f69527677a14-bfdfe5aed3c461ce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:40:58Z"
    - latency: 7.260861ms
      message: 'load-balancer-api-external: resolved host name adcda812868e94021a91f69527677a14-bfdfe5aed3c461ce.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T15:40:58Z"
    - latency: 4.016673ms
      message: 'load-balancer-api-external: tcp connection to adcda812868e94021a91f69527677a14-bfdfe5aed3c461ce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:39:58Z"
    - latency: 7.527899ms
      message: 'load-balancer-api-external: resolved host name adcda812868e94021a91f69527677a14-bfdfe5aed3c461ce.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T15:39:58Z"
    - latency: 5.949019ms
      message: 'load-balancer-api-external: tcp connection to adcda812868e94021a91f69527677a14-bfdfe5aed3c461ce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:38:58Z"
    - latency: 7.034715ms
      message: 'load-balancer-api-external: resolved host name adcda812868e94021a91f69527677a14-bfdfe5aed3c461ce.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T15:38:58Z"
    - latency: 3.423937ms
      message: 'load-balancer-api-external: tcp connection to adcda812868e94021a91f69527677a14-bfdfe5aed3c461ce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:37:58Z"
    - latency: 7.377796ms
      message: 'load-balancer-api-external: resolved host name adcda812868e94021a91f69527677a14-bfdfe5aed3c461ce.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T15:37:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T15:11:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-215-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-215.ec2.internal
      uid: 1fa77dda-6ee7-4e01-b700-0ea8dcd63153
    resourceVersion: "59985"
    uid: cc49d849-44e0-4fd8-99d9-03593a6432c0
  spec:
    sourcePod: network-check-source-6f8b768455-qm4lg
    targetEndpoint: adcda812868e94021a91f69527677a14-bfdfe5aed3c461ce.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T15:17:58Z"
      message: 'load-balancer-api-internal: tcp connection to adcda812868e94021a91f69527677a14-bfdfe5aed3c461ce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.370811ms
      message: 'load-balancer-api-internal: tcp connection to adcda812868e94021a91f69527677a14-bfdfe5aed3c461ce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:41:58Z"
    - latency: 7.168426ms
      message: 'load-balancer-api-internal: resolved host name adcda812868e94021a91f69527677a14-bfdfe5aed3c461ce.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T15:41:58Z"
    - latency: 5.475887ms
      message: 'load-balancer-api-internal: tcp connection to adcda812868e94021a91f69527677a14-bfdfe5aed3c461ce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:40:58Z"
    - latency: 7.323818ms
      message: 'load-balancer-api-internal: resolved host name adcda812868e94021a91f69527677a14-bfdfe5aed3c461ce.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T15:40:58Z"
    - latency: 3.996111ms
      message: 'load-balancer-api-internal: tcp connection to adcda812868e94021a91f69527677a14-bfdfe5aed3c461ce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:39:58Z"
    - latency: 7.566761ms
      message: 'load-balancer-api-internal: resolved host name adcda812868e94021a91f69527677a14-bfdfe5aed3c461ce.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T15:39:58Z"
    - latency: 5.831818ms
      message: 'load-balancer-api-internal: tcp connection to adcda812868e94021a91f69527677a14-bfdfe5aed3c461ce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:38:58Z"
    - latency: 7.10364ms
      message: 'load-balancer-api-internal: resolved host name adcda812868e94021a91f69527677a14-bfdfe5aed3c461ce.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T15:38:58Z"
    - latency: 3.389902ms
      message: 'load-balancer-api-internal: tcp connection to adcda812868e94021a91f69527677a14-bfdfe5aed3c461ce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:37:58Z"
    - latency: 7.460006ms
      message: 'load-balancer-api-internal: resolved host name adcda812868e94021a91f69527677a14-bfdfe5aed3c461ce.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T15:37:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T15:11:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-215-to-network-check-target-ip-10-0-134-128
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-215.ec2.internal
      uid: 1fa77dda-6ee7-4e01-b700-0ea8dcd63153
    resourceVersion: "58253"
    uid: 7e5732e2-0b7f-4704-a471-850f85dac9a3
  spec:
    sourcePod: network-check-source-6f8b768455-qm4lg
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T15:18:58Z"
      message: 'network-check-target-ip-10-0-134-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.018253ms
      message: 'network-check-target-ip-10-0-134-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:39:58Z"
    - latency: 1.946628ms
      message: 'network-check-target-ip-10-0-134-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:38:58Z"
    - latency: 2.176666ms
      message: 'network-check-target-ip-10-0-134-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:37:58Z"
    - latency: 2.109078ms
      message: 'network-check-target-ip-10-0-134-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:36:58Z"
    - latency: 1.977006ms
      message: 'network-check-target-ip-10-0-134-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:35:58Z"
    - latency: 2.388322ms
      message: 'network-check-target-ip-10-0-134-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:34:58Z"
    - latency: 2.001695ms
      message: 'network-check-target-ip-10-0-134-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:33:58Z"
    - latency: 2.122725ms
      message: 'network-check-target-ip-10-0-134-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:32:58Z"
    - latency: 2.148392ms
      message: 'network-check-target-ip-10-0-134-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:31:58Z"
    - latency: 1.954412ms
      message: 'network-check-target-ip-10-0-134-128: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:30:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T15:11:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-215-to-network-check-target-ip-10-0-134-20
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-215.ec2.internal
      uid: 1fa77dda-6ee7-4e01-b700-0ea8dcd63153
    resourceVersion: "58254"
    uid: ce169674-0470-4d48-a069-73fa79487b2f
  spec:
    sourcePod: network-check-source-6f8b768455-qm4lg
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T15:18:58Z"
      message: 'network-check-target-ip-10-0-134-20: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.105741ms
      message: 'network-check-target-ip-10-0-134-20: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:39:58Z"
    - latency: 2.370357ms
      message: 'network-check-target-ip-10-0-134-20: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:38:58Z"
    - latency: 2.359672ms
      message: 'network-check-target-ip-10-0-134-20: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:37:58Z"
    - latency: 2.168769ms
      message: 'network-check-target-ip-10-0-134-20: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:36:58Z"
    - latency: 2.039108ms
      message: 'network-check-target-ip-10-0-134-20: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:35:58Z"
    - latency: 2.276351ms
      message: 'network-check-target-ip-10-0-134-20: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:34:58Z"
    - latency: 2.419446ms
      message: 'network-check-target-ip-10-0-134-20: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:33:58Z"
    - latency: 2.235061ms
      message: 'network-check-target-ip-10-0-134-20: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:32:58Z"
    - latency: 2.356433ms
      message: 'network-check-target-ip-10-0-134-20: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:31:58Z"
    - latency: 2.167393ms
      message: 'network-check-target-ip-10-0-134-20: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:30:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T15:11:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-215-to-network-check-target-ip-10-0-138-215
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-215.ec2.internal
      uid: 1fa77dda-6ee7-4e01-b700-0ea8dcd63153
    resourceVersion: "58252"
    uid: 98b1c465-77df-4f91-963c-0a232a4d38b4
  spec:
    sourcePod: network-check-source-6f8b768455-qm4lg
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T15:18:58Z"
      message: 'network-check-target-ip-10-0-138-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.267331ms
      message: 'network-check-target-ip-10-0-138-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:39:58Z"
    - latency: 968.12µs
      message: 'network-check-target-ip-10-0-138-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:38:58Z"
    - latency: 1.271884ms
      message: 'network-check-target-ip-10-0-138-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:37:58Z"
    - latency: 1.456718ms
      message: 'network-check-target-ip-10-0-138-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:36:58Z"
    - latency: 913.931µs
      message: 'network-check-target-ip-10-0-138-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:35:58Z"
    - latency: 1.522037ms
      message: 'network-check-target-ip-10-0-138-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:34:58Z"
    - latency: 961.467µs
      message: 'network-check-target-ip-10-0-138-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:33:58Z"
    - latency: 1.632928ms
      message: 'network-check-target-ip-10-0-138-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:32:58Z"
    - latency: 1.00758ms
      message: 'network-check-target-ip-10-0-138-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:31:58Z"
    - latency: 1.232998ms
      message: 'network-check-target-ip-10-0-138-215: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:30:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T15:11:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-215-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-215.ec2.internal
      uid: 1fa77dda-6ee7-4e01-b700-0ea8dcd63153
    resourceVersion: "59984"
    uid: 411c2d0e-14a8-4693-a1ec-7f33afc4987a
  spec:
    sourcePod: network-check-source-6f8b768455-qm4lg
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T15:17:58Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 843.333µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:41:58Z"
    - latency: 1.671328ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T15:41:58Z"
    - latency: 891.385µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:40:58Z"
    - latency: 1.707636ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T15:40:58Z"
    - latency: 1.225681ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:39:58Z"
    - latency: 1.825056ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T15:39:58Z"
    - latency: 941.82µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:38:58Z"
    - latency: 1.865354ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T15:38:58Z"
    - latency: 956.593µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T15:37:58Z"
    - latency: 1.736098ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T15:37:58Z"
kind: List
metadata:
  resourceVersion: ""