Updated by Igor Mameshin
Accessing the Control Plane
Upon sign-up, your administrator should have received an onboarding email which includes your username, and a link to reset your password. We use Okta for account management, Single-Sign-On, and third party auth integration. As part of the onboarding process, you will have an organization created within Okta, as well as in the AgileStacks Control Plane.
After you have set your password, you are ready to proceed to logging into the Control Plane.
Simply open a browser and navigate to : controlplane.agilestacks.io
You can navigate here by clicking the "Stacks > Clusters > List" menu in the top nav bar.
The Stacks screen shows a list of all the stack instances or clusters in the current organization that you have permissions to see. For each stack, you can see the environment where it is deployed, the owner, the status, the cloud regions where it is deployed, and the date it was created.
You may have several stacks already created by your administrator. If you don't see any Stacks on this page, then you need to create a new Stack from a Stack template. You may also need to onboard a cloud account, create an environment, and create a stack template. Refer to Creating Stacks for additional details about creating stacks.
To perform actions on a Stack, or to view more details, click on the Actions button and then "View Details". In the Stack Details screen, you can execute operations such as Undeploy, Update, or Repair.
On the Stack Details page, you can see the link to the stack template it was created from (ML Stack), the link to the environment (DEV01), the base stack, the status, and the history of deployment.
To access stack components and tools deployed in the stacks, navigate to the Components tab and click on the buttons for stack components, for example Traefik, Kubeflow, Dashboard, Harbor.
To manage Kubernetes cluster, navigate to the Kubernetes tab where you can download Kubeconfig file for this cluster, or manage the size of the cluster by clicking "Add workers" button. You can also change the configuration of worker pools available on this page.
Stack Templates Section
You can navigate here by clicking the "Template > Stack Templates > List" menu in the top nav bar.
You may have several stack templates already created by your administrator. If you don't see any Stack Templates on this page, then you need to create a new Stack Template. Refer to Create a Stack Template for additional details about creating templates.
To view more details about a stack template, click on "Details" button. In the Stack Template Details screen, you can execute operations such as Deploy and Delete. The source code for stack template is stored in a Git repository. You can copy the URL in Template Source Code field and clone it to your workstation to review or modify code.
Note: click "Show Secret URL" button before cloning the repository. Secret URL includes a secret token that for Git authentication.
You can use git clone command to download stack template repository. For example:
git clone https://firstname.lastname@example.org/repo/demo05/ml-stack-1735
If you have appropriate permissions, you can change the existing template. For example, you can add another Terraform file, or edit the variables. Once you complete the changes, push your updates to Git. Your updated template can be used to create new stacks or update existing stacks.
You can also delete a template, in which case it can no longer be used to create stacks. As a template owner you can update permissions to read and write the template using "Teams and Permissions" list on the Stack Template screen.
You can navigate here by clicking the "Administration" button in the top nav bar.
As a team platform Admin, you may
- Setup payment controls
- Register cloud accounts
- Manage 3rd party Licenses
Here would be a good opportunity to create any teams or users that you require. Teams are used to provide granular access control to Environments, Stack Templates, and Applications.
Note that users with Write access can make changes to objects like, Environment and Templates and permissions for them
A user with read access can view objects, like Clouds, Environments and Templates.