You can monitor the state of the Kepler exporter with the status
field of the Kepler
resource.
The status.exporter
field includes information, such as the following:
-
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
field.
Example state of the Kepler
resource
apiVersion: kepler.system.sustainable.computing.io/v1alpha1
kind: Kepler
metadata:
name: kepler
status:
exporter:
conditions: (1)
- 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 (2)
desiredNumberScheduled: 2 (3)
1 |
The health of the Kepler resource. In this example, Kepler is successfully reconciled and ready. |
2 |
The number of nodes currently running the Kepler pods is 2. |
3 |
The wanted number of nodes to run the Kepler pods is 2. |