STACKIT Container Registry now supports Service Accounts
Section titled “STACKIT Container Registry now supports Service Accounts”We are excited to announce that you can now map STACKIT Service Accounts directly to Robot Accounts within the STACKIT Container Registry!
This update aligns the Container Registry’s local authentication mechanism with the broader platform’s identity provider, enabling secure, automated CI/CD workflows for pushing and pulling container images. These are the key benefits it brings:
- Enhanced Security & Token-Based Auth: Move away from hardcoded, long-lived robot secret keys.
- Centralized Identity Management: Leverage centrally managed STACKIT Service Account credentials, eliminating fragmented identity management across your repositories.
- Granular Permission Mapping: Seamlessly assign specific roles and technical permissions (such as image Push, Pull, or Delete) to the mapped STACKIT Service Account within specific Registry projects.
Now, the lifecycle of your identity is securely governed by the STACKIT Portal, while the scope of technical permissions remains fully managed within your Registry resource. Check out our step-by-step guide to learn more.