You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In our customer & prospect conversations and POVs, we are hearing more and more frequently about RBAC & security patterns. People want to know how to manage their secrets, and provide promises access to the appropriate secrets for each team. RBAC concerns are both around securing the platform cluster, access to promises and access to resources.
Note
RBAC is out of scope for this blog
This miro board describes our recommended approach to this pattern. We want to write up a blog to explain this pattern to people using Kratix on docs.kratix.io
Tip
Consider using the GACC framework and get a review of that before writing everything up
Done When
Blog written that describes secuirty and platforms
Blog has been reviewed by @cghsystems & @catmo-syntasso (if they are around), and someone from CA if not
Blog published on syntasso.io/blog
CA informed so they can share/shoutabout/whatever they need to do
cghsystems
changed the title
blog: Document vault pattern for secrets management
blog: Document vault pattern for secrets management (part 1)
Jan 15, 2025
cghsystems
changed the title
blog: Document vault pattern for secrets management (part 1)
blog: Document why security matters in platforms (part 1)
Jan 15, 2025
In our customer & prospect conversations and POVs, we are hearing more and more frequently about RBAC & security patterns. People want to know how to manage their secrets, and provide promises access to the appropriate secrets for each team. RBAC concerns are both around securing the platform cluster, access to promises and access to resources.
Note
RBAC is out of scope for this blog
This miro board describes our recommended approach to this pattern. We want to write up a blog to explain this pattern to people using Kratix on docs.kratix.io
Tip
Consider using the GACC framework and get a review of that before writing everything up
Done When
See GACC for more information
The text was updated successfully, but these errors were encountered: