4 ms·
The first time I used helm was to set up JenkinsCI on a k8s cluster on AWS, and in the default configuration, it setup a public-internet ELB listener (with type
by ninkendo 5y ago
The first time I used helm was to set up JenkinsCI on a k8s cluster on AWS, and in the default configuration, it setup a public-internet ELB listener (with type=LoadBalancer) for Jenkins' internal JNLP port. Which pretty much means the public internet has root access to your jenkins cluster, by default.
I had crypto miners using my k8s cluster within a couple of hours.
That was also the last time I used helm.
- SirMonkey 5y agoYou mean the helm-package you installed without reading the documentation? Hate the player, not the game.
- ninkendo 5y agoNo. 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.
- deleted 5y ago[deleted]