关于“Implementing Role-Based Access Control with Google Kubernetes Engine”的评价

pooja B. · 已于 over 3 years前审核

Valurouthu H. · 已于 over 3 years前审核

Rafi B. · 已于 over 3 years前审核

Anil M. · 已于 over 3 years前审核

Vikas Y. · 已于 over 3 years前审核

Nitin R. · 已于 over 3 years前审核

Kristof D. · 已于 over 3 years前审核

Jurgen D. · 已于 over 3 years前审核

Benoit G. · 已于 over 3 years前审核

Eddy W. · 已于 over 3 years前审核

jan V. · 已于 over 3 years前审核

Eric D. · 已于 over 3 years前审核

Bram V. · 已于 over 3 years前审核

Richa P. · 已于 over 3 years前审核

Pratik B. · 已于 over 3 years前审核

Pratik B. · 已于 over 3 years前审核

Meharaj M. · 已于 over 3 years前审核

MANIKANTA D. · 已于 over 3 years前审核

Mohammed Y. · 已于 over 3 years前审核

good

GONGATI R. · 已于 over 3 years前审核

Veeru N. · 已于 over 3 years前审核

Mac A. · 已于 over 3 years前审核

Rakshith S. · 已于 over 3 years前审核

Subramanyeswara B. · 已于 over 3 years前审核

The "pod-reader" role is poorly-named with respect to its capabilities--if this is a standard convention, it should be called out here, or if there is a reason not to call it "pod-creator" or "pod-manager" or something that implies greater than "get" privileges, that should be pointed out as well.

Jeremy B. · 已于 over 3 years前审核