simplified #38
Open
simplified #38
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Back to basics with the Akash Provider install on VM infrastructure using Kubespray. We can build up from this with optional extras.
Description
It's a start from scratch using Ansible to configure an Akash Provider on top of a Kubernetes cluster with ArgoCD and Helm charts.
Motivation and Context
We are onboarding more providers and the current DISCO was a bit out of date and tailored more towards being composable and experimental. This repo has been repurposed for helping new providers get setup quickly.
How Has This Been Tested?
Yes, we use these playbooks already for spinning up test environments.
Types of changes
Checklist: