|
|
|
|
|
|
by ninkendo
1704 days ago
|
|
|
No. No, no no. This was legitimate a bug that they immediately fixed when I reported it... There is no legitimate reason to expose the master JNLP port to the internet, ever. The chart did not have a configuration option for this, it just exposed the JNLP port as part of the same k8s Service that exposed the web port. (The JNLP port is for jenkins workers to phone back home to the main instance, it's not for external use.) "Just read the docs" is not an answer to a chart setup which is just plain broken. |
|
|