Administrative tasks
Starting monitoring
CRC disables cluster monitoring by default to ensure that CRC can run on a typical notebook. Monitoring is responsible for listing your cluster in the Red Hat Hybrid Cloud Console. Follow this procedure to enable monitoring for your cluster.
-
You must assign additional memory to the CRC instance. At least 14 GiB of memory, a value of
14336
, is recommended for core functionality. Increased workloads will require more memory. For more information, see Configuring the instance.
-
Set the
enable-cluster-monitoring
configurable property totrue
:$ crc config set enable-cluster-monitoring true
-
Start the instance:
$ crc start
Cluster monitoring cannot be disabled. To remove monitoring, set the
enable-cluster-monitoring
configurable property tofalse
and delete the existing CRC instance.
Enabling override Operators
To verify CRC can run on a typical notebook, some resource-heavy services get disabled by default. These services can be enabled by manually removing the desired Operator from the Operator override list.
-
A running CRC virtual machine and a working
oc
command. For more information, see Accessing the OpenShift cluster withoc
. -
You must log in through
oc
as thekubeadmin
user.
-
List unmanaged Operators and note the numeric index for the desired Operator:
-
On Linux or macOS:
$ oc get clusterversion version -ojsonpath='{range .spec.overrides[*]}{.name}{"\n"}{end}' | nl -v -2
-
On Microsoft Windows using PowerShell:
PS> oc get clusterversion version -ojsonpath='{range .spec.overrides[*]}{.name}{"\n"}{end}' | % {$nl++;"`t$($nl-3) `t $_"};$nl=0
-
-
Start the desired Operator using the identified numeric index:
$ oc patch clusterversion/version --type='json' -p '[{"op":"remove", "path":"/spec/overrides/<unmanaged-operator-index>"}]' clusterversion.config.openshift.io/version patched