Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

ICN strives to automate the process of installing the local cluster controller to the greatest degree possiblepossible–"zero touch installation". Most of the work is done simply by booting up the jump host (Local Controller) from the ISO image. Once booted, (edit config file ??) .., the controller is fully provisioned and begins to inspect and provision  baremetal servers, until the cluster is entirely configured.

License


Deployment Architecture

...

Install software for Local Controller, by booting fterom from ICN ISO device.

Edit Baremetal Host CRD by adding unique names for the Secret and BareMetalHost, IPMI address, and bootMACaddress.

Create the CR for each BareMetalHost. This can be done by connecting to the Kubernetes Dashboard and adding the CR, or by using the kubectl command to create a resource.

On creating the CR, the Baremetal Operator will start provisioning the baremetal hosts. (section on adding images?)(add KuD)

Virtual Deployment


Kubernetes Dashboard

Kubernetes Dashboard runs on the Local Controller. (add to Baremetal Hosts as well?) It  It is accessed via a web browser. kubectl proxy should be running.

(assume dashboard is pre-built and installed via Kubernetes deployment. The dashboard container must be in the docker registry. The dashboard is deployed by dashboard-deploy.yaml)

(user should be provided the dashboard token in the installation, but to re-create, do the following:)The Dashboard is brought up by with the dashboard-deployment yaml file. This file must refer to the images in the local Docker repository (see "spec: container: image:"). There should also be a K8S service account created for an admin-user. The token for Dashboard login is created from the admin-user secrets.

To re-create a token for Dashboard authentication:

...

If accessing the Dashboard from a location other than the Local Controller, the pkcs12 certificate must be imported into the browser. The Dashboard is accessed via the following URL (note–if the namespace or name of the dashboard is changed, the URL must match):

https://<controller IP>:6443/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/

...