young-ook / terraform-aws-spinnaker Goto Github PK

Hi!,
Thank for your work, this is the only working spinnaker bootstrap that I've found.

I have to upgrade halyard from 1.44 to 1.45 since spinnaker 1.27 needs the last version.

I don't know how to update halyard, because is not possible to run sudo apt-get in the halyard container (which is the halyard instruction).

Could you help me?

When attempting to run terraform apply in the spinnaker example folder I get the following errors / warnings:

│ Warning: Provider aws is undefined
│
│ on main.tf line 36, in module "spinnaker-managed-role":
│ 36: providers = { aws = aws.prod }
│
│ Module module.spinnaker-managed-role does not declare a provider named aws.
│ If you wish to specify a provider configuration for the module, add an entry for aws in the required_providers
│ block within the module.
╵
╷
│ Error: no matching VPC found
│
│ with module.spinnaker.module.eks.data.aws_vpc.default,
│ on .terraform/modules/spinnaker.eks/network.tf line 4, in data "aws_vpc" "default":
│ 4: data "aws_vpc" "default"

an s3 bucket to store the artefacts from CI tools

First of all, great work!
I am trying to run the complete example under the spinnaker (terraform-aws-spinnaker/examples/spinnaker/main.tf
) and I am getting the following error when I run terraform plan:

Error: Unsupported argument

on main.tf line 53, in module "spinnaker":
53: aurora_instances = {

An argument named "aurora_instances" is not expected here.

Error: Unsupported argument

on main.tf line 59, in module "spinnaker":
59: helm = {

An argument named "helm" is not expected here.

Thank you!

I cloned your repo and running a terraform apply form the root directory, but I get the following:
helm_release.spinnaker: Still creating... [13m40s elapsed]
helm_release.spinnaker: Still creating... [13m50s elapsed]
helm_release.spinnaker: Still creating... [14m0s elapsed]

Error: Kubernetes cluster unreachable: the server has asked for the client to provide credentials

on main.tf line 139, in resource "helm_release" "spinnaker":
139: resource "helm_release" "spinnaker" {

There is no context on "count" variable on vpc.tf

Error: Reference to "count" in non-counted context

  on .terraform/modules/spinnaker/vpc.tf line 101, in resource "aws_route_table" "public":
 101:       "Name" = "${local.name}-public-route-${count.index}"

The "count" object can be used only in "resource" and "data" blocks, and only
when the "count" argument is set.


Error: Reference to "count" in non-counted context

  on .terraform/modules/spinnaker/vpc.tf line 112, in resource "aws_route_table" "private":
 112:       "Name" = "${local.name}-private-route-${count.index}"

The "count" object can be used only in "resource" and "data" blocks, and only
when the "count" argument is set.

Hi there,

I was trying to create a spinnaker-managed-eks by following the example.

However in the Node Group Panel, it shows Access Denied with description Your worker nodes do not have access to the cluster.

Do you have any suggestion to fix this issue? thanks!

Need halyard prefix in s3 bucket for spinnaker for storing secret values.
https://docs.armory.io/spinnaker-install-admin-guides/secrets-s3/