Questions
- The dashboard is insecure.
- True
- False
- How can the dashboard identify a user?
- A token injected from a reverse proxy or provided by the login form
- Username and password
- service account
- Multi-factor authentication
- How does the dashboard track the session state?
- Sessions are stored in etcd
- Sessions are stored in custom resource objects called
DashboardSession
- There are no sessions
- If a token is uploaded, it’s encrypted and stored in the browser as a cookie
- When using a token, how often can the dashboard refresh it?
- Once a minute
- Every thirty seconds
- When the token expires
- None of the above
- What’s the best way to deploy the dashboard?
- Using
kubectl
port-forward - Using
kubectl
proxy - With a secret Ingress...
- Using