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

Subnets in existing VPC requite alphabetical order annotations #771

Open
JoshVanL opened this issue Mar 14, 2019 · 0 comments
Open

Subnets in existing VPC requite alphabetical order annotations #771

JoshVanL opened this issue Mar 14, 2019 · 0 comments
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@JoshVanL
Copy link
Contributor

Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug

What happened:
Vault instances were not able to attach volumes as they existed in a different zone.
This was caused by vault instances to be deployed in the wrong zones due to miss ordering of subnets in network annotations in an existing VPC.

What you expected to happen:
Tarmak should sort the subnet list and pair with ebs volumes in the same zone.

How to reproduce it (as minimally and precisely as possible):
Create annotations of subnets that are miss orderd,

subnet-private: sub-zone-c,sub-zone-a,sub-zone-b
subnet-public: sub-zone-c,sub-zone-a,sub-zone-b

Anything else we need to know?:
Ordering of subnets described in the instance pool will be sorted correctly.

Environment:

  • Kubernetes version (use kubectl version):
  • Cloud provider or hardware configuration**:
  • Install tools:
  • Others:
@jetstack-bot jetstack-bot added the kind/bug Categorizes issue or PR as related to a bug. label Mar 14, 2019
@simonswine simonswine changed the title Subnets in expisting vpc requite alphabetical order annotations Subnets in existing VPC requite alphabetical order annotations Mar 15, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

2 participants