WIP - Update makefile - Do Not Merge #89
Open
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
- Externalize the .tfvars file - Add target to install a demo user account - Add target to label the worker nodes - Copy the k8s-cluster.yml customizations into the kubespray deploy - Update README
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.
Problem
We need to be able to tie together several processes for deploying workbench, including:
This PR is an initial attempt at creating a makefile to join all of these processes together into a single
paradigm.
Approach
Externalized configuration files used by the Terraform Process and created a makefile command to execute.
Externalized configuration for Kubespray ansible playbook and added makefile command for it too.
Migrated the templates from NDSLabs-Startup and wrote makefile targets to apply each of them.
Status
This is not yet complete and fully functional. Please try out the README and review the overall direction.