-
Notifications
You must be signed in to change notification settings - Fork 239
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
Remove cluster node status reporting from agent #1973
Comments
Removes cluster node status reporting from agent and adds a basic unit test for the `clusterstatus Ticker` Refers to: rancher#1973 Signed-off-by: Xavi Garcia <xavi.garcia@suse.com>
Removes cluster node status reporting from agent and adds a basic unit test for the `clusterstatus Ticker` Refers to: rancher#1973 Signed-off-by: Xavi Garcia <xavi.garcia@suse.com>
Removes cluster node status reporting from agent and adds a basic unit test for the `clusterstatus Ticker` Refers to: rancher#1973 Signed-off-by: Xavi Garcia <xavi.garcia@suse.com>
Removes cluster node status reporting from agent and adds a basic unit test for the `clusterstatus Ticker` Refers to: rancher#1973 Signed-off-by: Xavi Garcia <xavi.garcia@suse.com>
Removes cluster node status reporting from agent and adds a basic unit test for the `clusterstatus Ticker` Refers to: rancher#1973 Signed-off-by: Xavi Garcia <xavi.garcia@suse.com>
Removes cluster node status reporting from agent and adds a basic unit test for the `clusterstatus Ticker` Refers to: rancher#1973 Signed-off-by: Xavi Garcia <xavi.garcia@suse.com>
Removes cluster node status reporting from agent and adds a basic unit test for the `clusterstatus Ticker` Refers to: rancher#1973 Signed-off-by: Xavi Garcia <xavi.garcia@suse.com>
Removes cluster node status reporting from agent and adds a basic unit test for the `clusterstatus Ticker` Refers to: rancher#1973 Signed-off-by: Xavi Garcia <xavi.garcia@suse.com>
Removes cluster node status reporting from agent and adds a basic unit test for the `clusterstatus Ticker` Refers to: rancher#1973 Signed-off-by: Xavi Garcia <xavi.garcia@suse.com>
QA TemplateSolutionDeletes some information provided by $ kubectl get clusters -A
NAMESPACE NAME BUNDLES-READY NODES-READY SAMPLE-NODE LAST-SEEN STATUS
fleet-local local 1/1 3/3 k3d-upstream-server-0 2024-03-13T10:34:07Z The change removes the values reported for "NODES-READY and SAMPLE-NODE". TestingJust run a command to retrieve all clusters and you should not see the NODES-READY nor SAMPLE-NODE columns $ kubectl get clusters -A
NAMESPACE NAME BUNDLES-READY LAST-SEEN STATUS
fleet-local local 1/1 2024-03-13T10:49:27Z Additional info |
Test reportWorks as expected. But currently waiting for rancher/dashboard implementation as Tested on rancher
Also in this diff it is visible that status information are reduced in |
The agent reports the node status of the cluster it's running on.
It lists all nodes every 15min, or by the amount configured as
CheckInterval
in the agents config.Since it also updates a timestamp, the bundledeployment is changed.
The UI only displays the timestamp for the clustergroups
Last seen
column.We could remove the node count and status reporting.
This is a follow-up to #1772
The text was updated successfully, but these errors were encountered: