Infrasnap for Google Cloud MAX

Components
Artifact Registry in Google Cloud
GCP Kubernetes Cluster
Flexible VPC setup in GCP
Kubernetes ESO for Google Cloud Secret Manager
DNS Management	Cloudflare
Infrastructure CI/CD pipeline	Bitbucket Pipelines Drone CI Bitbucket Pipelines GitHub Actions Gitlab CI
Ingress Controller	Nginx Nginx Traefik
Autoscaling	KEDA
CI/CD Runner	Gitlab CI Runner Gitlab CI Runner Bitbucket Pipelines Runner Drone Server and Runner GitHub Actions Runner
Caching	Memorystore
Monitoring	Prometheus/Grafana/Loki
Object Storage	Cloud Storage Buckets
Queue Manager	Pub/Sub
SQL Database	MySQL and PostgreSQL
Helm Chart
Setup by Corewide team
Post-implementation training
2-week warranty support
Documentation

$12,060

License

Once you have a Corewide Solutions Portal account, this one-time action will use your browser session to retrieve credentials:

 shellterraform login solutions.corewide.com

Provision instructions

Download Infrasnap archive from My Library page, unpack it to a new directory and initialize a new project there:

 shellcd infrasnap/
git init
git add .

Follow the instructions in README.md:

Pass cloud provider API credentials as Terraform variables (as terraform.tfvars, or using environment variables)
Edit infrasnap.yml parameters based on the reference below
Prepare Terraform backend configuration in backend.tf

Initialize the setup, create the environment you configured in infrasnap.yml and provision the infrastructure:

 shellterraform init
terraform workspace new <environment_name>
terraform workspace select <environment_name>
terraform apply

Variable	Description	Type	Default	Required	Sensitive
`cloudflare_api_token`	Cloudflare API token with DNS management permissions for all DNS zones managed in the setup. This can also be sourced from the `CLOUDFLARE_API_TOKEN` environment variable	`string`		no	yes

Variable	Description	Type	Default
`dns_zone_create`	Whether to create DNS zone or use the existing one	`bool`	`false`
`dns_zone`	DNS zone in which to create records, disable to reuse the same zone from another workspace	`string`	`example.com`
`dns_records_k8s`	A list of subdomains that must point at Ingress LoadBalancer	`list`
`dns_proxied_records_k8s`	A list of subdomains that must be proxied by Cloudflare and point at Ingress LoadBalancer	`list`
`dns_records`	List of extra records that do not point at Ingress LoadBalancer See module_docs for complete reference	`map`
`dns_records.www`	Name of the DNS record	`map`
`dns_records.www.type`	The type of the record. Possible values are: `A`, `AAAA`, `CNAME`, `MX`, `NS` and `TXT`	`string`	`CNAME`
`dns_records.www.value`	The content of the record	`list`	`['test']`
`cloudflare_account_id`	Cloudflare account ID in which to manage the DNS zone resources	`NoneType`
`cert_manager_email`	E-mail that Let's Encrypt cluster issuer will use to request certificates	`string`	`[email protected]`
`keda`	Parameters for KEDA deployment	`map`
`keda.prometheus`	KEDA Prometheus integration configuration parameters	`map`
`keda.prometheus.create_service_monitor`	Indicates if a ServiceMonitor should be created for Prometheus monitoring	`bool`	`true`

Output	Description	Type	Sensitive
`name_servers`	Name servers of DNS zone managed in this workspace	`attribute`	no
`keda_namespace`	The namespace where KEDA is installed	`attribute`	no
`keda_service_account_name`	The name of the ServiceAccount used by KEDA	`attribute`	no

Not sure where to start?Let's find your perfect match.