detect kcp connection failures via typed errors

[nuromirg]

Summary

kubectl kcp quickstart now prints a "cannot reach kcp" setup hint only when a step fails due to a genuine connection error. The command docs also point users at the kcp release download and manual start, since embedding kcp in the CLI will bloat the binary.

What Type of PR Is This?

/kind cleanup
/kind feature

Related Issue(s)

Fixes #3942

Release Notes

NONE

[kcp-ci-bot]

Hi @nuromirg. Thanks for your PR.

I'm waiting for a kcp-dev member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[mjudeikis]

/ok-to-test

[mjudeikis]

/lgtm
/approve

thanks for this!

[kcp-ci-bot]

LGTM label has been added.

Details

Git tree hash: 12b82ba58f1199927872c0696d003c2d7d98feca

[kcp-ci-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mjudeikis

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• staging/src/github.com/kcp-dev/cli/OWNERS [mjudeikis]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment