Skip to content
This repository has been archived by the owner on Nov 20, 2023. It is now read-only.

etcd nodes separate from masters in aws #365

Open
mbach04 opened this issue Apr 1, 2019 · 1 comment
Open

etcd nodes separate from masters in aws #365

mbach04 opened this issue Apr 1, 2019 · 1 comment
Assignees
Labels

Comments

@mbach04
Copy link
Contributor

mbach04 commented Apr 1, 2019

Currently etcd nodes are staged to be deployed separately in the AWS deployer and should deploy converged with the Masters as recommended by 3.11 architecture documentation.

Removing etcd from the cloud infrastructure definitions in group_vars/all.yaml results in a failed process of the cloudformations template.

Removing etcdnodes from the cloudformations template (casl-ansible/roles/manage-aws-infra/defaults/main.yml) results in AnsibleUndefinedVariable: 'aws_etcd_zones' is undefined.

@makentenza
Copy link
Contributor

I'm a bit confused here @mbach04, why are you editing defaults/main.yml file? This is not the way to customise your infra "skeleton". That Ansible dictionary must be configured in your inventory.

@makentenza makentenza self-assigned this May 1, 2019
@makentenza makentenza added the AWS label May 1, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants