Manage Kubernetes Secrets

​

Introduction

If your GitOps repositories are public, you do not need to create a secret. Secrets are required only when connecting to private Git or Helm repositories that require authentication. A secret stores the credentials that ZEDEDA Edge Kubernetes Service uses to authenticate with a private repository. Create a secret once, then reference it in one or more GitOps repository configurations. Secrets support two authentication types:

• SSH Key Pair: Authenticates using an SSH private key. Used with repositories accessed over SSH.
• HTTP Basic Auth: Authenticates using a username and password or personal access token. Used with repositories accessed over HTTPS.

To navigate to the Secrets list, select Infrastructure > Workloads > Build > Secrets in the sidebar.

​

Create a Secret

1. In the sidebar, navigate to Infrastructure > Workloads > Build > Secrets.
2. Select the contextual + create action. The Create Secret wizard opens.
3. In the Secret Name field, enter a unique name. Names must use only lowercase letters, numbers, and hyphens.
4. In the Project dropdown, select the project this secret belongs to.
5. Under Authentication Type, select SSH Key Pair or HTTP Basic Auth.
6. Complete the fields for the selected authentication type (see the following sections).
7. Select Create Secret.

​

SSH Key Pair fields

​

HTTP Basic Auth fields

​

View Secrets

The Secrets page lists all secrets in the selected project scope. Use the All Projects dropdown to filter by project, or search by name using the search bar. The list shows the following columns: Secrets cannot be edited or deleted after creation through Edge Infrastructure Services. To update credentials, use kubectl to delete the secret from the cluster directly, then create a new secret in Edge Infrastructure Services and update any GitOps repositories that referenced the old secret.

​

Next Steps