Initial Configuration
After installing Fuzzball, you need to log in to your newly created cluster as an administrator and complete four configuration steps so you (and potentially your users) can begin running workflows.
- Provisioner Configuration: This tells Fuzzball what compute resources it has access to and how it should provision and/or allocate them.
- Storage Configuration: This tells Fuzzball what types of storage it has access to and how to allot storage volumes to users.
- Keycloak Configuration (Keycloak-backed deployments only): You should change the default admin user’s password for security. Additionally, if you are not using an external identity provider (like LDAP) you should configure Keycloak to require new users to change their passwords on initial login. Deployments using the local organization feature introduced in v3.3.0 do not require Keycloak and can skip this step.
- Organization, Group, and User Management (Optional): The cluster administrator can create new users. They can also create new organizations and groups to better manage users, share resources, and enforce permissions.
In this section of the guide, we will describe an initial configuration that will cover all of these steps. More detailed instructions for custom configurations can be found in the dedicated sections that are linked throughout.
These steps must be completed in the order given. For instance, Fuzzball uses compute resources when it configures storage provisioners. Therefore, you must create a provisioner configuration before configuring your storage resources.
Organization owners can also track their organization’s setup from the Fuzzball web UI. When you open the dashboard as an organization owner, a Set up your organization panel shows one step for each resource your organization needs before its users can run workflows:
- Node provisioners: define the compute nodes Fuzzball can provision. See Basic Provisioner Configuration.
- Volume provisioners: define the storage where Fuzzball creates volumes. See Storage Configuration.
- Secrets: store organization-wide credentials that workflows use, such as registry credentials or API keys. See Adding Secrets.
Each step shows whether its resource already exists. A step with nothing configured usually links to the page where you can set it up. A step that is already configured links to the existing resources so you can review them instead. For example, the volume provisioner step shows as configured if Fuzzball created a volume provisioner for your organization automatically. When every step is configured, the panel’s heading changes to Review your organization’s defaults.
Only a cluster admin can define node provisioners. If you are an organization owner but not a cluster admin, the node provisioner step links to the cluster’s existing node provisioners or, if none exist, asks you to contact a cluster admin.
The panel stays on the dashboard until you select Dismiss. Dismissing it hides it for you only; other owners of the organization still see it. The web UI has no setting to show the panel again after you dismiss it.