Dieser Inhalt ist in der von Ihnen ausgewählten Sprache nicht verfügbar.
Chapter 4. Configuring power monitoring
Power monitoring is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.
For more information about the support scope of Red Hat Technology Preview features, see Technology Preview Features Support Scope.
The
Kepler
4.1. The Kepler configuration Link kopierenLink in die Zwischenablage kopiert!
You can configure Kepler with the
spec
Kepler
Ensure that the name of your Kepler instance is
kepler
The following is the list of configuration options:
| Name | Spec | Description | Default |
|---|---|---|---|
|
|
| The port on the node where the Prometheus metrics are exposed. |
|
|
|
| The nodes on which Kepler exporter pods are scheduled. |
|
|
|
| The tolerations for Kepler exporter that allow the pods to be scheduled on nodes with specific characteristics. |
|
Example Kepler resource with default configuration
apiVersion: kepler.system.sustainable.computing.io/v1alpha1
kind: Kepler
metadata:
name: kepler
spec:
exporter:
deployment:
port: 9103
nodeSelector:
kubernetes.io/os: linux
Tolerations:
- key: ""
operator: "Exists"
value: ""
effect: ""
4.2. Monitoring the Kepler status Link kopierenLink in die Zwischenablage kopiert!
You can monitor the state of the Kepler exporter with the
status
Kepler
The
status.exporter
- The number of nodes currently running the Kepler pods
- The number of nodes that should be running the Kepler pods
- Conditions representing the health of the Kepler resource
This provides you with valuable insights into the changes made through the
spec
Example state of the Kepler resource
apiVersion: kepler.system.sustainable.computing.io/v1alpha1
kind: Kepler
metadata:
name: kepler
status:
exporter:
conditions:
- lastTransitionTime: '2024-01-11T11:07:39Z'
message: Reconcile succeeded
observedGeneration: 1
reason: ReconcileSuccess
status: 'True'
type: Reconciled
- lastTransitionTime: '2024-01-11T11:07:39Z'
message: >-
Kepler daemonset "kepler-operator/kepler" is deployed to all nodes and
available; ready 2/2
observedGeneration: 1
reason: DaemonSetReady
status: 'True'
type: Available
currentNumberScheduled: 2
desiredNumberScheduled: 2
4.3. Configuring Kepler to use Redfish Link kopierenLink in die Zwischenablage kopiert!
You can configure Kepler to use Redfish as the source for running or hosting containers. Kepler can then monitor the power usage of these containers.
Prerequisites
- You have access to the OpenShift Container Platform web console.
-
You are logged in as a user with the role.
cluster-admin - You have installed the Power monitoring Operator.
Procedure
-
In the Administrator perspective of the web console, click Operators
Installed Operators. - Click Power monitoring for Red Hat OpenShift from the Installed Operators list and click the Kepler tab.
- Click Create Kepler. If you already have a Kepler instance created, click Edit Kepler.
Configure
of the Kepler instance by specifying the mandatory.spec.exporter.redfishfield. You can also configure the optionalsecretRefandprobeIntervalfields to meet your needs.skipSSLVerifyExample Kepler instance
apiVersion: kepler.system.sustainable.computing.io/v1alpha1 kind: Kepler metadata: name: kepler spec: exporter: deployment: # ... redfish: secretRef: <secret_name> required1 probeInterval: 60s2 skipSSLVerify: false3 # ...- 1
- Required: Specifies the name of the secret that contains the credentials for accessing the Redfish server.
- 2
- Optional: Controls the frequency at which the power information is queried from Redfish. The default value is
60s. - 3
- Optional: Controls if Kepler skips verifying the Redfish server certificate. The default value is
false.
NoteAfter Kepler is deployed, the
namespace is created.openshift-power-monitoringCreate the
file with the following data format:redfish.csv<your_kubelet_node_name>,<redfish_username>,<redfish_password>,https://<redfish_ip_or_hostname>/Example
redfish.csvfilecontrol-plane,exampleuser,examplepass,https://redfish.nodes.example.com worker-1,exampleuser,examplepass,https://redfish.nodes.example.com worker-2,exampleuser,examplepass,https://another.redfish.nodes.example.comCreate the secret under the
namespace. You must create the secret with the following conditions:openshift-power-monitoring-
The secret type is .
Opaque -
The credentials are stored under the key in the
redfish.csvfield of the secret.data
$ oc -n openshift-power-monitoring \ create secret generic redfish-secret \ --from-file=redfish.csvExample output
apiVersion: v1 kind: Secret metadata: name: redfish-secret data: redfish.csv: YmFyCg== # ...ImportantThe Kepler deployment will not continue until the Redfish secret is created. You can find this information in the
of a Kepler instance.status-
The secret type is