### Problem to solve Currently there is no way to override Prometheus chart default settings when installing through GitLab's Kubernetes integration. ### Intended users <!-- Who will use this feature? If known, include any of the following: types of users (e.g. Developer), personas, or specific company roles (e.g. Release Manager). It's okay to write "Unknown" and fill this field in later. Personas can be found at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/ --> ### Further details 1. The default chart scrapes 1 our of 33 possible kubernetes endpoints, as a user I'd like to specify which additional endpoints to scrape 1. As I user I'd like to specify which certificate/endpoint to use for SSL 1. As I user I'd like to specify which host name to use for this prometheus instance 1. As I user I'd like to remove persistent storage for applications that don't need it ### Proposal Allow user to specify an `overide.yml` file when installing prometheus Example ``` alertmanager: persistentVolume: enabled: false server: persistentVolume: enabled: false ingress: enabled: true tls: - secretName: example-tls hosts: - prometheus.example.com hosts: - prometheus.example.com ``` ### Permissions and Security <!-- What permissions are required to perform the described actions? Are they consistent with the existing permissions as documented for users, groups, and projects as appropriate? Is the proposed behavior consistent between the UI, API, and other access methods (e.g. email replies)? --> ### Documentation <!-- See the Feature Change Documentation Workflow https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html Add all known Documentation Requirements here, per https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html#documentation-requirements --> ### What does success look like, and how can we measure that? <!-- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this. --> ### Links / references