apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T13:20:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-111-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-111.ec2.internal
      uid: 99ca24db-6754-4877-9d17-8cfc4dec3600
    resourceVersion: "22116"
    uid: 80e2beb4-dad5-4a7a-b249-3cb2346ed86c
  spec:
    sourcePod: network-check-source-56499946bc-42xgd
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T13:27:10Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 967.09µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:41:10Z"
    - latency: 1.216809ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:40:10Z"
    - latency: 902.736µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:39:10Z"
    - latency: 956.098µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:38:10Z"
    - latency: 1.021448ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:37:10Z"
    - latency: 1.150004ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:36:10Z"
    - latency: 1.201968ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:35:10Z"
    - latency: 935.259µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:34:10Z"
    - latency: 914.411µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:33:10Z"
    - latency: 967.707µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:32:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T13:20:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-111-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-111.ec2.internal
      uid: 99ca24db-6754-4877-9d17-8cfc4dec3600
    resourceVersion: "20591"
    uid: c80cd5ce-4ef7-40ae-a65c-8f79970f1fd3
  spec:
    sourcePod: network-check-source-56499946bc-42xgd
    targetEndpoint: ae5bf3b438d084602894fcda5ff98ff5-7528034784e3fb56.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T13:26:10Z"
      message: 'load-balancer-api-external: tcp connection to ae5bf3b438d084602894fcda5ff98ff5-7528034784e3fb56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.874718ms
      message: 'load-balancer-api-external: tcp connection to ae5bf3b438d084602894fcda5ff98ff5-7528034784e3fb56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:38:10Z"
    - latency: 8.652636ms
      message: 'load-balancer-api-external: resolved host name ae5bf3b438d084602894fcda5ff98ff5-7528034784e3fb56.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:38:10Z"
    - latency: 5.918814ms
      message: 'load-balancer-api-external: tcp connection to ae5bf3b438d084602894fcda5ff98ff5-7528034784e3fb56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:37:10Z"
    - latency: 8.34738ms
      message: 'load-balancer-api-external: resolved host name ae5bf3b438d084602894fcda5ff98ff5-7528034784e3fb56.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:37:10Z"
    - latency: 6.14103ms
      message: 'load-balancer-api-external: tcp connection to ae5bf3b438d084602894fcda5ff98ff5-7528034784e3fb56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:36:10Z"
    - latency: 9.023315ms
      message: 'load-balancer-api-external: resolved host name ae5bf3b438d084602894fcda5ff98ff5-7528034784e3fb56.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:36:10Z"
    - latency: 7.561744ms
      message: 'load-balancer-api-external: tcp connection to ae5bf3b438d084602894fcda5ff98ff5-7528034784e3fb56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:35:10Z"
    - latency: 8.319613ms
      message: 'load-balancer-api-external: resolved host name ae5bf3b438d084602894fcda5ff98ff5-7528034784e3fb56.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:35:10Z"
    - latency: 6.960378ms
      message: 'load-balancer-api-external: tcp connection to ae5bf3b438d084602894fcda5ff98ff5-7528034784e3fb56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:34:10Z"
    - latency: 9.048324ms
      message: 'load-balancer-api-external: resolved host name ae5bf3b438d084602894fcda5ff98ff5-7528034784e3fb56.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:34:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T13:20:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-111-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-111.ec2.internal
      uid: 99ca24db-6754-4877-9d17-8cfc4dec3600
    resourceVersion: "20592"
    uid: 27e34d8d-801b-439f-9819-ad592ade0795
  spec:
    sourcePod: network-check-source-56499946bc-42xgd
    targetEndpoint: ae5bf3b438d084602894fcda5ff98ff5-7528034784e3fb56.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T13:26:10Z"
      message: 'load-balancer-api-internal: tcp connection to ae5bf3b438d084602894fcda5ff98ff5-7528034784e3fb56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.869653ms
      message: 'load-balancer-api-internal: tcp connection to ae5bf3b438d084602894fcda5ff98ff5-7528034784e3fb56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:38:10Z"
    - latency: 8.736195ms
      message: 'load-balancer-api-internal: resolved host name ae5bf3b438d084602894fcda5ff98ff5-7528034784e3fb56.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:38:10Z"
    - latency: 5.978407ms
      message: 'load-balancer-api-internal: tcp connection to ae5bf3b438d084602894fcda5ff98ff5-7528034784e3fb56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:37:10Z"
    - latency: 8.18131ms
      message: 'load-balancer-api-internal: resolved host name ae5bf3b438d084602894fcda5ff98ff5-7528034784e3fb56.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:37:10Z"
    - latency: 6.820101ms
      message: 'load-balancer-api-internal: tcp connection to ae5bf3b438d084602894fcda5ff98ff5-7528034784e3fb56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:36:10Z"
    - latency: 8.864711ms
      message: 'load-balancer-api-internal: resolved host name ae5bf3b438d084602894fcda5ff98ff5-7528034784e3fb56.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:36:10Z"
    - latency: 3.900623ms
      message: 'load-balancer-api-internal: tcp connection to ae5bf3b438d084602894fcda5ff98ff5-7528034784e3fb56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:35:10Z"
    - latency: 8.184722ms
      message: 'load-balancer-api-internal: resolved host name ae5bf3b438d084602894fcda5ff98ff5-7528034784e3fb56.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:35:10Z"
    - latency: 6.154458ms
      message: 'load-balancer-api-internal: tcp connection to ae5bf3b438d084602894fcda5ff98ff5-7528034784e3fb56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:34:10Z"
    - latency: 9.119198ms
      message: 'load-balancer-api-internal: resolved host name ae5bf3b438d084602894fcda5ff98ff5-7528034784e3fb56.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:34:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T13:20:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-111-to-network-check-target-ip-10-0-130-179
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-111.ec2.internal
      uid: 99ca24db-6754-4877-9d17-8cfc4dec3600
    resourceVersion: "22114"
    uid: 27df2246-bfd8-4922-ae06-b470f6586d61
  spec:
    sourcePod: network-check-source-56499946bc-42xgd
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T13:27:10Z"
      message: 'network-check-target-ip-10-0-130-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.244847ms
      message: 'network-check-target-ip-10-0-130-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:41:10Z"
    - latency: 2.335781ms
      message: 'network-check-target-ip-10-0-130-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:40:10Z"
    - latency: 2.29875ms
      message: 'network-check-target-ip-10-0-130-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:39:10Z"
    - latency: 2.403868ms
      message: 'network-check-target-ip-10-0-130-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:38:10Z"
    - latency: 2.551696ms
      message: 'network-check-target-ip-10-0-130-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:37:10Z"
    - latency: 2.311644ms
      message: 'network-check-target-ip-10-0-130-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:36:10Z"
    - latency: 2.151163ms
      message: 'network-check-target-ip-10-0-130-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:35:10Z"
    - latency: 2.244989ms
      message: 'network-check-target-ip-10-0-130-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:34:10Z"
    - latency: 2.379024ms
      message: 'network-check-target-ip-10-0-130-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:33:10Z"
    - latency: 2.05817ms
      message: 'network-check-target-ip-10-0-130-179: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:32:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T13:20:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-111-to-network-check-target-ip-10-0-133-111
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-111.ec2.internal
      uid: 99ca24db-6754-4877-9d17-8cfc4dec3600
    resourceVersion: "22113"
    uid: 3f39f676-d473-4f82-9b89-aaac899f6650
  spec:
    sourcePod: network-check-source-56499946bc-42xgd
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T13:27:10Z"
      message: 'network-check-target-ip-10-0-133-111: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 990.999µs
      message: 'network-check-target-ip-10-0-133-111: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:41:10Z"
    - latency: 910.117µs
      message: 'network-check-target-ip-10-0-133-111: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:40:10Z"
    - latency: 972.134µs
      message: 'network-check-target-ip-10-0-133-111: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:39:10Z"
    - latency: 858.001µs
      message: 'network-check-target-ip-10-0-133-111: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:38:10Z"
    - latency: 871.839µs
      message: 'network-check-target-ip-10-0-133-111: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:37:10Z"
    - latency: 947.587µs
      message: 'network-check-target-ip-10-0-133-111: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:36:10Z"
    - latency: 909.503µs
      message: 'network-check-target-ip-10-0-133-111: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:35:10Z"
    - latency: 1.330599ms
      message: 'network-check-target-ip-10-0-133-111: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:34:10Z"
    - latency: 879.559µs
      message: 'network-check-target-ip-10-0-133-111: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:33:10Z"
    - latency: 964.347µs
      message: 'network-check-target-ip-10-0-133-111: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:32:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T13:20:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-111-to-network-check-target-ip-10-0-134-102
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-111.ec2.internal
      uid: 99ca24db-6754-4877-9d17-8cfc4dec3600
    resourceVersion: "22115"
    uid: 84858b9e-c137-4a3e-bfca-bc62280bc458
  spec:
    sourcePod: network-check-source-56499946bc-42xgd
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T13:27:10Z"
      message: 'network-check-target-ip-10-0-134-102: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.175784ms
      message: 'network-check-target-ip-10-0-134-102: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:41:10Z"
    - latency: 2.019394ms
      message: 'network-check-target-ip-10-0-134-102: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:40:10Z"
    - latency: 2.131601ms
      message: 'network-check-target-ip-10-0-134-102: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:39:10Z"
    - latency: 2.149412ms
      message: 'network-check-target-ip-10-0-134-102: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:38:10Z"
    - latency: 2.263772ms
      message: 'network-check-target-ip-10-0-134-102: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:37:10Z"
    - latency: 2.329686ms
      message: 'network-check-target-ip-10-0-134-102: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:36:10Z"
    - latency: 2.447091ms
      message: 'network-check-target-ip-10-0-134-102: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:35:10Z"
    - latency: 2.913963ms
      message: 'network-check-target-ip-10-0-134-102: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:34:10Z"
    - latency: 2.404088ms
      message: 'network-check-target-ip-10-0-134-102: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:33:10Z"
    - latency: 2.244752ms
      message: 'network-check-target-ip-10-0-134-102: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:32:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T13:20:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-111-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-111.ec2.internal
      uid: 99ca24db-6754-4877-9d17-8cfc4dec3600
    resourceVersion: "20590"
    uid: ff7281fb-79dc-4a17-91ea-c3872825123e
  spec:
    sourcePod: network-check-source-56499946bc-42xgd
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T13:26:10Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 760.959µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:38:10Z"
    - latency: 1.704902ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:38:10Z"
    - latency: 743.172µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:37:10Z"
    - latency: 1.693974ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:37:10Z"
    - latency: 1.165913ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:36:10Z"
    - latency: 2.005419ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:36:10Z"
    - latency: 856.332µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:35:10Z"
    - latency: 1.780105ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:35:10Z"
    - latency: 798.92µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:34:10Z"
    - latency: 1.752701ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:34:10Z"
kind: List
metadata:
  resourceVersion: ""