Upgrade the centraldashboard for supporting the BoundServiceAccountTokenVolume

[carloscao0928]

/kind feature

Why you need this feature:
Recently I had encounted a issue on our product that after loging to the Kubeflow, I got a 500 error, the menu can't show normally, looks like this:

And then I checked the centraldashboard pod log and got this,

After investigated I found it's due to the service account token life over 90 days, so the API had been rejected by AWS, refer here: https://docs.aws.amazon.com/eks/latest/userguide/service-accounts.html#identify-pods-using-stale-tokens

Describe the solution you'd like:
Restart the centraldashboard to refresh the sa token life.

Anything else you would like to add:
So I want know if any plan for upgrading this components or a better solution.

[thesuperzapper]

@kimwnasptd we probably need to address this in a patch release (no specific need to cut a new overall Kubeflow version, however).

/priority 2

[google-oss-prow]

@thesuperzapper: The label(s) priority/2 cannot be applied, because the repository doesn't have them.

In response to this:

@kimwnasptd we probably need to address this in a patch release (no specific need to cut a new overall Kubeflow version, however).

/priority 2

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.

[thesuperzapper]

/priority p2

[andreyvelich]

/transfer dashboard

[google-oss-prow]

@carloscao0928: The label(s) kind/feature cannot be applied, because the repository doesn't have them.

In response to this:

/kind feature

Why you need this feature:
Recently I had encounted a issue on our product that after loging to the Kubeflow, I got a 500 error, the menu can't show normally, looks like this:

And then I checked the centraldashboard pod log and got this,

After investigated I found it's due to the service account token life over 90 days, so the API had been rejected by AWS, refer here: https://docs.aws.amazon.com/eks/latest/userguide/service-accounts.html#identify-pods-using-stale-tokens

Describe the solution you'd like:
Restart the centraldashboard to refresh the sa token life.

Anything else you would like to add:
So I want know if any plan for upgrading this components or a better solution.

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.