4 ms·
While I agree with your position that admin rights should not be the default, that doesn't seem to be what Argo is actually doing. The text snippet you've incl
by nrmitchi 8y ago
While I agree with your position that admin rights should not be the default, that doesn't seem to be what Argo is actually doing.
The text snippet you've included is from the quick start/demo page, which seems to be targeted at getting the examples running quickly so that a potential user can see what it is capable of. Other issues for this in a production setup would be the use of the 'default' role/namespace at all. In this use case (running the examples in a new cluster), giving the default user full access is the quickest way to this result.
Clearly it would be better if Argo included a more precise (permission wise) role by default, but from my understanding Argo does not require cluster admin permissions in order to function.
- TheDong 8y agoThe parent post did quality it appropriately with "if the docs are even close to representative of the actual application". I hope the docs are not representative, but the parent post is right that it's a bad sign. At least put up a warning sign that it's insecure and only suitable for demo purposes to do that.
- jessesuen 8y agoThanks. We've updated the docs to outline the bare minimum set of privileges.