Storage class might fix this issue but am not convinced fully claiming a PV
without using selector. It bypasses protection offer by storage label
selectors. Again, we have to wait for 3.4 and upgrade 3.3. some more work.
--
Srinivas Kotaru
From: Brad Childs
Date: Friday, January 13, 2017 at 1
On Fri, Jan 13, 2017 at 2:05 PM, Srinivas Naga Kotaru (skotaru) <
skot...@cisco.com> wrote:
> Can you explain or point a documentation on how to use storage class? I
> don’t see any document on storage class yet, at least OSE 3.3. I heard that
> feature will be releasing in 3.4.
>
Sorry I should
Can you explain or point a documentation on how to use storage class? I don’t
see any document on storage class yet, at least OSE 3.3. I heard that feature
will be releasing in 3.4.
--
Srinivas Kotaru
From: Brad Childs
Date: Friday, January 13, 2017 at 11:59 AM
To: Srinivas Naga Kotaru
Cc: N
On Fri, Jan 13, 2017 at 12:59 PM, Srinivas Naga Kotaru (skotaru) <
skot...@cisco.com> wrote:
> Perfect, that answer and clarify. Thank you, Nakayama,
>
>
>
>
>
> I was able to bound a PV which has label selectors using a PVC which
> doesn’t have any selectors. This behavior completely makes useles
Brad, can you comment?
On Jan 13, 2017, at 1:59 PM, Srinivas Naga Kotaru (skotaru) <
skot...@cisco.com> wrote:
Perfect, that answer and clarify. Thank you, Nakayama,
I was able to bound a PV which has label selectors using a PVC which
doesn’t have any selectors. This behavior completely make
Perfect, that answer and clarify. Thank you, Nakayama,
I was able to bound a PV which has label selectors using a PVC which doesn’t
have any selectors. This behavior completely makes useless our storage labeling
strategy. We want to label few volumes (special volumes by
cost/performance/size)
I think that following sentence in the docs is wrong(?).
https://docs.openshift.com/container-platform/3.3/install_config/storage_examples/binding_pv_by_label.html
"It is important to note that a claim must match all of the key-value
pairs included in its selector stanza."
In my understanding,