oob

README

oob

Overview

The operator is doing a "light" lights out management of the hardware deployed in an Ironcore installation. It is handling the user management, power states, identification and service data collection via/of the baseboard management controllers by leveraging different industry standards and protocols (e.g. Redfish/IPMI).

It is scanning the known IP Addresses/MAC Addresses from the out-of-band network and handling only specific endpoints that are determined by a filtering mechanism that is preconfigured. The filtering mechanism is used to assign/find the preferred protocol and the proper manufacturer default credentials.

After proper credentials have been found, a new set of credentials is created, existing state for the device will be enforced and all service information is read. A new OOB object is created or updated if already existing.

Installation, using and developing

To find out more, please refer to documentation folder docs

Contributing

We'd love to get feedback from you. Please report bugs, suggestions or post questions by opening a GitHub issue.

How it works

This project aims to follow the Kubernetes Operator pattern

It uses Controllers which provides a reconcile function responsible for synchronizing resources untile the desired state is reached on the cluster

License

Copyright 2023.

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.