In this exercise you manage the existing cluster on the Red Hat Advanced Cluster Management stack - local-cluster
. You will attach labels to the cluster, visualize its resources and perform updates to the OpenShift Platform.
- Modify the attributes of the managed cluster in Red Hat Advanced Cluster Management -
- Name: local-cluster
- labels:
- environment=dev
- owner=<your-name>
In order to associate the labels with local-cluster, follow the next steps -
- Navigate to Cluster Lifecycle -> local-cluster -> Actions -> Edit labels.
- Add the labels.
- Log into the cluster using the oc cli tool.
<managed cluster> $ oc login -u <admin-user> -p <password> https://api.cluster.2222.sandbox.opentlc.com:6443
- Make sure that all of the agent pods are up and running on the cluster.
<managed cluster> $ oc get pods -n open-cluster-management-agent
NAME READY STATUS RESTARTS AGE
klusterlet-645d98d7d5-hnn2z 1/1 Running 0 46m
klusterlet-registration-agent-66fdc479cf-ltlx6 1/1 Running 0 46m
klusterlet-registration-agent-66fdc479cf-qnhzj 1/1 Running 0 46m
klusterlet-registration-agent-66fdc479cf-t8x5n 1/1 Running 0 46m
klusterlet-work-agent-6b8b99b899-27ht9 1/1 Running 0 46m
klusterlet-work-agent-6b8b99b899-95dkr 1/1 Running 1 46m
klusterlet-work-agent-6b8b99b899-vdp9r 1/1 Running 0 46m
<managed cluster> $ oc get pods -n open-cluster-management-agent-addon
NAME READY STATUS RESTARTS AGE
klusterlet-addon-appmgr-64695b8d7b-q7jdg 2/2 Running 0 44m
klusterlet-addon-certpolicyctrl-75df48646-j5zpc 2/2 Running 0 44m
klusterlet-addon-iampolicyctrl-6867d45954-xv9c2 2/2 Running 0 44m
klusterlet-addon-operator-f85df9c7f-lb2cq 1/1 Running 0 45m
klusterlet-addon-policyctrl-config-policy-6fd8d88f5-chjls 1/1 Running 0 44m
klusterlet-addon-policyctrl-framework-7544f4678-kwbz9 4/4 Running 0 44m
klusterlet-addon-search-7b697f899f-5vqwl 2/2 Running 0 44m
klusterlet-addon-workmgr-7f48869cd6-mqq8g 2/2 Running 0 44m
In this exercise you will be using the Red Hat Advanced Cluster Management portal to analyze the managed cluster’s resources.
- Using Red Hat Advanced Cluster Management, find out what is the cloud provider of the managed cluster.
- Using Red Hat Advanced Cluster Management, find out the number of nodes that make up the managed cluster. How many CPUs does each node have?
- Using Red Hat Advanced Cluster Management, check out whether all users can provision new projects on local-cluster (check if the self-provisioners ClusterRoleBinding has the system:authenticated:oauth group associated with it).
- Using Red Hat Advanced Cluster Management, check what channel version is associated with local-cluster (stable / candidate / fast) - (Search for kind:ClusterVersion CR).
- Using Red Hat Advanced Cluster Management -
- Check the port number that the alertmanager-main-0 pod listens on local-cluster (can be found using the pod logs and pod resource definition).
- Check the full path of the alertmanager-main-0 pod configuration file (can be found using the pod logs and pod resource definition).
NOTE: Do this exercise towards the end of the day. The upgrading process may take up to an hour to complete.
- Change the channel version on the local-cluster from stable-4.x to stable-4.x+1.
- Upgrade the cluster using Red Hat Advanced Cluster Management.