...
The port value here is generated randomly in the range 30000-32767, after saving the modified file with type: NodePort (the default value should be ClusterIP). If you want, you can opt for another value, as long as it belongs to the aforementioned range of values, by relaunching the edit command (here we have chosen the 30000 port, easier to remember). There is no need to open the port on OpenStack, if you access the service through the Worker node FIP, because this range of ports is already open for WorkerNodes (see "Preliminary steps" in cap. 2). If you are using the Control-Plane FIP, you need to open the chosen port. We can check if the changes made have had any effect on the service by running the command
...
By connecting to the browser at https://<master<node_FIP>:<port>, in our case https://131.154.97.163:30000 (note the adoption of the protocol for secure communication with https), we could access the dashboard. There is no need to activate the VPN. The credentials entry screen will appear. As you can see, there are two ways of accessing: via token or via a configuration file. Here we deal with the first mode. However, it is advisable to try the connection to the dashboard, to make sure that the procedure carried out so far is correct.
...