-
Notifications
You must be signed in to change notification settings - Fork 132
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
OCPBUGS-8044: Garbage collect grafana-dashboard-etcd #1016
OCPBUGS-8044: Garbage collect grafana-dashboard-etcd #1016
Conversation
@Elbehery: This pull request references Jira Issue OCPBUGS-8044, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
Requesting review from QA contact: The bug has been updated to refer to the pull request using the external bug tracker. 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. |
release.openshift.io/delete: "true" | ||
labels: | ||
console.openshift.io/dashboard: "true" | ||
name: remove-etcd-dashboard |
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.
I'm not entirely sure what that does, @Elbehery. This will create a new configmap with the name "remove-etcd-dashboard" that will then be removed by the CVO.
I think we need to patch the existing configmap grafana-dashboard-etcd
with the annotation release.openshift.io/delete: "true"
.
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.
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.
if we add the annotation to the existing CM, all etcd-dashboards will be removed
yes, that's my point. You need to add the annotation on the existing CM that you want to remove. What you committed here creates an entirely new configmap that will be deleted and recreated again - all the time.
@@ -0,0 +1,11 @@ | |||
apiVersion: v1 |
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.
also another nitpick, why not put it next to the existing dashboard in jsonnet?
https://github.com/openshift/cluster-etcd-operator/blob/master/jsonnet/dashboard.jsonnet
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.
+1, this is the best option .. i will change it now 👍🏽
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.
Done 👍🏽
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.
Thanks. Strange that the verify job doesn't complain, doesn't this need to go into the binary with make update
?
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.
i ran make update
, make verify
!!
let me reassure 👍🏽
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.
ran them again, nothing changed :/
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.
ah it was hack/generate.sh
. Can you try that?
Also while reading the docs https://github.com/openshift/cluster-etcd-operator/blob/master/docs/HACKING.md#cvo-resource-removal ...
could you kindly document this annotation approach in the cvo-resource-removal
section?
0eb536f
to
f1cede6
Compare
jsonnet/dashboard.jsonnet
Outdated
'release.openshift.io/delete': "true", | ||
}, | ||
labels: { | ||
'console.openshift.io/dashboard': 'true', |
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.
There's no need to set labels
on a deletion manifest, because the CVO will delete the resource if it exists, labels
isn't part of matching a manifest to a resource (just the group, kind, namespace, and name), and deleted resources don't retain any labels.
jsonnet/dashboard.jsonnet
Outdated
labels: { | ||
'console.openshift.io/dashboard': 'true', | ||
}, | ||
name: 'remove-etcd-dashboard', |
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.
This should be grafana-dashboard-etcd
(the name of the resource you want to delete)
b2e02d7
to
8c257b1
Compare
/label tide/merge-method-squash |
@simonpasquier Hello ✋🏽 Would you mind having a look here plz ? .. I used a list to have two CM in the dashboard manifest, i validated it on https://jsonnet.org/learning/tools.html yet it fails the CI 🤔 |
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
/hold cancel |
@wking one final review please? |
/cherry-pick release-4.12 |
@Elbehery: once the present PR merges, I will cherry-pick it on top of release-4.12 in a new PR and assign it to you. 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. |
/cherry-pick release-4.11 |
@Elbehery: once the present PR merges, I will cherry-pick it on top of release-4.11 in a new PR and assign it to you. 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-required |
1 similar comment
/retest-required |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Elbehery, simonpasquier, tjungblu, wking 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 |
/retest-required |
@Elbehery: 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. |
@Elbehery: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-8044 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. |
@Elbehery: new pull request created: #1019 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. |
@Elbehery: #1016 failed to apply on top of branch "release-4.11":
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. |
/cherry-pick release-4.13 |
@Elbehery: new pull request created: #1023 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. |
resolves https://issues.redhat.com/browse/OCPBUGS-8044