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
Bug 1971589: Change default telemeter server of installed clusters to prod. (#1988) #2003
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ronniel1, ybettan 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:
Approvers can indicate their approval by writing |
… prod. (openshift#1988) Until now, in the service, we changed the default behavior of openshift, which is to always send cluster metrics to prod-telemeter-server unless changed by the user, and we: * left untouched clusters created by cloud prod env * redirected to telemeter-stage stage clusters * redirected to dummy-url all other clusters The issue with this approach is that all prod clusters that aren't created in the cloud, operator clusters for example, will fail to deliver telemetry. Instead, we will now default to prod-telemeter instead of dummy-url unless we know better: * left untouched clusters created by ALL prod envs (not just cloud) * redirect to telemeter-stage stage clusters * redirect to dummy-url integration clusters Signed-off-by: Yoni Bettan <ybettan@redhat.com>
@ybettan: This pull request references Bugzilla bug 1971589, which is invalid:
Comment In response to this:
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. |
/bugzilla refresh |
@ybettan: This pull request references Bugzilla bug 1971589, which is invalid:
Comment In response to this:
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. |
/bugzilla refresh |
@ybettan: This pull request references Bugzilla bug 1971589, which is invalid:
Comment In response to this:
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. |
@ybettan could you please fix the PR description? The title is broken, the description is out of the section, no flags are selected. I saw the master PR is linked but it would be better to have a small heading for it. Holding for now while this is fixed. Thank you, 🙏 /hold |
@ybettan: This pull request references Bugzilla bug 1971589, which is invalid:
Comment In response to this:
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. |
5 similar comments
@ybettan: This pull request references Bugzilla bug 1971589, which is invalid:
Comment In response to this:
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. |
@ybettan: This pull request references Bugzilla bug 1971589, which is invalid:
Comment In response to this:
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. |
@ybettan: This pull request references Bugzilla bug 1971589, which is invalid:
Comment In response to this:
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. |
@ybettan: This pull request references Bugzilla bug 1971589, which is invalid:
Comment In response to this:
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. |
@ybettan: This pull request references Bugzilla bug 1971589, which is invalid:
Comment In response to this:
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. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest |
/retest Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest |
/test subsystem-kubeapi-aws |
@ybettan: The specified target(s) for
Use In response to this:
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. |
/test subsystem-aws |
/test subsystem-kubeapi-aws |
/retest Please review the full test history for this PR and help us cut down flakes. |
12 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/test e2e-metal-assisted-operator-ztp |
/test subsystem-kubeapi-aws |
/retest Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
/retest Please review the full test history for this PR and help us cut down flakes. |
/test subsystem-kubeapi-aws |
@ybettan: All pull requests linked via external trackers have merged: Bugzilla bug 1971589 has been moved to the MODIFIED state. In response to this:
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. |
Description
Until now, in the service, we changed the default behavior of openshift,
which is to always send cluster metrics to prod-telemeter-server unless
changed by the user, and we:
* left untouched clusters created by cloud prod env
* redirected to telemeter-stage stage clusters
* redirected to dummy-url all other clusters
The issue with this approach is that all prod clusters that aren't
created in the cloud, operator clusters for example, will fail to
deliver telemetry.
Instead, we will now default to prod-telemeter instead of dummy-url
unless we know better:
* left untouched clusters created by ALL prod envs (not just cloud)
* redirect to telemeter-stage stage clusters
* redirect to dummy-url integration clusters
Signed-off-by: Yoni Bettan ybettan@redhat.com
This PR clones #1988 and was cherry-picked from it to this specific branch.
What environments does this code impact?
How was this code tested?
Please, select one or more if needed:
It's recommended to take a few extra minutes to provide more information about
how this code was tested. Here are some questions that may be worth answering:
Manual system tests:
I have run test-infra locally and we can see that no manifest was created to redirect the metrics (we defaulted to prod):
Also, in the created cluster, we can see that the ConfigMap for redirection wasn't created:
Assignees
Please, add one or two reviewers that could help review this PR.
/assign @
/assign @
Checklist
docs
, README, etc)Reviewers Checklist