FIX #72 for LoadBalancer creation on AWS

kube-controller-manager and kube-apiserver service unit files are missing
one option --cloud-provider=aws parameter, which is creating problem while
creating ELB on AWS when type: LoadBalancer is provided in service YAML file.
This commit fixes that, issue
pull/101/merge
ksingh7 2017-01-08 00:31:31 +02:00 committed by Kelsey Hightower
parent e465ee81f1
commit 4ad918e7c6
1 changed files with 3 additions and 0 deletions

View File

@ -176,6 +176,7 @@ RestartSec=5
WantedBy=multi-user.target
EOF
```
- Note: If you are deploying this on AWS then you should add ``--cloud-provider=aws`` in the ``kube-apiserver.service`` unit file's [service] section. If you are adding this before ``--v=2`` line, remember to add ``\`` character at the end
```
sed -i s/INTERNAL_IP/$INTERNAL_IP/g kube-apiserver.service
@ -222,6 +223,8 @@ RestartSec=5
WantedBy=multi-user.target
EOF
```
- Note: If you are deploying this on AWS then you should add ``--cloud-provider=aws`` in the ``kube-controller-manager.service`` unit file's [service] section. If you are adding this before ``--v=2`` line , remember to add ``\`` character at the end.
```
sed -i s/INTERNAL_IP/$INTERNAL_IP/g kube-controller-manager.service