Bug 1372730 - Need to tag AWS instances to avoid provisioning volumes in wrong AZ - AWS
Summary: Need to tag AWS instances to avoid provisioning volumes in wrong AZ - AWS
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Ryan Cook
QA Contact: Johnny Liu
URL:
Whiteboard:
Depends On: 1367617
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-02 13:50 UTC by Scott Dodson
Modified: 2016-10-13 19:14 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1367617
Environment:
Last Closed: 2016-10-13 19:14:59 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Scott Dodson 2016-09-02 13:50:44 UTC
+++ This bug was initially created as a clone of Bug #1367617 +++

We don't have documentation to instruct user that they have the possibility to run into the same problem as https://bugzilla.redhat.com/show_bug.cgi?id=1365398 if they are using a shared aws account(as us) and didn't properly tag their instances.
Given an aws account has different instances in different zones, it is vital that the user tag their instances with "Key=KubernetesCluster,Value=<clusterid>". Otherwise they may see their volumes provisioned in unepxected AZ.

Comment 1 Scott Dodson 2016-09-02 13:51:19 UTC
Cloned this for Ryan to look at in AWS provisioning work.

Comment 2 Ryan Cook 2016-10-13 19:14:59 UTC
Scott. I believe we are going to hold off on implementing this until dynamically provisioned volumes is GA. Currently in the Ref Arch document we have people manually provision pvs when they need it. It looks like there is a fix/work around when looking at the initial commit but for the reference architecture we are just going to wait in the event there are major changes when the feature is GA.


Note You need to log in before you can comment on or make changes to this bug.