Skip to content
This repository has been archived by the owner on Feb 22, 2022. It is now read-only.
This repository has been archived by the owner on Feb 22, 2022. It is now read-only.

[stable/jenkins] JNLP port should not be exposed via type=LoadBalancer #1341

Closed
@kensimon

Description

Is this a request for help?: No


Is this a BUG REPORT or FEATURE REQUEST? (choose one): Bug Report

Version of Helm and Kubernetes: Makes no difference

Which chart: stable/jenkins

What happened: Port 50000 (the jenkins JNLP master port) is exposed to the open internet via an ELB when the helm chart is installed on a cluster with an AWS cloud provider

What you expected to happen: The jenkins master port should not be exposed the same way the HTTP port is... since it's configured to launch slaves in the same kubernetes cluster, that service can just be ClusterIP. There should be an option to only expose the HTTP port via type=LoadBalancer while keeping the master port private to the cluster.

How to reproduce it (as minimally and precisely as possible): helm install stable/jenkins on an AWS cluster (I'm sure it's the same for any other cloud provider)

Anything else we need to know: There's enough configuration options to tune this behavior, but the defaults should not be this insecure.

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions