feat: refresh development container

[shu-mutou]

Support for new Kubernetes Dashboard configuration.
Omitted connecting to an external K8s cluster.
Currently, it only supports kind k8s clusters built by scripts in this repository.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: shu-mutou

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:

• OWNERS [shu-mutou]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 37.20%. Comparing base (a49364c) to head (bbee95e).

❗ Current head bbee95e differs from pull request most recent head b7540d7. Consider uploading reports for the commit b7540d7 to get more accurate results

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #8828   +/-   ##
=======================================
  Coverage   37.19%   37.20%           
=======================================
  Files         255      255           
  Lines       11156    11149    -7     
  Branches      157      158    +1     
=======================================
- Hits         4150     4148    -2     
- Misses       6756     6790   +34     
+ Partials      250      211   -39     

[k8s-triage-robot]

Unknown CLA label state. Rechecking for CLA labels.

Send feedback to sig-contributor-experience at kubernetes/community.

/check-cla
/easycla

[shu-mutou]

@maciaszczykm @floreks PTAL Thanks!

[floreks]

make serve and make run are broken now and do not work.

[shu-mutou]

/checkcla

[shu-mutou]

/easycla

[shu-mutou]

@floreks @maciaszczykm dashboard runs properly with this development container.
Please try hack/develop/run-dev-container.sh. Then try followings.

To add a role with full access for development and get its token
to log into the Dashboard, see followings:

1. Run terminal in development container.
    docker exec -it k8s-dashboard-dev gosu user bash

2. Set env for kubeconfig on development container
    export KUBECONFIG=/go/src/github.com/kubernetes/dashboard/.tmp/kubeconfig

3. Add full access role for development.
    kubectl apply -f hack/develop/developmental-role.yaml

4. Run following to get token for logging into dashboard.
    kubectl -n kubernetes-dashboard create token kubernetes-dashboard

5. Access https://localhost:8443/ with browser on your host,
   then login with token.

[floreks]

What I meant is that running make serve and make run directly in the dashboard root (without using dev container) dir no longer works with these changes applied.

[shu-mutou]

@floreks could you check this again?

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[shu-mutou]

@floreks could you check this again?

[k8s-ci-robot]

PR needs rebase.

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-sigs/prow repository.