Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AWS NLB - controllers #136

Closed

Conversation

pms1969
Copy link
Contributor

@pms1969 pms1969 commented Feb 16, 2018

Controller load balancer set to an AWS NLB

Testing
deployed/destroyed/applied all addons.

ref: #130

@dghubble dghubble self-requested a review February 19, 2018 19:45
Copy link
Member

@dghubble dghubble left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks. I explored this in November, but there were bugs in the AWS provider causing issues. What is the minimum version of the AWS provider you've evaluated this against?

}
}

resource "aws_lb_listener" "apiserver-443" {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Resource naming convention would be apiserver-https if you look at other places in the project.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll provide a change soon'ish. probably tomorrow morning.

resource "aws_lb" "apiserver" {
name = "${var.cluster_name}-apiserver"
load_balancer_type = "network"
subnets = ["${aws_subnet.public.*.id}"]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You've removed the security group

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Disregard, I see network load balancer doesn't allow it.


# Kubelet HTTP health check
health_check {
target = "SSL:443"
protocol = "TCP"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Intentional change?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes. Required to get the healthcheck working with nlb's.

}

resource "aws_lb_target_group_attachment" "apiserver" {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"apiservers" or better yet "controllers" would match the established patterns

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll provide a fix soon changing it to controllers.

@pms1969
Copy link
Contributor Author

pms1969 commented Feb 21, 2018

In answer to your question:

What is the minimum version of the AWS provider you've evaluated this against?

My current setup is.

$ terraform version
Terraform v0.11.3
+ provider.aws v1.9.0
+ provider.ct (unversioned)
+ provider.local v1.1.0
+ provider.null v1.0.0
+ provider.template v1.0.0
+ provider.tls v1.0.1

* Renames lb. Changes suffix from 443 to https.
* Renames target-group-attachment to "controllers".
@dghubble
Copy link
Member

The new minimum version for the terraform-provider-aws plugin is 1.7.0, as established in #141. You won't have to worry about it after all, since that's already made its way to master.

@dghubble
Copy link
Member

Squashed and merged with a few minor tweaks in ceb5555. Thanks!

@dghubble dghubble closed this Feb 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants