apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T02:50:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-87-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-87.ec2.internal
      uid: 7c42c209-ff5e-4fdf-a93b-67197d2b595c
    resourceVersion: "31432"
    uid: 840ef769-7ad4-43c9-9c4a-6a924815406b
  spec:
    sourcePod: network-check-source-56d84b9f44-n6xxs
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T02:57:11Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.02178ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T03:04:11Z"
    - latency: 1.334043ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T03:03:11Z"
    - latency: 1.021139ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T03:02:11Z"
    - latency: 1.113391ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T03:01:11Z"
    - latency: 1.134482ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T03:00:11Z"
    - latency: 1.11682ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T02:59:11Z"
    - latency: 1.278119ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T02:58:11Z"
    - latency: 1.004291ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T02:57:11Z"
    - latency: 1.172824ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T02:56:11Z"
    - latency: 1.192434ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T02:55:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T02:50:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-87-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-87.ec2.internal
      uid: 7c42c209-ff5e-4fdf-a93b-67197d2b595c
    resourceVersion: "29521"
    uid: 297c4f1f-c6e2-4627-befb-47c9712522e1
  spec:
    sourcePod: network-check-source-56d84b9f44-n6xxs
    targetEndpoint: a7fdc7f412cb747a5aee1fbe7de7818c-c5342477208b74d8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T02:56:11Z"
      message: 'load-balancer-api-external: tcp connection to a7fdc7f412cb747a5aee1fbe7de7818c-c5342477208b74d8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.871194ms
      message: 'load-balancer-api-external: tcp connection to a7fdc7f412cb747a5aee1fbe7de7818c-c5342477208b74d8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T03:02:11Z"
    - latency: 9.639321ms
      message: 'load-balancer-api-external: resolved host name a7fdc7f412cb747a5aee1fbe7de7818c-c5342477208b74d8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T03:02:11Z"
    - latency: 4.983519ms
      message: 'load-balancer-api-external: tcp connection to a7fdc7f412cb747a5aee1fbe7de7818c-c5342477208b74d8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T03:01:11Z"
    - latency: 7.596476ms
      message: 'load-balancer-api-external: resolved host name a7fdc7f412cb747a5aee1fbe7de7818c-c5342477208b74d8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T03:01:11Z"
    - latency: 4.963163ms
      message: 'load-balancer-api-external: tcp connection to a7fdc7f412cb747a5aee1fbe7de7818c-c5342477208b74d8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T03:00:11Z"
    - latency: 8.444976ms
      message: 'load-balancer-api-external: resolved host name a7fdc7f412cb747a5aee1fbe7de7818c-c5342477208b74d8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T03:00:11Z"
    - latency: 5.156868ms
      message: 'load-balancer-api-external: tcp connection to a7fdc7f412cb747a5aee1fbe7de7818c-c5342477208b74d8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T02:59:11Z"
    - latency: 7.040964ms
      message: 'load-balancer-api-external: resolved host name a7fdc7f412cb747a5aee1fbe7de7818c-c5342477208b74d8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T02:59:11Z"
    - latency: 3.766578ms
      message: 'load-balancer-api-external: tcp connection to a7fdc7f412cb747a5aee1fbe7de7818c-c5342477208b74d8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T02:58:11Z"
    - latency: 7.108952ms
      message: 'load-balancer-api-external: resolved host name a7fdc7f412cb747a5aee1fbe7de7818c-c5342477208b74d8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T02:58:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T02:50:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-87-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-87.ec2.internal
      uid: 7c42c209-ff5e-4fdf-a93b-67197d2b595c
    resourceVersion: "29520"
    uid: ab4c02ce-6cc1-4dd0-adf8-13a7caaf3224
  spec:
    sourcePod: network-check-source-56d84b9f44-n6xxs
    targetEndpoint: a7fdc7f412cb747a5aee1fbe7de7818c-c5342477208b74d8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T02:56:11Z"
      message: 'load-balancer-api-internal: tcp connection to a7fdc7f412cb747a5aee1fbe7de7818c-c5342477208b74d8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.808936ms
      message: 'load-balancer-api-internal: tcp connection to a7fdc7f412cb747a5aee1fbe7de7818c-c5342477208b74d8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T03:02:11Z"
    - latency: 9.596026ms
      message: 'load-balancer-api-internal: resolved host name a7fdc7f412cb747a5aee1fbe7de7818c-c5342477208b74d8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T03:02:11Z"
    - latency: 5.014796ms
      message: 'load-balancer-api-internal: tcp connection to a7fdc7f412cb747a5aee1fbe7de7818c-c5342477208b74d8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T03:01:11Z"
    - latency: 7.567983ms
      message: 'load-balancer-api-internal: resolved host name a7fdc7f412cb747a5aee1fbe7de7818c-c5342477208b74d8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T03:01:11Z"
    - latency: 5.060642ms
      message: 'load-balancer-api-internal: tcp connection to a7fdc7f412cb747a5aee1fbe7de7818c-c5342477208b74d8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T03:00:11Z"
    - latency: 8.389769ms
      message: 'load-balancer-api-internal: resolved host name a7fdc7f412cb747a5aee1fbe7de7818c-c5342477208b74d8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T03:00:11Z"
    - latency: 5.1428ms
      message: 'load-balancer-api-internal: tcp connection to a7fdc7f412cb747a5aee1fbe7de7818c-c5342477208b74d8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T02:59:11Z"
    - latency: 6.993939ms
      message: 'load-balancer-api-internal: resolved host name a7fdc7f412cb747a5aee1fbe7de7818c-c5342477208b74d8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T02:59:11Z"
    - latency: 3.824791ms
      message: 'load-balancer-api-internal: tcp connection to a7fdc7f412cb747a5aee1fbe7de7818c-c5342477208b74d8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T02:58:11Z"
    - latency: 7.076111ms
      message: 'load-balancer-api-internal: resolved host name a7fdc7f412cb747a5aee1fbe7de7818c-c5342477208b74d8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T02:58:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T02:50:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-87-to-network-check-target-ip-10-0-129-101
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-87.ec2.internal
      uid: 7c42c209-ff5e-4fdf-a93b-67197d2b595c
    resourceVersion: "31431"
    uid: 73a5bc5a-1753-468e-8176-405589289f23
  spec:
    sourcePod: network-check-source-56d84b9f44-n6xxs
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T02:57:11Z"
      message: 'network-check-target-ip-10-0-129-101: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.050246ms
      message: 'network-check-target-ip-10-0-129-101: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T03:04:11Z"
    - latency: 2.072489ms
      message: 'network-check-target-ip-10-0-129-101: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T03:03:11Z"
    - latency: 2.41669ms
      message: 'network-check-target-ip-10-0-129-101: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T03:02:11Z"
    - latency: 2.186977ms
      message: 'network-check-target-ip-10-0-129-101: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T03:01:11Z"
    - latency: 2.049166ms
      message: 'network-check-target-ip-10-0-129-101: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T03:00:11Z"
    - latency: 1.815403ms
      message: 'network-check-target-ip-10-0-129-101: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T02:59:11Z"
    - latency: 2.217091ms
      message: 'network-check-target-ip-10-0-129-101: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T02:58:11Z"
    - latency: 2.508217ms
      message: 'network-check-target-ip-10-0-129-101: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T02:57:11Z"
    - latency: 2.347694ms
      message: 'network-check-target-ip-10-0-129-101: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T02:56:11Z"
    - latency: 2.176728ms
      message: 'network-check-target-ip-10-0-129-101: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T02:55:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T02:50:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-87-to-network-check-target-ip-10-0-138-19
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-87.ec2.internal
      uid: 7c42c209-ff5e-4fdf-a93b-67197d2b595c
    resourceVersion: "31430"
    uid: 3f72742d-e1aa-49dd-bc58-abdbf9d0fbcd
  spec:
    sourcePod: network-check-source-56d84b9f44-n6xxs
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T02:57:11Z"
      message: 'network-check-target-ip-10-0-138-19: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.813199ms
      message: 'network-check-target-ip-10-0-138-19: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T03:04:11Z"
    - latency: 2.035637ms
      message: 'network-check-target-ip-10-0-138-19: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T03:03:11Z"
    - latency: 2.198014ms
      message: 'network-check-target-ip-10-0-138-19: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T03:02:11Z"
    - latency: 2.150304ms
      message: 'network-check-target-ip-10-0-138-19: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T03:01:11Z"
    - latency: 1.963807ms
      message: 'network-check-target-ip-10-0-138-19: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T03:00:11Z"
    - latency: 2.094937ms
      message: 'network-check-target-ip-10-0-138-19: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T02:59:11Z"
    - latency: 1.751865ms
      message: 'network-check-target-ip-10-0-138-19: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T02:58:11Z"
    - latency: 2.506961ms
      message: 'network-check-target-ip-10-0-138-19: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T02:57:11Z"
    - latency: 2.474935ms
      message: 'network-check-target-ip-10-0-138-19: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T02:56:11Z"
    - latency: 1.943079ms
      message: 'network-check-target-ip-10-0-138-19: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T02:55:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T02:50:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-87-to-network-check-target-ip-10-0-139-87
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-87.ec2.internal
      uid: 7c42c209-ff5e-4fdf-a93b-67197d2b595c
    resourceVersion: "31429"
    uid: 1787aa56-49e4-42ae-bc69-d8d348dbefa5
  spec:
    sourcePod: network-check-source-56d84b9f44-n6xxs
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T02:57:11Z"
      message: 'network-check-target-ip-10-0-139-87: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 960.103µs
      message: 'network-check-target-ip-10-0-139-87: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T03:04:11Z"
    - latency: 1.486425ms
      message: 'network-check-target-ip-10-0-139-87: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T03:03:11Z"
    - latency: 1.031538ms
      message: 'network-check-target-ip-10-0-139-87: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T03:02:11Z"
    - latency: 809.249µs
      message: 'network-check-target-ip-10-0-139-87: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T03:01:11Z"
    - latency: 906.545µs
      message: 'network-check-target-ip-10-0-139-87: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T03:00:11Z"
    - latency: 1.00173ms
      message: 'network-check-target-ip-10-0-139-87: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T02:59:11Z"
    - latency: 1.532964ms
      message: 'network-check-target-ip-10-0-139-87: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T02:58:11Z"
    - latency: 1.628115ms
      message: 'network-check-target-ip-10-0-139-87: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T02:57:11Z"
    - latency: 1.307189ms
      message: 'network-check-target-ip-10-0-139-87: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T02:56:11Z"
    - latency: 968.244µs
      message: 'network-check-target-ip-10-0-139-87: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T02:55:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T02:50:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-87-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-87.ec2.internal
      uid: 7c42c209-ff5e-4fdf-a93b-67197d2b595c
    resourceVersion: "29518"
    uid: 7f5a986d-0b86-4a1e-8ba9-629836571f18
  spec:
    sourcePod: network-check-source-56d84b9f44-n6xxs
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T02:56:11Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 922.093µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T03:02:11Z"
    - latency: 1.897725ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T03:02:11Z"
    - latency: 1.020709ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T03:01:11Z"
    - latency: 1.960364ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T03:01:11Z"
    - latency: 758.443µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T03:00:11Z"
    - latency: 2.525388ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T03:00:11Z"
    - latency: 1.001186ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T02:59:11Z"
    - latency: 1.652187ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T02:59:11Z"
    - latency: 1.075911ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T02:58:11Z"
    - latency: 1.667758ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T02:58:11Z"
kind: List
metadata:
  resourceVersion: ""