Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TalOS based control-plane setup on AWS #2

Open
devopstoday11 opened this issue Jul 27, 2022 · 1 comment
Open

TalOS based control-plane setup on AWS #2

devopstoday11 opened this issue Jul 27, 2022 · 1 comment
Assignees
Labels
good first issue Good for newcomers

Comments

@devopstoday11
Copy link
Contributor

With respect to prerequisites from end-user perspective -

Scenario:
When our end user login to intelops UI, the first thing we ask the user is to choose which cloud the User wants to use to set up the Control-Plane we provide & manage for them to set up air-gap control-plane behind the user's network firewall.
So we need to ask user to create a user id in the cloud IAM with full admin rights and we take those credentials (access key, secret key, tokens, password, etc. whatever is relevant to the cloud) in our UI's inputs form.
Using those credentials, we should create TalOS cluster with production-level resources configurations for cpu & memory & storage.
After the cluster is up, going forward we should use the TalOS cluster's API to connect to it & manage it.
So the first piece to deploy automatically as soon as the cluster is ready should be our gRPC agent which establishes the connection between our SaaS side and the control-plane we auto-created for customer inside customer's cloud. From there onwards we should use the TalOS API & gRPC agent to deploy & configure everything we support , into that TalOS cluster.

As first cloud we support we can start with assuming customers have AWS account.

Pramod - work this full automation & setup of TalOS for AWS.

@vpramod03
Copy link
Contributor

#3 Changes are in.

jebinjeb pushed a commit that referenced this issue Jul 20, 2023
mergeback main branch changes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

3 participants