skeltonthatcher/aws-terraform-rancher-single-node-ha-elb

Terraform scripts to deploy Rancher server single node HA with SSL and multi-AZ Rancher hosts in AWS

aws-terraform-rancher-single-node-ha-elb's Issues

Connection to host via public access ELB shows weird behaviour

Hi there,

I've been playing around this repo in my sandbox and got an issue related to the hosts accessed via public domain (https://rancher.example.com).

Sometime it lost of connection, but when I check the ELB, the status inService, even no outService at that point the rancher subdomain inaccessible.

I use the latest version (at this point)

RancherOS v1.1.x
Rancher server v2.0.1
Rancher agent v1.6.9

Any comment really helpful.
Thank you

Adapting for Terraform 0.9.2 and above

Terraform remote config has now been removed, you can adapt as follows:

Create a new file in current directory - backend.tf
Contents:

terraform {
  backend "s3" {
    access_key = "AWS _Access_Key"
    secret_key = "AWS_Secret_Key"
  }
}

Modify init.sh

terraform init \
    -backend-config "bucket=${BUCKET}" \
    -backend-config "key=${PROJECT}/terraform.tfstate" \
    -backend-config "region=${REGION}" \
    -backend=true \
    -force-copy \
    -get=true \
    -input=false
}

[feature request] Rancher server HA

Hi @richbos ,

I try to enable full active/active HA of this rancher server.

As I dig into the rancher server config server.tf , the rancher server node doesn't use aws_instance resource to fire up the node, right? It's via resource "aws_launch_configuration" "rancher_srv" { ... }
Because I want to get the private_ip atrrib of the rancher node(s) passed to --advertise-address to create full active/active HA.

I added resource "aws_instance" {...} and passed the ip of the node to --advertise-address, but Terraform ended up fire up one new ec2 node that not part of the rancher server itself.

Any help explanation about this issue, kinda welcome!

Thank you.

IAM Roles Deprecated

iam.tf can be modified to suit:

resource "aws_iam_instance_profile" "rancher" {
  name  = "rancher"
  role = "${aws_iam_role.rancher.name}"
}

Any help ? :)

There are warnings and/or errors related to your configuration. Please
fix these before continuing.

Errors:

• data.aws_route53_zone.selected: Provider doesn't support data source: aws_route53_zone

I set domain like in route53