-
Notifications
You must be signed in to change notification settings - Fork 3.5k
Update README.md with kubectl-proxy-command for dashboard #57
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
base: main
Are you sure you want to change the base?
Update README.md with kubectl-proxy-command for dashboard #57
Conversation
WalkthroughThe command for starting the Kubernetes Dashboard proxy in the documentation was updated to include explicit options for port, address, and accepted hosts. Instead of relying on default settings, the proxy is now configured to listen on port 8001, bind to all network interfaces, and accept requests from any host, thereby changing its network accessibility parameters. Changes
Poem
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (1)
kind-cluster/README.md (1)
116-116: Security Consideration: Binding the proxy to all interfaces
By using--address=0.0.0.0with--accept-hosts='.*', the dashboard proxy is exposed on every network interface and will accept requests from any host. This can unintentionally open your cluster dashboard to untrusted networks.
Consider tightening these flags for safer defaults, for example:kubectl proxy \ --port=8001 \ --address=127.0.0.1 \ --accept-hosts='^127\.0\.0\.1$'Or, if remote access is required, document a more restrictive regex to whitelist only your known client IPs.
Start the Dashboard using kubectl proxy:
kubectl proxy --port=8001 --address=0.0.0.0 --accept-hosts='.*'
Summary by CodeRabbit