K8s cluster blocks project manual Prometheus configuration
Summary
(Summarize the bug encountered concisely)
When there is an project/group/instance cluster with Prometheus installed, the project's "Prometheus manual configuration" cannot be configured. However, the manual configuration can be enabled via the Rails console, so I think this is only a UI limitation.
Steps to reproduce
(How one can reproduce the issue - this is very important)
This issue can be reproduced with a regular project.
- Add an instance cluster.
- Install Helm and Prometheus managed apps in the instance cluster.
- Create a project.
- Go to the Prometheus integration settings page of the project: Project settings > Integrations > Prometheus.
- If the Prometheus manual configuration for the project was already enabled, it will remain enabled. However, if you disable it now, there is no way to enable it again.
- Also, if the Prometheus manual configuration was not enabled before you installed the managed Prometheus app, there is no way to enable it now.
This behavior can be a problem if there is an instance cluster with managed Prometheus installed. This would prevent all projects in the instance from using the Prometheus manual configuration without first uninstalling the managed Prometheus app.
Example Project
(If possible, please create an example project here on GitLab.com that exhibits the problematic behavior, and link to it here in the bug report)
(If you are using an older version of GitLab, this will also determine whether the bug is fixed in a more recent version)
What is the current bug behavior?
(What actually happens)
There is no way to enable Prometheus manual configuration for a project that has a managed Prometheus app installed on a linked k8s cluster.
What is the expected correct behavior?
(What you should see instead)
TBD
Relevant logs and/or screenshots
(Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's tough to read otherwise.)
Output of checks
(If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com)
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:env:info
)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production
)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true
)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true
)(we will only investigate if the tests are passing)
Possible fixes
(If you can, link to the line of code that might be responsible for the problem)