Ordering Secrets Store Access¶
We manage access to the Secrets Store. Once you have access, you create and manage the secrets in your own path. This page describes how to order access.
How to Order¶
Open a ticket in our Service Desk. State that you want Secrets Store access and include the information below.
Information to Include¶
| Field | Required | Description | Example |
|---|---|---|---|
| Team | Yes | The team the path belongs to. We use it to name the path. | your-team |
| Identities | Yes | The users or identity provider groups that need access. These are the same identities you use to access the Kubernetes API. | your-team-developers group |
| Access level | Yes | Whether each identity can read only, or read and write. See Options. | Read and write |
| Store | No | The shared store, or your dedicated store if you have one. | Shared |
| Technical contact | Yes | The person we contact about the access. | Name and email |
Options¶
| Option | Choices | Guidance |
|---|---|---|
| Access level | Read, or read and write | Give write access only to the people who maintain secrets. Applications read secrets through the Secrets service, not through your user access. |
| Path layout | One path per team, with sub-paths you create | See path policies for how paths map to what your namespaces can read. |
| Store | Shared or dedicated | A dedicated store isolates your secrets from other customers and has its own address. |
What You Receive¶
When access is ready, your identities can log in with the oidc method, and we
tell you your dedicated path, for example kv/your-team/.
Changes and Cancellation¶
To add or remove identities or change access levels, open a new Service Desk ticket that names the path and the change you need.
Next Steps¶
- Getting Started shows how to log in and manage secrets.