Ended up doing the same thing with a validating webhook using OPA
On Mon, Nov 18, 2019, 4:13 AM Alan Christie <
achris...@informaticsmatters.com> wrote:
> Thanks,
>
> I was wondering whether I could create an arbitrary storage class so (if
> the application can be adjusted to name that class) thi
Thanks,
I was wondering whether I could create an arbitrary storage class so (if the
application can be adjusted to name that class) this might well be a solution.
I’ll poke around today, thanks.
Alan Christie
achris...@informaticsmatters.com
> On 18 Nov 2019, at 12:08 pm, Frederic Giloux
Hi Alan
you can use a storage class for the purpose [1] and pair it with quotas for
the defined storage class [2] as proposed by Samuel.
[1]
https://docs.okd.io/3.11/install_config/storage_examples/storage_classes_legacy.html#install-config-storage-examples-storage-classes-legacy
[2]
https://docs
Not that I know of.
The claimRef is not meant to be changed manually. Once set, PV should have
been bound already, you won't be able to only set a namespace.
Have you considered using ResourceQuotas?
To deny users in a Project from requesting persistent storage, you could
use the following:
apiV
On the topic of volume claim pre-binding …
Is there a pattern for creating volumes that can only be bound to a PVC from a
known namespace, specifically when the PVC name may not be known in advance?
In my specific case I don’t have control over the application's PVC name but I
do know its names
