terraform-google-nomad icon indicating copy to clipboard operation
terraform-google-nomad copied to clipboard

📗 Terraform Module for Nomad clusters with Consul on GCP

Results 10 terraform-google-nomad issues
Sort by recently updated
recently updated
newest added

In step 4, right after executing the command 'terraform plan...' I have the output below, please how can I solve this problem? Terraform v0.12.28 + provider.google v3.65.0 + provider.local v2.1.0...

Client agents do not need to enable connect, [this is only used on servers](https://www.consul.io/docs/connect/configuration#agent-configuration): > Enabling Connect requires changing the configuration of only your Consul servers (not client agents). https://github.com/picatz/terraform-google-nomad/blob/0db159e7c90367553c3c9b61c3a892418d686e36/packer/configs/consul/client.hcl#L30-L32...

enhancement
good first issue
consul

This PR aims to fix #42

enhancement

Currently, there is no way to really tune the Consul integration outside of enabling/disabling Consul ACLs and the default policy. https://github.com/picatz/terraform-google-nomad/blob/8c61d662a89c9633a4b38739716f64b2ffd15bfd/vars.tf#L138-L148 But there are many [options available](https://www.nomadproject.io/docs/configuration/consul#consul-parameters). These should be...

documentation
enhancement
good first issue
consul

GCP now recommends using the new [Ops Agent](https://cloud.google.com/blog/products/operations/ops-agent-now-ga-and-it-includes-opentelemetry) for monitoring and logging. - https://cloud.google.com/stackdriver/docs/solutions/agents/ops-agent - https://cloud.google.com/stackdriver/docs/solutions/agents/ops-agent/installation#install-latest-version - https://cloud.google.com/stackdriver/docs/solutions/agents/ops-agent/authorization

enhancement

Support an option to deploy Vault with [github.com/picatz/terraform-google-vault](https://github.com/picatz/terraform-google-vault)

enhancement

It would be interesting to provide an option to enable running a Firecracker task driver since GCP supports nested virtualization. ## Supporting Documentation * https://github.com/firecracker-microvm/firecracker/blob/main/docs/dev-machine-setup.md#gcp * https://cloud.google.com/compute/docs/instances/nested-virtualization/overview * https://www.nomadproject.io/docs/drivers/external/firecracker-task-driver

enhancement
good first issue

🤦 Following up on https://github.com/picatz/terraform-google-nomad/commit/a1a3f2949220b485e0d37741a0544aef01f53457, when `rootless` and `experimental` were set to `true`, the Docker Daemon still seemed to be running as `root`. So, I seem to be missing something....

enhancement
needs investigation
security

It would probably be a good idea to use [managed instance groups](https://cloud.google.com/compute/docs/instance-groups#managed_instance_groups) for Nomad server and client deployments in the future with the [`compute_instance_group_manager`](https://www.terraform.io/docs/providers/google/r/compute_instance_group_manager.html) Terraform resource. [GoogleCloudPlatform/terraform-google-managed-instance-group](https://github.com/GoogleCloudPlatform/terraform-google-managed-instance-group) looks like a...

enhancement
help wanted
good first issue

Bumps [golang.org/x/crypto](https://github.com/golang/crypto) from 0.1.0 to 0.17.0. Commits 9d2ee97 ssh: implement strict KEX protocol changes 4e5a261 ssh: close net.Conn on all NewServerConn errors 152cdb1 x509roots/fallback: update bundle fdfe1f8 ssh: defer channel...

dependencies
go