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
OCPNODE-1655: Apply node-cluster dashboard as a config map #3708
Conversation
Skipping CI for Draft Pull Request. |
2e4ea09
to
c09c5a4
Compare
8f1bad3
to
cbdc07d
Compare
/cc @harche |
/retest |
1 similar comment
/retest |
/hold till we finalize the node dashboard yaml |
Node dashboard contains useful information and metrics related to the node components. This Config map can be updated with the new metrics as and when required Signed-off-by: Sai Ramesh Vanka <svanka@redhat.com>
@sairameshv: This pull request references OCPNODE-1655 which is a valid jira issue. 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. |
@sairameshv: 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. |
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 |
lgtm |
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.
One question: since this cm gets installed in openshift-config-managed namespace. Shouldn't this be part of that repo? Although I am not sure which repo this namespace belongs to.
@sinnykumari node monitoring dashboard (part of this PR) will be owned and maintained by the node team. Historically, we have used MCO to deliver node specific configurations, e.g. kubelet config. This is the reason we have decided to install this dashboard using MCO. Etcd team uses their own operator to install their dashboard and that one gets installed in same openshift-config-managed namespace. The monitoring dashboard has to be installed by applying a config map in openshift-config-managed namespace with payload containing the jsonnet for the dashboard. The operator that actually installs this config map could be any operator, in node team's case MCO would be the preferred choice. |
makes sense, thanks for the explanation. Wanted to just make sure that we are consistent. /approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: harche, sairameshv, sinnykumari 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 |
- What I did
Added a configmap that creates a node related dashboard
- How to verify it
Install the cluster and observe a
node-cluster
configmap in theopenshift-config-managed
namespace.Also find the
node-cluster
dashboard in theObserve/Dashboards
section in the OCP UI- Description for the changelog
Added a configmap that installs a node-cluster dashboard that contains some useful information about the node related components.