Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix console port forward step #30823

Merged
merged 2 commits into from
Dec 16, 2024
Merged

Conversation

SangJunBak
Copy link
Contributor

We extend the existing port forward to retry on failure.

Motivation

Tips for reviewer

Checklist

  • This PR has adequate test coverage / QA involvement has been duly considered. (trigger-ci for additional test/nightly runs)
  • This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
  • If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
  • If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).
  • If this PR includes major user-facing behavior changes, I have pinged the relevant PM to schedule a changelog post.

@SangJunBak SangJunBak requested a review from a team December 13, 2024 22:44
@SangJunBak SangJunBak requested a review from a team as a code owner December 13, 2024 22:44
@SangJunBak
Copy link
Contributor Author

@kay-kim it looks like a lot's duplicated between the mini-kube and kubectl setup. Should we create partials for at least some of the common steps? Or would you prefer the duplication for maximal flexibility?

We extend the existing port forward to retry on failure.
@SangJunBak SangJunBak force-pushed the jun/self-managed-console-kind-fixes branch from 066d2a9 to af3f402 Compare December 14, 2024 01:20
@kay-kim
Copy link
Contributor

kay-kim commented Dec 14, 2024

Oh, will definitely create shortcodes/partials. Heh heh ... I just copied+paste for speed right before going on Thanksgiving break 😄 I'll update those next week. Didn't have time to do the updates this week - but, next week is mostly self-managed docs work (including AWS instructions).

interrupted long-running requests through a standard port-forward cause the port forward to hang. The command above
automatically restarts the port forwarding if an error occurs, ensuring a more stable
connection. It detects failures by monitoring for "portforward.go" error messages.
{{< /note >}}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Heh ... yeah ... our note shortcode needs tweak. I see you did left-aligning below and not here. I'll add a patch to just fix the note, so that people can do the sensible thing like you did here.

@SangJunBak SangJunBak merged commit 0241015 into main Dec 16, 2024
11 checks passed
@SangJunBak SangJunBak deleted the jun/self-managed-console-kind-fixes branch December 16, 2024 15:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants