...
Once the installation is complete, it will display the URL to continue the configuration. Copy that URL and manually enter it in the browser for UI configuration. When the below pop-up prompts, you are ready to go to the UI to configure the system.
...
...
Click “Create New” to create a new cluster.
Fill in all the required fields:
Cluster Name - The name of your new Swarm cluster. This needs to be unique, but will not be seen on the network.
Virtual IP Address - The IP address for the new cluster.
Network Services Addresses - The Cilium IP ranges. It can be an individual IP, IP ranges, or CIDR-formatted IP blocks. These IPs must be unique and must not be assigned to any machine.
License - If you have a license file, you can upload it here. If not, a default 2TB license will automatically be deployed with the cluster.
Click “Advanced” to add a new domain and bucket on the default cluster.
Clicking on Next will start the deployment, which includes:
Installing k3s
Installing flux
Adding base overseer
Adding bucket login details
Using hostype to push the configuration
Helm reconcilliation via flux
The K3s install takes a few seconds to complete, then you should be able to use Kubectl to query the cluster.
When cluster manifests are deployed, the terminal looks like this:
Code Block root@demo00:/var/perifery# kubectl get pods -A --watch NAMESPACE NAME READY STATUS RESTARTS AGE kube-system helm-install-traefik-q6wjs 0/1 Pending 0 0s kube-system helm-install-traefik-crd-28bgc 0/1 Pending 0 0s kube-system helm-install-traefik-q6wjs 0/1 Pending 0 0s kube-system helm-install-traefik-crd-28bgc 0/1 Pending 0 0s kube-system helm-install-traefik-q6wjs 0/1 ContainerCreating 0 0s kube-system helm-install-traefik-crd-28bgc 0/1 ContainerCreating 0 0s kube-system svclb-overseer-lb-265778c4-sq6k8 0/1 Pending 0 0s kube-system svclb-overseer-lb-265778c4-sq6k8 0/1 Pending 0 0s kube-system svclb-overseer-lb-265778c4-sq6k8 0/1 ContainerCreating 0 0s default overseer-77bcc8795c-zhd2k 0/1 Pending 0 0s kube-system metrics-server-5f8b4ffd8-hlg9l 0/1 Pending 0 0s kube-system local-path-provisioner-79ffd768b5-v742d 0/1 Pending 0 0s kube-system coredns-77ccd57875-bsn64 0/1 Pending 0 0s kube-system metrics-server-5f8b4ffd8-hlg9l 0/1 Pending 0 0s kube-system local-path-provisioner-79ffd768b5-v742d 0/1 Pending 0 1s kube-system coredns-77ccd57875-bsn64 0/1 Pending 0 1s kube-system metrics-server-5f8b4ffd8-hlg9l 0/1 ContainerCreating 0 1s kube-system local-path-provisioner-79ffd768b5-v742d 0/1 ContainerCreating 0 1s kube-system coredns-77ccd57875-bsn64 0/1 ContainerCreating 0 1s flux-system helm-controller-74b9b95b88-7r586 0/1 Pending 0 0s flux-system helm-controller-74b9b95b88-7r586 0/1 Pending 0 0s flux-system kustomize-controller-696657b79c-rlb28 0/1 Pending 0 0s flux-system kustomize-controller-696657b79c-rlb28 0/1 Pending 0 0s flux-system helm-controller-74b9b95b88-7r586 0/1 ContainerCreating 0 0s flux-system notification-controller-6cb7b4f4bf-c4tnr 0/1 Pending 0 0s flux-system notification-controller-6cb7b4f4bf-c4tnr 0/1 Pending 0 0s flux-system source-controller-5c69c74b57-tn8vl 0/1 Pending 0 0s flux-system kustomize-controller-696657b79c-rlb28 0/1 ContainerCreating 0 0s flux-system source-controller-5c69c74b57-tn8vl 0/1 Pending 0 0s flux-system notification-controller-6cb7b4f4bf-c4tnr 0/1 ContainerCreating 0 0s flux-system source-controller-5c69c74b57-tn8vl 0/1 ContainerCreating 0 0s kube-system svclb-overseer-lb-265778c4-sq6k8 1/1 Running 0 5s kube-system coredns-77ccd57875-bsn64 0/1 Running 0 6s kube-system coredns-77ccd57875-bsn64 1/1 Running 0 6s kube-system helper-pod-create-pvc-9341ef6d-81aa-4332-9d1b-29cc631e1b1a 0/1 Pending 0 0s kube-system helper-pod-create-pvc-9341ef6d-81aa-4332-9d1b-29cc631e1b1a 0/1 ContainerCreating 0 0s kube-system local-path-provisioner-79ffd768b5-v742d 1/1 Running 0 7s
When K3s is online, the UI looks like:
Click Done to proceed.
It may take a few minutes for the storage nodes to come online.
The gateway gets created when the storage nodes are up. We are about 30 sec away from a running cluster.
Code Block root@demo00:/var/perifery# kubectl get pods -n swarm NAME READY STATUS RESTARTS AGE elastic-operator-0 1/1 Running 0 3m50s swarm-operators-controller-manager-c7cbfb844-nhp6m 1/1 Running 0 2m53s ssa-stack-ldap-deploy-84d58c844d-kt7v6 1/1 Running 0 2m53s ssa-stack-syslog-deploy-796bbb577f-njtgn 1/1 Running 0 2m53s ssa-stack-gatewayoobe-job-r2h4z 1/1 Running 0 2m37s ssa-stack-es-es-microa-1 1/1 Running 0 2m52s ssa-stack-es-es-microa-0 1/1 Running 0 2m52s ssa-stack-es-es-microa-2 1/1 Running 0 2m52s ssa-stack-castor-microa-demo00-0 0/1 Running 0 77s ssa-stack-castor-microa-demo00-2 0/1 Running 0 77s ssa-stack-castor-microa-demo00-1 0/1 Running 0 77s ssa-stack-castor-microa-demo00-3 0/1 Running 0 77s
When the pods are in this state, you are ready to login.
Code Block root@demo00:/var/perifery# kubectl get pods -n swarm NAME READY STATUS RESTARTS AGE elastic-operator-0 1/1 Running 0 6m16s swarm-operators-controller-manager-c7cbfb844-nhp6m 1/1 Running 0 5m19s ssa-stack-ldap-deploy-84d58c844d-kt7v6 1/1 Running 0 5m19s ssa-stack-syslog-deploy-796bbb577f-njtgn 1/1 Running 0 5m19s ssa-stack-gatewayoobe-job-r2h4z 1/1 Running 0 5m3s ssa-stack-es-es-microa-1 1/1 Running 0 5m18s ssa-stack-es-es-microa-0 1/1 Running 0 5m18s ssa-stack-es-es-microa-2 1/1 Running 0 5m18s ssa-stack-castor-microa-demo00-0 1/1 Running 0 3m43s ssa-stack-castor-microa-demo00-2 1/1 Running 0 3m43s ssa-stack-castor-microa-demo00-1 1/1 Running 0 3m43s ssa-stack-castor-microa-demo00-3 1/1 Running 0 3m43s ssa-stack-gateway-hpqbt 1/1 Running 0 73s
Now, the UI will redirect to the login screen as shown below:
Login credentials for the first-time install are:
username – periferyadmin
password – password
The system asks to update the default password on the first login.
Use a unique and strong password, then click Update.
After a successful password update, you can log into the system with the updated password. It displays the below dashboard:
...