dashboard icon indicating copy to clipboard operation
dashboard copied to clipboard
verified publisher icon kubernetes

Add custom terminal timeout option

Open Joseph-Goergen opened this issue 3 years ago • 4 comments

What would you like to be added?

Another customizable option for the kubernetes-dashboard-settings configmap called terminalTimeout or something along those lines that gives the user the ability to set the timeout (in seconds) for the terminal.

The variable would be used to replace the value set here (leave the default to 10 seconds when not specified) https://github.com/kubernetes/dashboard/blob/9d720d765fe1747c92aa592ef68abd3e419da3c5/src/app/backend/handler/terminal.go#L311.

Why is this needed?

We've had multiple customers complaining to us that the terminal left them hung when attempting to exec into the pod. We run the kubernetes dashboard through a proxy agent for our customers. The proxy agent is not as quick as the kubectl proxy method and times-out for them. We are requesting to make this configurable for us.

Joseph-Goergen avatar Nov 17 '22 21:11 Joseph-Goergen

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

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

/lifecycle stale

k8s-triage-robot avatar Feb 15 '23 21:02 k8s-triage-robot

/remove-lifecycle stale

rtheis avatar Feb 15 '23 21:02 rtheis

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

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

/lifecycle stale

k8s-triage-robot avatar May 16 '23 22:05 k8s-triage-robot

/remove-lifecycle stale

rtheis avatar May 16 '23 23:05 rtheis