apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T00:45:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-169-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-169.ec2.internal
      uid: 60e518de-6650-44f7-bbaf-916f27806b07
    resourceVersion: "138967"
    uid: 25160ef8-45af-4706-be2c-74ea4c1a6aa4
  spec:
    sourcePod: network-check-source-6f78d59f99-fkqq5
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T00:52:16Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.556535ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:41:16Z"
    - latency: 1.055265ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:40:16Z"
    - latency: 1.072069ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:39:16Z"
    - latency: 1.357913ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:38:16Z"
    - latency: 1.029343ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:37:16Z"
    - latency: 1.127545ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:36:16Z"
    - latency: 1.725479ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:35:16Z"
    - latency: 1.340988ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:34:16Z"
    - latency: 7.800451ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:33:16Z"
    - latency: 2.065667ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:32:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T00:45:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-169-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-169.ec2.internal
      uid: 60e518de-6650-44f7-bbaf-916f27806b07
    resourceVersion: "143348"
    uid: 4651527c-a6a0-4c0e-9ead-afc7df5aeaa0
  spec:
    sourcePod: network-check-source-6f78d59f99-fkqq5
    targetEndpoint: a1fc8c24b7a3247cb8a3414f48925440-f66bb235af0cdc67.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T00:51:16Z"
      message: 'load-balancer-api-external: tcp connection to a1fc8c24b7a3247cb8a3414f48925440-f66bb235af0cdc67.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 15.575649ms
      message: 'load-balancer-api-external: tcp connection to a1fc8c24b7a3247cb8a3414f48925440-f66bb235af0cdc67.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:45:16Z"
    - latency: 6.833745ms
      message: 'load-balancer-api-external: resolved host name a1fc8c24b7a3247cb8a3414f48925440-f66bb235af0cdc67.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T01:45:16Z"
    - latency: 27.455755ms
      message: 'load-balancer-api-external: tcp connection to a1fc8c24b7a3247cb8a3414f48925440-f66bb235af0cdc67.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:44:16Z"
    - latency: 7.081375ms
      message: 'load-balancer-api-external: resolved host name a1fc8c24b7a3247cb8a3414f48925440-f66bb235af0cdc67.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T01:44:16Z"
    - latency: 34.220173ms
      message: 'load-balancer-api-external: tcp connection to a1fc8c24b7a3247cb8a3414f48925440-f66bb235af0cdc67.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:43:16Z"
    - latency: 21.519217ms
      message: 'load-balancer-api-external: resolved host name a1fc8c24b7a3247cb8a3414f48925440-f66bb235af0cdc67.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T01:43:16Z"
    - latency: 13.862616ms
      message: 'load-balancer-api-external: tcp connection to a1fc8c24b7a3247cb8a3414f48925440-f66bb235af0cdc67.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:42:16Z"
    - latency: 8.15875ms
      message: 'load-balancer-api-external: resolved host name a1fc8c24b7a3247cb8a3414f48925440-f66bb235af0cdc67.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T01:42:16Z"
    - latency: 16.721069ms
      message: 'load-balancer-api-external: tcp connection to a1fc8c24b7a3247cb8a3414f48925440-f66bb235af0cdc67.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:41:16Z"
    - latency: 7.251539ms
      message: 'load-balancer-api-external: resolved host name a1fc8c24b7a3247cb8a3414f48925440-f66bb235af0cdc67.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T01:41:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T00:45:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-169-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-169.ec2.internal
      uid: 60e518de-6650-44f7-bbaf-916f27806b07
    resourceVersion: "143349"
    uid: 08d307f7-3258-4d19-b3a9-5b24f532ede7
  spec:
    sourcePod: network-check-source-6f78d59f99-fkqq5
    targetEndpoint: a1fc8c24b7a3247cb8a3414f48925440-f66bb235af0cdc67.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T00:51:16Z"
      message: 'load-balancer-api-internal: tcp connection to a1fc8c24b7a3247cb8a3414f48925440-f66bb235af0cdc67.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 15.591794ms
      message: 'load-balancer-api-internal: tcp connection to a1fc8c24b7a3247cb8a3414f48925440-f66bb235af0cdc67.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:45:16Z"
    - latency: 6.890744ms
      message: 'load-balancer-api-internal: resolved host name a1fc8c24b7a3247cb8a3414f48925440-f66bb235af0cdc67.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T01:45:16Z"
    - latency: 15.735539ms
      message: 'load-balancer-api-internal: tcp connection to a1fc8c24b7a3247cb8a3414f48925440-f66bb235af0cdc67.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:44:16Z"
    - latency: 7.115397ms
      message: 'load-balancer-api-internal: resolved host name a1fc8c24b7a3247cb8a3414f48925440-f66bb235af0cdc67.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T01:44:16Z"
    - latency: 32.808201ms
      message: 'load-balancer-api-internal: tcp connection to a1fc8c24b7a3247cb8a3414f48925440-f66bb235af0cdc67.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:43:16Z"
    - latency: 21.811784ms
      message: 'load-balancer-api-internal: resolved host name a1fc8c24b7a3247cb8a3414f48925440-f66bb235af0cdc67.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T01:43:16Z"
    - latency: 15.650661ms
      message: 'load-balancer-api-internal: tcp connection to a1fc8c24b7a3247cb8a3414f48925440-f66bb235af0cdc67.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:42:16Z"
    - latency: 8.192466ms
      message: 'load-balancer-api-internal: resolved host name a1fc8c24b7a3247cb8a3414f48925440-f66bb235af0cdc67.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T01:42:16Z"
    - latency: 15.830606ms
      message: 'load-balancer-api-internal: tcp connection to a1fc8c24b7a3247cb8a3414f48925440-f66bb235af0cdc67.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:41:16Z"
    - latency: 7.285864ms
      message: 'load-balancer-api-internal: resolved host name a1fc8c24b7a3247cb8a3414f48925440-f66bb235af0cdc67.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T01:41:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T00:45:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-169-to-network-check-target-ip-10-0-130-169
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-169.ec2.internal
      uid: 60e518de-6650-44f7-bbaf-916f27806b07
    resourceVersion: "138963"
    uid: 1ce1348d-f538-4635-aa31-8d1ad0fbc288
  spec:
    sourcePod: network-check-source-6f78d59f99-fkqq5
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T00:52:16Z"
      message: 'network-check-target-ip-10-0-130-169: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.208425ms
      message: 'network-check-target-ip-10-0-130-169: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:41:16Z"
    - latency: 1.305738ms
      message: 'network-check-target-ip-10-0-130-169: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:40:16Z"
    - latency: 1.439321ms
      message: 'network-check-target-ip-10-0-130-169: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:39:16Z"
    - latency: 1.569998ms
      message: 'network-check-target-ip-10-0-130-169: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:38:16Z"
    - latency: 932.471µs
      message: 'network-check-target-ip-10-0-130-169: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:37:16Z"
    - latency: 1.020723ms
      message: 'network-check-target-ip-10-0-130-169: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:36:16Z"
    - latency: 1.909777ms
      message: 'network-check-target-ip-10-0-130-169: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:35:16Z"
    - latency: 1.802486ms
      message: 'network-check-target-ip-10-0-130-169: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:34:16Z"
    - latency: 5.444142ms
      message: 'network-check-target-ip-10-0-130-169: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:33:16Z"
    - latency: 1.160781ms
      message: 'network-check-target-ip-10-0-130-169: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:32:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T00:45:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-169-to-network-check-target-ip-10-0-140-206
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-169.ec2.internal
      uid: 60e518de-6650-44f7-bbaf-916f27806b07
    resourceVersion: "138964"
    uid: 7b1501cc-ebed-4dbb-9bc1-48ee2fd8c58f
  spec:
    sourcePod: network-check-source-6f78d59f99-fkqq5
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T00:52:16Z"
      message: 'network-check-target-ip-10-0-140-206: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.679763ms
      message: 'network-check-target-ip-10-0-140-206: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:41:16Z"
    - latency: 2.28516ms
      message: 'network-check-target-ip-10-0-140-206: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:40:16Z"
    - latency: 2.057839ms
      message: 'network-check-target-ip-10-0-140-206: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:39:16Z"
    - latency: 2.482958ms
      message: 'network-check-target-ip-10-0-140-206: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:38:16Z"
    - latency: 2.203211ms
      message: 'network-check-target-ip-10-0-140-206: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:37:16Z"
    - latency: 2.060916ms
      message: 'network-check-target-ip-10-0-140-206: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:36:16Z"
    - latency: 2.60548ms
      message: 'network-check-target-ip-10-0-140-206: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:35:16Z"
    - latency: 3.140218ms
      message: 'network-check-target-ip-10-0-140-206: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:34:16Z"
    - latency: 13.270405ms
      message: 'network-check-target-ip-10-0-140-206: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:33:16Z"
    - latency: 3.523365ms
      message: 'network-check-target-ip-10-0-140-206: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:32:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T00:45:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-169-to-network-check-target-ip-10-0-143-7
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-169.ec2.internal
      uid: 60e518de-6650-44f7-bbaf-916f27806b07
    resourceVersion: "138965"
    uid: 895925a4-34db-4d56-8dbd-c9c5e3e36655
  spec:
    sourcePod: network-check-source-6f78d59f99-fkqq5
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T00:52:16Z"
      message: 'network-check-target-ip-10-0-143-7: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.629677ms
      message: 'network-check-target-ip-10-0-143-7: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:41:16Z"
    - latency: 2.514357ms
      message: 'network-check-target-ip-10-0-143-7: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:40:16Z"
    - latency: 2.377161ms
      message: 'network-check-target-ip-10-0-143-7: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:39:16Z"
    - latency: 2.486805ms
      message: 'network-check-target-ip-10-0-143-7: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:38:16Z"
    - latency: 3.034281ms
      message: 'network-check-target-ip-10-0-143-7: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:37:16Z"
    - latency: 2.240022ms
      message: 'network-check-target-ip-10-0-143-7: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:36:16Z"
    - latency: 2.863933ms
      message: 'network-check-target-ip-10-0-143-7: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:35:16Z"
    - latency: 3.242192ms
      message: 'network-check-target-ip-10-0-143-7: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:34:16Z"
    - latency: 5.26072ms
      message: 'network-check-target-ip-10-0-143-7: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:33:16Z"
    - latency: 2.941982ms
      message: 'network-check-target-ip-10-0-143-7: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:32:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T00:45:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-169-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-169.ec2.internal
      uid: 60e518de-6650-44f7-bbaf-916f27806b07
    resourceVersion: "143347"
    uid: 2f6c3e51-f52e-48df-b5f5-2e68edf7e5fe
  spec:
    sourcePod: network-check-source-6f78d59f99-fkqq5
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T00:51:16Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 943.99µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:45:16Z"
    - latency: 1.954845ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T01:45:16Z"
    - latency: 1.072696ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:44:16Z"
    - latency: 2.38731ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T01:44:16Z"
    - latency: 2.10487ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:43:16Z"
    - latency: 10.016185ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T01:43:16Z"
    - latency: 1.435783ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:42:16Z"
    - latency: 2.783848ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T01:42:16Z"
    - latency: 922.353µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:41:16Z"
    - latency: 2.385569ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T01:41:16Z"
kind: List
metadata:
  resourceVersion: ""