Once you have successully completed the browser-based or command-line installation, there are a few additional steps to take before beginning to use the platform.
Final configuration steps#
The installation includes self-signed SSL certificates for encrypting web traffic. While these certificates can be used on a temporary basis to get started, you should replace them with non-self-signed SSL certificates for production operation. See Updating TLS/SSL certificates for information on modifying certificates.
(Gravity only) To add worker nodes to the cluster, follow the instructions here: Adding and removing nodes (Gravity)
Wait for the application to fully stabilize. Anaconda Enterprise can take up to 30 minutes to fully finish loading, depending upon the performance of the cluster network and attached disks. You may be able to log in to the main UI immediately, but sessions and deployments will not be ready to start. To confirm that the cluster is fully loaded, run the following command from the master node:
watch kubectl get pods
The output will look something like this:
Every 2.0s: kubectl get pods aip2: Sat Jan 22 22:21:24 2022 NAME READY STATUS RESTARTS AGE anaconda-enterprise-ap-auth-5c7d6589f7-4fh9m 1/1 Running 0 8m29s anaconda-enterprise-ap-auth-api-cbc8c54df-946pj 1/1 Running 0 8m28s anaconda-enterprise-ap-auth-escrow-57c49f66d5-fnjwx 1/1 Running 0 8m29s anaconda-enterprise-ap-deploy-5c7dbbd7b-l777x 1/1 Running 0 8m28s anaconda-enterprise-ap-docs-5df4f8744c-8qwll 1/1 Running 0 8m28s anaconda-enterprise-ap-git-storage-8597677fbf-dffjn 2/2 Running 0 8m29s anaconda-enterprise-ap-object-storage-54bf8b568b-f5nz7 1/1 Running 0 8m28s anaconda-enterprise-ap-operation-controller-67cdb6cdbb-rfph9 1/1 Running 0 8m28s anaconda-enterprise-ap-repository-95cb86f85-chbt9 1/1 Running 0 8m28s anaconda-enterprise-ap-storage-57668b8765-5r64r 1/1 Running 0 8m28s anaconda-enterprise-ap-ui-56c798bbcb-lrtsh 1/1 Running 0 8m28s anaconda-enterprise-ap-workspace-7ff495c5dd-mg42z 1/1 Running 0 8m28s anaconda-enterprise-app-images-qbtvv 0/3 ContainerCreating 0 8m29s anaconda-enterprise-nginx-ingress-rc-sj55d 1/1 Running 3 8m29s anaconda-enterprise-operation-images-f2bmn 1/1 Running 0 8m28s anaconda-enterprise-postgres-7b947455cf-bd667 1/1 Running 0 8m28s anaconda-enterprise-redis-77d49d5777-22rk4 1/1 Running 0 8m27s generate-certs-dfmsj 0/1 Completed 0 8m28s
Wait for every pod to indicate a status of either
app-imagespods will be the last to stabilize. You can exit the
watchcommand at any time with
Testing your installation#
Once the application has fully loaded, you can do the following to verify that your installation succeeded.
Access the Anaconda Enterprise console by entering the URL of your AE server in a web browser:
anaconda.example.comwith the fully-qualified domain name of the host server.
Log in using the default username and password
Update the passwords for your
adminusers. See Configuring user access for information and steps for updating your password.
Do not alter the
anaconda-enterpriseaccount user name; it is used for certain cluster administration functions.
If you do not update your passwords, anyone with the default credentials will be able to access your admin console. This poses a security risk, so it is important to change these passwords immediately.
You can verify a successful installation by doing any or all of the following:
Creating a new project and starting an editing session
Deploying a project
Generating a token from a deployment
Some of the sample projects can only be deployed after mirroring the package repository. To test your installation without doing this first, you can deploy the “Hello Anaconda Enterprise” sample project.
Now that you’ve completed these essential steps, you can do any of the following optional steps: