Deploy and Access the Kubernetes Dashboard

[manishpanjwani21]

While deploying the dashboard on 1.22.2 I am getting a warning
Warning: spec.template.metadata.annotations[seccomp.security.alpha.kubernetes.io/pod]: deprecated since v1.19; use the "seccompProfile" field instead.
Please if you can fix it.

annotations:
seccomp.security.alpha.kubernetes.io/pod: 'runtime/default'

[sftim]

/retitile Warning whilst following task “Deploy and Access the Kubernetes Dashboard”

[sftim]

I think this report is about https://kubernetes.io/docs/tasks/access-application-cluster/web-ui-dashboard/
/language en

[sftim]

That page links to https://raw.githubusercontent.com/kubernetes/dashboard/v2.3.1/aio/deploy/recommended.yaml

I suspect the fix will be to update that to a more recent all-in-one manifest, and test that the updated manifest works.
/kind bug

[Garima-Negi]

Seeing an error (not warning) : error: error validating "https://raw.githubusercontent.com/kubernetes/dashboard/v2.4.0/aio/deploy/recommended.yaml": error validating data: ValidationError(Deployment.spec.template.spec.securityContext): unknown field "seccompProfile" in io.k8s.api.core.v1.PodSecurityContext; if you choose to ignore these errors, turn validation off with --validate=false

seems to be related to most recent merge kubernetes/dashboard@f97fb55 on aio/deploy/recommended/06_dashboard_deployment.yaml

which is where securityContext: seccompProfile: type: RuntimeDefault was added

[Garima-Negi]

Hi, can this be assigned to me?

kubernetes/dashboard#6615

[dims]

/assign @Garima-Negi

[mehabhalodiya]

/triage accepted

[k8s-triage-robot]

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

This bot triages issues and 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 issue is closed

You can:

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

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

/lifecycle stale

[Garima-Negi]

@dims @mehabhalodiya The corresponding PR for this issue is now closed.
How do I go about closing this issue?

[mehabhalodiya]

/close

[k8s-ci-robot]

@mehabhalodiya: Closing this issue.

In response to this:

/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.