Instances in ELB are OutOfService

[Joseph Borg]

Using the charm with a K8s LoadBalancer:

```
Name: veering-sasquatch-drupal
Namespace: default
Labels: app=veering-sasquatch-drupal
                          chart=drupal-3.0.1
                          heritage=Tiller
                          release=veering-sasquatch
Annotations: <none>
Selector: app=veering-sasquatch-drupal
Type: LoadBalancer
IP: 10.152.183.129
LoadBalancer Ingress: a227bf17f571c11e9a0ae060f536a367-404974088.eu-west-2.elb.amazonaws.com
Port: http 80/TCP
TargetPort: http/TCP
NodePort: http 32511/TCP
Endpoints:
Port: https 443/TCP
TargetPort: https/TCP
NodePort: https 31432/TCP
Endpoints:
Session Affinity: None
External Traffic Policy: Cluster
Events:
  Type Reason Age From Message
  ---- ------ ---- ---- -------
  Normal EnsuringLoadBalancer 23m service-controller Ensuring load balancer
  Normal EnsuredLoadBalancer 23m service-controller Ensured load balancer
```

All looks fine from the K8s end, but if I try and access the LoadBalancer Ingress URL I get "The connection was reset".

Looking in the ELB console, it seems the heathchecks fail on all 3 nodes (which are the K8s worker nodes), so they've all been put in "OutOfService" and aren't routed too.

[Tim Van Steenburgh (tvansteenburgh)]

Steps to repro? When I follow the instructions at https://www.ubuntu.com/kubernetes/docs/aws-integration things work fine for me. Is it possible that you forgot to specify a port for your veering-sasquatch-drupal deployment to listen on?

[Joseph Borg (joeborg)]

What region did you try in? I tried that guide in eu-west-2, the instances were "InService" but I still couldn't access the HTTP server.

[Joseph Borg (joeborg)]

Ah, it seems you just have to wait a while for the ELB to settle and DNS to propagate. Once you access the site, via the ELB, the instances move to "InService".