Write the settings¶
Choose the settings of your first installation and keep them in a file, before any cluster exists.
Run¶
See what nereus init would use, and where each value comes from; --dry-run creates nothing:
nereus init --dry-run --create-cluster
output
SETTING VALUE SOURCE
target k3d default
create_cluster true flag
name nereus default
ingress_port 8080 default
installation_name nereus cluster name
profile core default
The table comes first; the two helm upgrade --install lines after it make the same install by hand.
Write the same settings to a file with nereus init --generate-file; it prints the table again and the path it wrote:
nereus init --generate-file --create-cluster
Read the file:
cat ~/.config/nereus/init.yaml
output
apiVersion: core.getnereus.dev/v1alpha1
kind: InitConfig
spec:
profile: core
ingressPort: 8080
undercloud:
create: true
name: nereus
---
apiVersion: core.getnereus.dev/v1alpha1
kind: Installation
metadata:
name: nereus
spec:
alias: nereus
What you get¶
- Two documents: the
InitConfig, how this machine builds the platform, and theInstallation, whose name never changes (spec 0006). - The profile
core: core and the tenancy reef, nothing more until you add it (Runtime and profiles). - A plain
nereus initreads this file; a flag wins over it, and an unknown key is an error. - Nothing created yet: no cluster, no registry.
Next¶
Prepare the cluster from these settings.