apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T22:48:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-222-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-222.ec2.internal
      uid: 7a84684b-401c-4b64-9a73-ef579b9fe1e1
    resourceVersion: "16431"
    uid: 115095e9-1d85-4af8-813f-c18a202a8c4a
  spec:
    sourcePod: network-check-source-7d88cb55d8-2gjzh
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T22:55:59Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.036283ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T23:02:59Z"
    - latency: 1.062361ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T23:01:59Z"
    - latency: 966.335µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T23:00:59Z"
    - latency: 947.675µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:59:59Z"
    - latency: 1.26727ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:58:59Z"
    - latency: 1.105266ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:57:59Z"
    - latency: 925.504µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:56:59Z"
    - latency: 919.123µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:55:59Z"
    - latency: 963.732µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:54:59Z"
    - latency: 909.547µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:53:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T22:48:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-222-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-222.ec2.internal
      uid: 7a84684b-401c-4b64-9a73-ef579b9fe1e1
    resourceVersion: "15742"
    uid: b7aecc5b-f910-4d59-a980-42ad47c797e3
  spec:
    sourcePod: network-check-source-7d88cb55d8-2gjzh
    targetEndpoint: a27a2b4b9d6fb4f2dba3a56a60eafe1f-a183f327485a4b23.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T22:54:59Z"
      message: 'load-balancer-api-external: tcp connection to a27a2b4b9d6fb4f2dba3a56a60eafe1f-a183f327485a4b23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.956576ms
      message: 'load-balancer-api-external: tcp connection to a27a2b4b9d6fb4f2dba3a56a60eafe1f-a183f327485a4b23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T23:00:59Z"
    - latency: 7.711779ms
      message: 'load-balancer-api-external: resolved host name a27a2b4b9d6fb4f2dba3a56a60eafe1f-a183f327485a4b23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T23:00:59Z"
    - latency: 3.33549ms
      message: 'load-balancer-api-external: tcp connection to a27a2b4b9d6fb4f2dba3a56a60eafe1f-a183f327485a4b23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:59:59Z"
    - latency: 7.464243ms
      message: 'load-balancer-api-external: resolved host name a27a2b4b9d6fb4f2dba3a56a60eafe1f-a183f327485a4b23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T22:59:59Z"
    - latency: 3.517622ms
      message: 'load-balancer-api-external: tcp connection to a27a2b4b9d6fb4f2dba3a56a60eafe1f-a183f327485a4b23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:58:59Z"
    - latency: 11.622553ms
      message: 'load-balancer-api-external: resolved host name a27a2b4b9d6fb4f2dba3a56a60eafe1f-a183f327485a4b23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T22:58:59Z"
    - latency: 4.338646ms
      message: 'load-balancer-api-external: tcp connection to a27a2b4b9d6fb4f2dba3a56a60eafe1f-a183f327485a4b23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:57:59Z"
    - latency: 9.220071ms
      message: 'load-balancer-api-external: resolved host name a27a2b4b9d6fb4f2dba3a56a60eafe1f-a183f327485a4b23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T22:57:59Z"
    - latency: 4.790059ms
      message: 'load-balancer-api-external: tcp connection to a27a2b4b9d6fb4f2dba3a56a60eafe1f-a183f327485a4b23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:56:59Z"
    - latency: 15.834466ms
      message: 'load-balancer-api-external: resolved host name a27a2b4b9d6fb4f2dba3a56a60eafe1f-a183f327485a4b23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T22:56:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T22:48:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-222-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-222.ec2.internal
      uid: 7a84684b-401c-4b64-9a73-ef579b9fe1e1
    resourceVersion: "15741"
    uid: e18abaa7-689b-403c-b9c1-c49d9e2fc0ac
  spec:
    sourcePod: network-check-source-7d88cb55d8-2gjzh
    targetEndpoint: a27a2b4b9d6fb4f2dba3a56a60eafe1f-a183f327485a4b23.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T22:54:59Z"
      message: 'load-balancer-api-internal: tcp connection to a27a2b4b9d6fb4f2dba3a56a60eafe1f-a183f327485a4b23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.965725ms
      message: 'load-balancer-api-internal: tcp connection to a27a2b4b9d6fb4f2dba3a56a60eafe1f-a183f327485a4b23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T23:00:59Z"
    - latency: 7.782223ms
      message: 'load-balancer-api-internal: resolved host name a27a2b4b9d6fb4f2dba3a56a60eafe1f-a183f327485a4b23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T23:00:59Z"
    - latency: 3.925045ms
      message: 'load-balancer-api-internal: tcp connection to a27a2b4b9d6fb4f2dba3a56a60eafe1f-a183f327485a4b23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:59:59Z"
    - latency: 7.533653ms
      message: 'load-balancer-api-internal: resolved host name a27a2b4b9d6fb4f2dba3a56a60eafe1f-a183f327485a4b23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T22:59:59Z"
    - latency: 4.115314ms
      message: 'load-balancer-api-internal: tcp connection to a27a2b4b9d6fb4f2dba3a56a60eafe1f-a183f327485a4b23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:58:59Z"
    - latency: 11.685127ms
      message: 'load-balancer-api-internal: resolved host name a27a2b4b9d6fb4f2dba3a56a60eafe1f-a183f327485a4b23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T22:58:59Z"
    - latency: 4.320413ms
      message: 'load-balancer-api-internal: tcp connection to a27a2b4b9d6fb4f2dba3a56a60eafe1f-a183f327485a4b23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:57:59Z"
    - latency: 9.277346ms
      message: 'load-balancer-api-internal: resolved host name a27a2b4b9d6fb4f2dba3a56a60eafe1f-a183f327485a4b23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T22:57:59Z"
    - latency: 4.806411ms
      message: 'load-balancer-api-internal: tcp connection to a27a2b4b9d6fb4f2dba3a56a60eafe1f-a183f327485a4b23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:56:59Z"
    - latency: 15.889444ms
      message: 'load-balancer-api-internal: resolved host name a27a2b4b9d6fb4f2dba3a56a60eafe1f-a183f327485a4b23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T22:56:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T22:48:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-222-to-network-check-target-ip-10-0-130-222
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-222.ec2.internal
      uid: 7a84684b-401c-4b64-9a73-ef579b9fe1e1
    resourceVersion: "16428"
    uid: 9875399a-1993-4057-9930-7a47e3842713
  spec:
    sourcePod: network-check-source-7d88cb55d8-2gjzh
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T22:55:59Z"
      message: 'network-check-target-ip-10-0-130-222: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.362903ms
      message: 'network-check-target-ip-10-0-130-222: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T23:02:59Z"
    - latency: 830.622µs
      message: 'network-check-target-ip-10-0-130-222: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T23:01:59Z"
    - latency: 923.11µs
      message: 'network-check-target-ip-10-0-130-222: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T23:00:59Z"
    - latency: 980.994µs
      message: 'network-check-target-ip-10-0-130-222: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:59:59Z"
    - latency: 872.057µs
      message: 'network-check-target-ip-10-0-130-222: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:58:59Z"
    - latency: 1.010267ms
      message: 'network-check-target-ip-10-0-130-222: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:57:59Z"
    - latency: 1.004001ms
      message: 'network-check-target-ip-10-0-130-222: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:56:59Z"
    - latency: 1.180898ms
      message: 'network-check-target-ip-10-0-130-222: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:55:59Z"
    - latency: 1.024054ms
      message: 'network-check-target-ip-10-0-130-222: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:54:59Z"
    - latency: 894.179µs
      message: 'network-check-target-ip-10-0-130-222: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:53:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T22:48:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-222-to-network-check-target-ip-10-0-130-247
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-222.ec2.internal
      uid: 7a84684b-401c-4b64-9a73-ef579b9fe1e1
    resourceVersion: "16430"
    uid: 35291fab-f4c7-4e8e-86b7-04b66ac7b8f6
  spec:
    sourcePod: network-check-source-7d88cb55d8-2gjzh
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T22:55:59Z"
      message: 'network-check-target-ip-10-0-130-247: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.56964ms
      message: 'network-check-target-ip-10-0-130-247: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T23:02:59Z"
    - latency: 2.284477ms
      message: 'network-check-target-ip-10-0-130-247: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T23:01:59Z"
    - latency: 2.257722ms
      message: 'network-check-target-ip-10-0-130-247: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T23:00:59Z"
    - latency: 2.353856ms
      message: 'network-check-target-ip-10-0-130-247: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:59:59Z"
    - latency: 2.343439ms
      message: 'network-check-target-ip-10-0-130-247: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:58:59Z"
    - latency: 2.362973ms
      message: 'network-check-target-ip-10-0-130-247: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:57:59Z"
    - latency: 2.422621ms
      message: 'network-check-target-ip-10-0-130-247: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:56:59Z"
    - latency: 2.361685ms
      message: 'network-check-target-ip-10-0-130-247: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:55:59Z"
    - latency: 2.304441ms
      message: 'network-check-target-ip-10-0-130-247: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:54:59Z"
    - latency: 2.112201ms
      message: 'network-check-target-ip-10-0-130-247: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:53:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T22:48:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-222-to-network-check-target-ip-10-0-137-81
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-222.ec2.internal
      uid: 7a84684b-401c-4b64-9a73-ef579b9fe1e1
    resourceVersion: "16429"
    uid: 6500f0fa-55e2-4dcb-a7dc-05fdf217c598
  spec:
    sourcePod: network-check-source-7d88cb55d8-2gjzh
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T22:55:59Z"
      message: 'network-check-target-ip-10-0-137-81: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.10797ms
      message: 'network-check-target-ip-10-0-137-81: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T23:02:59Z"
    - latency: 2.460134ms
      message: 'network-check-target-ip-10-0-137-81: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T23:01:59Z"
    - latency: 1.966792ms
      message: 'network-check-target-ip-10-0-137-81: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T23:00:59Z"
    - latency: 2.293074ms
      message: 'network-check-target-ip-10-0-137-81: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:59:59Z"
    - latency: 2.155777ms
      message: 'network-check-target-ip-10-0-137-81: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:58:59Z"
    - latency: 2.420652ms
      message: 'network-check-target-ip-10-0-137-81: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:57:59Z"
    - latency: 2.241852ms
      message: 'network-check-target-ip-10-0-137-81: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:56:59Z"
    - latency: 2.268954ms
      message: 'network-check-target-ip-10-0-137-81: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:55:59Z"
    - latency: 2.394322ms
      message: 'network-check-target-ip-10-0-137-81: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:54:59Z"
    - latency: 2.27982ms
      message: 'network-check-target-ip-10-0-137-81: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:53:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T22:48:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-222-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-222.ec2.internal
      uid: 7a84684b-401c-4b64-9a73-ef579b9fe1e1
    resourceVersion: "15740"
    uid: 087c1039-4f58-4ea5-aa68-4c23cbc7121c
  spec:
    sourcePod: network-check-source-7d88cb55d8-2gjzh
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T22:54:59Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 898.927µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T23:00:59Z"
    - latency: 1.691124ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T23:00:59Z"
    - latency: 814.773µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:59:59Z"
    - latency: 1.566992ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T22:59:59Z"
    - latency: 989.257µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:58:59Z"
    - latency: 2.124114ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T22:58:59Z"
    - latency: 763.354µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:57:59Z"
    - latency: 1.52163ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T22:57:59Z"
    - latency: 880.509µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T22:56:59Z"
    - latency: 1.73183ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T22:56:59Z"
kind: List
metadata:
  resourceVersion: ""