[Don't Merge ... Ever] Manually Managed EKS-Solr Deployment #97
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
This grabs the credentials for a bucket and gives a clean output to directly use them
Use the s3creds.sh to optionally update the terraform.tfvars directly if a filename is provided
S3 Credentials will be passed to the terraform backend and the AWS credentials for normal operations will live in the environment
Terraform needs the string variables to be surrounded by double quotes
Terraform does not allow TF vars for backend configuration, so variables must be set in a .conf file and referenced with -backend-config=<file>
nickumia-reisys
force-pushed
the
static-eks
branch
from
f8af021
to
cc24d68
Compare
sed won't replace these characters without quoting them since they are regular expression identifiers
backend.tf is only necessary when running the terraform into an S3 bucket
These additional parameters are important for our deployment
This is only necessary when running bind manually
- Create script to reformat the terraform outputs from 'provision' for 'bind' - Add template for terraform.tfvars - Setup S3 Backend for 'bind'
Grab all required credentials and variables to initialize the solrcloud broker
6 tasks
Fuhu walked through this and was able to grab a kubeconfig from the cluster that I had created.
In case multiple EKS deployments are active, the new instructions describe the process for swapping the EKS backend that the SolrCloud broker is interacting with.
The script should error out if the proper parameters are not passed
Start the documentation on how to copy and/or share AMIs
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.
Related to GSA/data.gov#3807
Mainly to track changes and monitor customizations