search

crc-org / crc

CRC is a tool to help you run containers. It manages a local OpenShift 4.x cluster, Microshift or a Podman VM optimized for testing and development purposes
https://crc.dev
Apache License 2.0
1.25k stars 240 forks source link

Find a way to disable the 'Monitoring' section on the console/dashboard #36

Open gbraad opened 5 years ago

gbraad commented 5 years ago

Since most of the sections for monitoring and the link to metrics do not work, it is probably best to find a way to remove/disable this section from the dashboard.

monitoring

anjannath commented 5 years ago

This section is disabled for the developer user. only shown in the console if logged in as kubeadmin

cfergeau commented 5 years ago

But if the user reenables monitoring, then these metrics would work? Or even with monitoring enabled, in the single node/libvirt case, they would not be useful? If this section should be hidden/shown depending on the availability of the monitoring pods, then maybe it's something that should be dealt with by the console itself.

cfergeau commented 5 years ago

Something similar happens with "Admin/Cluster Settings" which shows some errors :

Update is failing. Multiple errors are preventing progress:

  • Cluster operator machine-config is reporting a failure: Failed to resync 4.1.11 because: timed out waiting for the condition during sync RequiredMachineConfigPools: pool master has not progressed to latest configuration: configuration status for pool master is empty, retrying
  • Cluster operator marketplace is still updating. View Cluster Operators for more details.
cfergeau commented 5 years ago

Something similar happens with "Admin/Cluster Settings" which shows some errors :

This actually is issue #299

AkihiroSuda commented 5 years ago

Why not install metrics-server by default?

stale[bot] commented 4 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

gbraad commented 4 years ago

Resource usage is too high to justify this being default

stale[bot] commented 4 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

stale[bot] commented 4 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

guillaumerose commented 3 years ago

There is good chance we will be able to turn on monitoring by default at some point. One goal of OpenShift 4.8 is to make monitoring stack fit in a single node cluster.

Monitoring is also what's defined OpenShift (ie. this is checked in e2e tests). I don't think this request will be ever considered in the console side.