The software described in this documentation is either no longer supported or is in extended support.
Oracle recommends that you upgrade to a current supported release.
To start the Dashboard, you can run a proxy service that allows
traffic on the node where it is running to reach the internal pod
where the Dashboard application is running. This is achieved by
running the kubectl proxy
service:
$ kubectl proxy
Starting to serve on 127.0.0.1:8001
The Dashboard is available on the node where the proxy is running
for as long as the proxy runs. To exit the proxy, use
Ctrl+C
.
You can run this as a systemd
service and
enable it so that it is always available after subsequent reboots:
$ sudo systemctl enable --now kubectl-proxy
This systemd
service requires that the
/etc/kubernetes/admin.conf
is present to run.
If you want to change the port that is used for the proxy service,
or you want to add other proxy configuration parameters, you can
configure this by editing the systemd
drop-in
file at
/etc/systemd/system/kubectl-proxy.service.d/10-kubectl-proxy.conf
.
You can get more information about the configuration options
available for the kubectl proxy
service by
running:
$ kubectl proxy ‐‐help