Edit service kubernetes-dashboard failed with ClusterIP

[ylacaute]

Environment

Installation method: kubeadm (manual)
Hardware configuration: VPS OVH (dedicated host, 2 CPU, 8Go RAM)
OS: Debian 4.9.30-2+deb9u3 (2017-08-06) x86_64 GNU/Linux
Kubernetes version: v1.14.1
Dashboard version: 1.10.1
Node.js version ('node --version' output): No node installed
Go version ('go version' output): No go installed

Steps to reproduce

With a running cluster with a single node master :
Add the dashboard:

kubectl apply -f https://raw.githubusercontent.com/kubernetes/dashboard/v1.10.1/src/deploy/recommended/kubernetes-dashboard.yaml 

Then edit the config by changing type ClusterIP to NodePort :

kubectl -n kube-system edit service kubernetes-dashboard

Everything ok, then do it again and change type NodePort to ClusterIP :

kubectl -n kube-system edit service kubernetes-dashboard

Observed result

We are unable to save back to ClusterIP type with the following output :

error: services "kubernetes-dashboard" is invalid
A copy of your changes has been stored to "/tmp/kubectl-edit-bhe72.yaml"
error: Edit cancelled, no valid changes were saved.

Expected result

We should be able to update the file exactly as it was after a fresh installation.

Comments

I opened the issue on dashboard repo but we told me the issue should be here.
Related but different issue : #24040

Sorry if this is not bug, I am still discovering K8S.
@kubernetes/sig-contributor-experience-bugs

[neolit123]

/sig ui

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

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.