Update Whisker access for HTTPS on port 8443 - #2909
Merged
Merged
Conversation
Whisker now serves HTTPS on port 8443 instead of HTTP on 8081. Update the port-forward commands and URLs, and note the self-signed certificate warning. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
✅ Deploy Preview for calico-docs-preview-next ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview succeeded!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
There was a problem hiding this comment.
Pull request overview
Updates Calico Open Source vNext documentation to reflect that Whisker now serves HTTPS on port 8443 (instead of HTTP on 8081), aligning the “next” docs with the upstream product change.
Changes:
- Update
kubectl port-forwardexamples from8081:8081to8443:8443. - Update browser URL instructions to
https://localhost:8443. - Add a brief note explaining the expected browser warning due to Whisker’s self-signed certificate.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| calico/observability/view-flow-logs.mdx | Updates Whisker port-forward and access URL instructions to HTTPS on 8443 and documents the self-signed cert warning. |
| calico/getting-started/kubernetes/quickstart.mdx | Updates the Quickstart Whisker access steps to use HTTPS on 8443 with an explanatory certificate-warning note. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Collaborator
|
LGTM, thanks. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Product Version(s):
Calico Open Source vNext (master / next release only — the change ships with projectcalico/calico#13436)
Issue:
projectcalico/calico#13436 and tigera/operator#5140 (both merged): Whisker now serves HTTPS on port 8443 instead of HTTP on 8081.
Link to docs preview:
SME review:
DOCS review:
Additional information:
Updates the two pages in the latest (next) docs tree that carry Whisker port-forward instructions:
calico/observability/view-flow-logs.mdxcalico/getting-started/kubernetes/quickstart.mdxChanges: the port-forward command moves to
8443:8443, the URL becomeshttps://localhost:8443, and a note explains the self-signed certificate warning. Versioned docs are untouched — released versions still serve HTTP on 8081.🤖 Generated with Claude Code