Skip to content

MON-2207: Expose Authorization settings for remote write in the CMO configuration #1598

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

Merged
merged 7 commits into from
Apr 12, 2022

Conversation

JoaoBraveCoding
Copy link
Contributor

@JoaoBraveCoding JoaoBraveCoding commented Mar 18, 2022

Problem: Although the prometheus-operator already supports RemoteWriteSpec.Authorization, the CMO did not support this configuration.

Solution: Allow CMO to pass the RemoteWriteSpec.Authorization from the ConfigMap to the Prometheus CRD

Issues: https://issues.redhat.com/browse/MON-2207

  • I added CHANGELOG entry for this change.
  • No user facing changes, so no entry in CHANGELOG was needed.

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 18, 2022
@JoaoBraveCoding
Copy link
Contributor Author

/test e2e-agnostic-upgrade

2 similar comments
@JoaoBraveCoding
Copy link
Contributor Author

/test e2e-agnostic-upgrade

@JoaoBraveCoding
Copy link
Contributor Author

/test e2e-agnostic-upgrade

@JoaoBraveCoding
Copy link
Contributor Author

/retest

@JoaoBraveCoding
Copy link
Contributor Author

/retest

@JoaoBraveCoding
Copy link
Contributor Author

/retest

@JoaoBraveCoding
Copy link
Contributor Author

/retest-required

@simonpasquier
Copy link
Contributor

/skip
/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 24, 2022
@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

1 similar comment
@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@JoaoBraveCoding
Copy link
Contributor Author

Ping @sferich888 for px approval.
Ping @juzhao for qe approval.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

3 similar comments
@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@juzhao
Copy link
Contributor

juzhao commented Mar 25, 2022

@lihongyan1 please help to review

@JoaoBraveCoding
Copy link
Contributor Author

/retest-required

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

1 similar comment
@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@JoaoBraveCoding
Copy link
Contributor Author

Ping @Senthamilarasu-STA for px approval.

@JoaoBraveCoding
Copy link
Contributor Author

/skip

@lihongyan1
Copy link

/label qe-approved

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Apr 6, 2022
@Senthamilarasu-STA
Copy link

/label px-approved

@openshift-ci openshift-ci bot added the px-approved Signifies that Product Support has signed off on this PR label Apr 8, 2022
@openshift-ci openshift-ci bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Apr 8, 2022
@openshift-ci openshift-ci bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Apr 8, 2022
@@ -228,7 +228,7 @@ func TestPrometheusRemoteWrite(t *testing.T) {
tlsConfig:
ca:
secret:
name: %[2]s
name:%[2]s
Copy link
Contributor

Choose a reason for hiding this comment

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

One last nit :) This change seems unintended and unrelated?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

No, that one actually is an improvement. When I was playing around with the tests I noticed that the ConfigMap was not properly formatted when I printed it with -o yaml with "\t" and "\n" showing and it was because of this space.

@JoaoBraveCoding
Copy link
Contributor Author

/retest

@JoaoBraveCoding
Copy link
Contributor Author

/retest-required

1 similar comment
@JoaoBraveCoding
Copy link
Contributor Author

/retest-required

@jan--f
Copy link
Contributor

jan--f commented Apr 12, 2022

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 12, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 12, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jan--f, JoaoBraveCoding, simonpasquier

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:
  • OWNERS [JoaoBraveCoding,jan--f,simonpasquier]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-robot openshift-merge-robot merged commit 2c494f4 into openshift:master Apr 12, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 12, 2022

@JoaoBraveCoding: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. docs-approved Signifies that Docs has signed off on this PR lgtm Indicates that a PR is ready to be merged. px-approved Signifies that Product Support has signed off on this PR qe-approved Signifies that QE has signed off on this PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants