Date
1 - 4 of 4
VMs are not added to AWS ELB target groups
Tsvetan Valchev
Thank you very much for that info.
Do you have any timeline when an official release with AWS v2 can be expected ? |
|
Dmitriy Kalinin
We didnt yet publish cpi release with AWS v2 integration (includes ALBs).
toggle quoted message
Show quoted text
You are welcome to build a local copy (bosh create release --with-tarball) from github.com/cloudfoundry-incubator/bosh-aws-cpi-release. We are planning to promote release with AWS v2 shortly pending stability testing in our pipelines. Feel free to hop into #bosh slack channel for more details. On Wed, Mar 29, 2017 at 9:27 AM, Danny Berger <dberger(a)pivotal.io> wrote:
Instead of `lbtargetgroups`, try `lb_target_groups` - the markup |
|
Danny Berger
Instead of `lbtargetgroups`, try `lb_target_groups` - the markup formatting
toggle quoted message
Show quoted text
on the bosh.io docs page is rendering poorly. Danny On Wed, Mar 29, 2017 at 9:10 AM, Tsvetan Valchev <bgtsetso(a)gmail.com> wrote:
Hi, --
Danny Berger |
|
Tsvetan Valchev
Hi,
In my cloud config descriptor in the vm_types section I have specified that I want the created via bosh deployment VM instances to be added to a specific load balancer target group using the lbtargetgroups attribute, e.g.: vm_types: - name: vm_myserver cloud_properties: { instance_type: m4.xlarge, lbtargetgroups: [my_target_group] } Although the balancer and target groups are already created, the newly created VMs are not added to the target group and I have to do this manually via the aws console. Do you have any ideas? Thanks, Tsvetan |
|