rufio
rufio copied to clipboard
tinkerbell
Kubernetes Controller for BMC State Mangement
I noticed that the namespace field on the `authSecretRef` is required, and if not set falls back to the default namespace. With a small amount of guidance I am happy...
## Expected Behaviour Expected that Rufio used the port defined in the Machine manifest. ## Current Behaviour The `port` is ignored, and the default IPMI and Redfish ports are unexpectedly...
The 'powerState' status of kubernetes object 'machine' not being updated, after the machine has been powered on/off via certain job yaml with tasks->powerAction being set to either 'on' or 'off'...
Rufio has a power action called [`PowerStatus`](https://github.com/tinkerbell/rufio/blob/main/api/v1alpha1/action.go#L12). Its unclear why this ever existed as its a read only action that doesn't get used in any capacity. I suggest we remove...
The Task spec currently doesn't allow referencing a machine but requires the full connection details. Tasks should not require the full connection details. It should instead reference a machine like...
The Job Controller and Task Controller have a useful set of unit tests and we confirm our types are registerable with Kubernetes but we have nothing confirming the contractual expectations...
Currently, several of our controllers (originally identified in the Task controller) don't filter status field updates resulting in status patches triggering additional reconciliation requests. This behavior is actually relied upon...
When Rufio times out a task it returns an error from the reconciliation request resulting in an unnecessary requeue. Instead, we expect the controller to patch the status, log the...
Currently, the `TaskReconciler` hard codes task completion timeouts to 3 minutes. While this seems like a sensible default, it also seems sensible to expose it as configuration for the end-user...