Nexastack is a Multi-Cloud Platform to automate Infrastructure for Multi-Cloud as well as capable of deployment on Kubernetes.
Currently, it supports Helm, Terraform, and Ansible.
Workflow is a manifest file that contains a set of tasks that will be executed sequentially or parallel in Nexastack. It has a fully-featured workflow engine that is intended to use for Automation Frameworks only.
You can add those modules to your GitHub repository and create a workflow that can use the existing modules.
To automate Terraform modules through Nexastack, you first have to integrate your cloud credentials , nd you can create a workflow using visual editor according to your terraform modules.
Users have to add the Kube config of the working cluster to the Infrastructure. Also, a user has to create a workflow according to the helm charts.
Nexastack is currently supporting GitHub. Bitbucket and GitLab are planned for Next Released.
Yes, Nexastack allows you to manage Infrastructure for GCP and AWS.
You can deploy the application's Helm charts on Supported Cloud Providers in Multi-Cloud Architecture using workflow.
It depends on the no of tasks in the workflow and also the duration of these tasks.
Any member of the project can create a workflow.
Only Admin of the project and the owner of the workspace can add the Infrastructure.
A Registry is the collection of different modules of Ansible, Terraform, and Helm, and a user can add them to the workflow using web UI.
You can either add a module in GitHub or add it from the registry using web UI.
Yes, you can add modules directly to the GitHub repository.
Yes, there can be multiple admins of a workspace.
Yes, you can add your custom modules to the GitHub repository.
No, you can't add modules to the registry at this moment. Nexastack will be supporting the Private Registry in the future.
You can easily change them through GitHub IDE or on your local like any code and push it to IaC Repository.