Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hide namespace for prometheus clusterRole and clusterRolebinding #1566

Conversation

primeroz
Copy link
Contributor

@primeroz primeroz commented Dec 23, 2021

Description

in release-0.10 the Prometheus clusterRole and clusteRoleBinding have a namespace due to the use of a common set of metadata.

this change will hide the namespace for those resources

Type of change

What type of changes does your code introduce to the kube-prometheus? Put an x in the box that apply.

  • CHANGE (fix or feature that would cause existing functionality to not work as expected)
  • FEATURE (non-breaking change which adds functionality)
  • BUGFIX (non-breaking change which fixes an issue)
  • ENHANCEMENT (non-breaking change which improves existing functionality)
  • NONE (if none of the other choices apply. Example, tooling, build system, CI, docs, etc.)

Changelog entry

Hide namespace for prometheus clusterRole and clusterRolebinding

Hide namespace for prometheus clusterRole and clusterRolebinding

Copy link
Member

@paulfantom paulfantom left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm on green

@primeroz
Copy link
Contributor Author

primeroz commented Jan 4, 2022

I did rebase on top of main and run make all to update the generated manifests ... but i am getting now some spurious changes. i will look into why

@primeroz primeroz force-pushed the fix/do-not-add-namespace-to-clusterwide-resources branch from 561915a to f7738d7 Compare January 4, 2022 09:03
@primeroz
Copy link
Contributor Author

primeroz commented Jan 4, 2022

Spurious changes fixed , now only jsonnet and generate manifests are in the diff

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants