-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
Disable dashboard by default #6804
Conversation
Users should opt in for features and not opt out.
Hi @hafe. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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/test-infra repository. |
I cannot find document which says Kubespray deployment should be minimum as possible in this repository. I could understand disabling the dashboard in the default because I expected most users just use kubectl command and not use the dashboard. However my colleagues want to use the dashboard to understand the situation easily and the dashboard is deployed at the default with Kubespray in our clusters. /cc @oomichi |
Reducing the scope of Kubespray has been discussed in slack and in the 3.0 issue. Disabling the dashboard by default was brought as something wanted. If you want it is still there and you can just flip the value of a variable. Of preferable (as discussed), use the official upstream supported way of deploying |
As long as we put a big (real big) notice in the release note, I think we are safe to go. So I would go with @hafe and roll this PR but as you pointed @oomichi maybe we need to discuss this with @Miouge1 and @EppO (and others if anyone as something to say about that) /ok-to-test |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hafe, woopstar The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Happy to see opinions, thanks. |
/lgtm |
* 'master' of https://github.com/kubernetes-sigs/kubespray: change owner to root for bin_dir directory (kubernetes-sigs#6814) Modify imagepullpolicy (kubernetes-sigs#6816) fix: add tags for set facts nodelocaldns (kubernetes-sigs#6813) Make reset work for crio (kubernetes-sigs#6812) Added option to force apiserver and respective client certificate to … (kubernetes-sigs#6403) cleanup kubelet_deployment_type (kubernetes-sigs#6815) allow pre-existing floating IPs to be specified with k8s_master_fips (kubernetes-sigs#6755) Fix line-spacing in no_proxy.yml (kubernetes-sigs#6810) Fix handler naming issue for Kubeadm | kubelet (kubernetes-sigs#6803) Disable dashboard by default (kubernetes-sigs#6804) Chmod kubeconfig to avoid group-readable (kubernetes-sigs#6800) Update bunch of dependencies (kubernetes-sigs#6801) If no_proxy_exclude_workers is true, workers will be excluded from the no_proxy variable. This prevents docker engine restarting when scaling workers. (kubernetes-sigs#6520)
Users should opt in for features and not opt out.
Since kubernetes-sigs#6804 dashboard_enabled has been false by default. However we forgot to update it on sample inventory and it made confusion. This updates the sample inventory.
Since #6804 dashboard_enabled has been false by default. However we forgot to update it on sample inventory and it made confusion. This updates the sample inventory.
Since kubernetes-sigs#6804 dashboard_enabled has been false by default. However we forgot to update it on sample inventory and it made confusion. This updates the sample inventory.
It was disabled by default in Kubespray recently: kubernetes-sigs/kubespray#6804
Users should opt in for features and not opt out.
What type of PR is this?
/kind api-change
What this PR does / why we need it:
Keep the default deployment as small as possible. Users should opt in for features and not opt out.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: