-
Notifications
You must be signed in to change notification settings - Fork 12
Cluster/Infra Creation Epic #585
Comments
Have we checked with the other groups about their need for cached data?
Are we requiring that a custom repo follows the same Bedrock directory structure?
What exactly will be in here? |
@andrebriggs
Are we requiring that a custom repo follows the same Bedrock directory structure?
What exactly will be in here?
---
Bedrock_Repo: True
Deployment_Name: Azure-ECK-Simple
Terraform_Version: 0.12.3
Bedrock_Source: (URL/LocalPath)
Data_Resources: [resource_group_name]
TFvars:
{
resource_group_name = "resource-group-name"
cluster_name = "cluster-name"
agent_vm_count = "3"
dns_prefix = "dns-prefix"
service_principal_id = "client-id"
service_principal_secret = "client-secret"
ssh_public_key = "public-key"
gitops_ssh_url = "[email protected]:timfpark/fabrikate-cloud-native-manifests.git"
gitops_ssh_key = "<path to private gitops repo key>"
vnet_name = "<vnet name>"
} |
After reaching out to other teams, it appears that there could be a need to have some sort of "cached data". Service Introspection may need store keys, and Service Creation potentially may need to store spk logs or PATs. Regardless, there is a need (currently) for infra. |
@andrebriggs @yradsmikham Can this be closed? |
Yes, it looks complete. |
Spikes
Terraform work
CLI Work
spk infra validate
(and alsospk init
)spk infra scaffold --name <env name> --source <bedrock git url> --template <env template>
spk infra validate
has run (check for existence of ~./spk/spk-config.yaml infra block)--source
argument (potentially to atmp
directory)definition.yaml
file with parameters like environment name, template name, and variables from avariables.tf
definition.yaml
(if it exists)spk infra generate --name <env name>
tmp
directory)definition.yaml
fileterraform.tfvars
with values that are unique to the clusterdefinition.yaml
Considerations:
The text was updated successfully, but these errors were encountered: