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
Codefresh has added the additional ability to resolve variables storing secrets from remote sources.
9
-
10
-
This allows you to keep sensitive data on your cluster, and for Codefresh to request it during pipeline execution on user's demand.
11
-
12
-
Secret-Store is an additional context in Codefresh, which can be created, updated, deleted, etc, using the Codefresh CLI:`codefresh create context secret-store --help`.
13
-
14
-
At the moment, we support two types of secret storage: Kubernetes (SAAS version) and Runtime-Kubernetes (hybrid deployments).
8
+
Once you have[connected Codefresh to your secrets storage]({{site.baseurl}}/docs/integrations/secret-storage/), you can use them in any pipeline or GUI screen.
15
9
16
10
>Note: This feature is for Enterprise accounts only.
17
11
18
-
##Prerequisites (for Kubernetes secret store)
19
-
20
-
You need to have your Kubernetes cluster[connected to Codefresh]({{site.baseurl}}/docs/deploy-to-kubernetes/add-kubernetes-cluster/).
21
-
(this is only for the Kubernetes type secret store, for runtime-kubernetes[hybrid installation]({{site.baseurl}}/docs/administration/behind-the-firewall/), this is not required)
-`$NAME_IN_CODEFRESH` is a unique name given to your context, which will be referenced in`codefresh.yaml` later.
79
-
-`$CLUSTER` is the name of the cluster as it is configured in Codefresh
80
-
-`$NAMESPACE` is the Kubernetes namespace
81
-
-`$TYPE` is of either`secret` or`configmap`
82
-
- if`secret`, data will be base64 decoded during resolution
83
-
- if`configmap`, data will be replaced as is
84
-
-`$RESOURCE_NAME` is the name of the secret (optional)
85
-
86
-
##Runtime Secret Store (Hybrid Installation)
87
-
88
-
If you are using the[hybrid installation]({{site.baseurl}}/docs/administration/behind-the-firewall/) of Codefresh with the[Runner]({{site.baseurl}}/docs/administration/codefresh-runner/)) you can also store secrets on your own runtime.
89
-
90
-
###Using the Codefresh UI
91
-
92
-
On the left-hand panel, navigate to**Account Settings** >**Integrations** >**Secret Store** and select**Configure**.
93
-
94
-
Click on**Add Provider** and select**Runtime secret store**.
95
-
96
-
For**Runtime** secret store, you need to define the following fields:
97
-
98
-
{% include
99
-
image.html
100
-
lightbox="true"
101
-
file="/images/secrets-ui-view2.png"
102
-
url="/images/secrets-ui-view2.png"
103
-
alt="Runtime Secret Store"
104
-
caption="Runtime Secret Store"
105
-
max-width="80%"
106
-
%}
107
-
108
-
- Name: a unique name given to your context, which will be referenced in`codefresh.yaml` later.
109
-
- Resource name: the name of the secret
110
-
- Runtime environment: select from the dropdown any[runtime environments you have installed]({{site.baseurl}}/docs/enterprise/codefresh-runner/).
111
-
112
-
You can toggle between ConfigMap or Secret, and also toggle the accessibility for users on this account.
113
-
114
-
###Using the Codefresh CLI
115
-
116
-
To create a secret store context for**Runtime-Kubernetes** environments ([behind the firewall]({{site.baseurl}}/docs/enterprise/codefresh-runner/)), run:
description:"Manage Kubernetes secrets with Codefresh"
4
+
group:integrations
5
+
toc:true
6
+
---
7
+
8
+
Codefresh has added the additional ability to resolve variables storing secrets from remote sources.
9
+
10
+
This allows you to keep sensitive data on your cluster, and for Codefresh to request it during pipeline execution on user's demand.
11
+
12
+
Secret-Store is an additional context in Codefresh, which can be created, updated, deleted, etc, using the Codefresh CLI:`codefresh create context secret-store --help`.
13
+
14
+
At the moment, we support two types of secret storage: Kubernetes (SAAS version) and Runtime-Kubernetes (hybrid deployments).
15
+
16
+
>Note: This feature is for Enterprise accounts only.
17
+
18
+
##Prerequisites (for Kubernetes secret store)
19
+
20
+
You need to have your Kubernetes cluster[connected to Codefresh]({{site.baseurl}}/docs/deploy-to-kubernetes/add-kubernetes-cluster/).
21
+
(this is only for the Kubernetes type secret store, for runtime-kubernetes[hybrid installation]({{site.baseurl}}/docs/administration/behind-the-firewall/), this is not required)
-`$NAME_IN_CODEFRESH` is a unique name given to your context, which will be referenced in`codefresh.yaml` later.
81
+
-`$CLUSTER` is the name of the cluster as it is configured in Codefresh
82
+
-`$NAMESPACE` is the Kubernetes namespace
83
+
-`$TYPE` is of either`secret` or`configmap`
84
+
- if`secret`, data will be base64 decoded during resolution
85
+
- if`configmap`, data will be replaced as is
86
+
-`$RESOURCE_NAME` is the name of the secret (optional)
87
+
88
+
##Runtime Secret Store (Hybrid Installation)
89
+
90
+
If you are using the[hybrid installation]({{site.baseurl}}/docs/administration/behind-the-firewall/) of Codefresh with the[Runner]({{site.baseurl}}/docs/administration/codefresh-runner/)) you can also store secrets on your own runtime.
91
+
92
+
###Using the Codefresh UI
93
+
94
+
On the left-hand panel, navigate to**Account Settings** >**Integrations** >**Secret Store** and select**Configure**.
95
+
96
+
Click on**Add Provider** and select**Runtime secret store**.
97
+
98
+
For**Runtime** secret store, you need to define the following fields:
- Name: a unique name given to your context, which will be referenced in`codefresh.yaml` later.
111
+
- Resource name: the name of the secret
112
+
- Runtime environment: select from the dropdown any[runtime environments you have installed]({{site.baseurl}}/docs/enterprise/codefresh-runner/).
113
+
114
+
You can toggle between ConfigMap or Secret, and also toggle the accessibility for users on this account.
115
+
116
+
###Using the Codefresh CLI
117
+
118
+
To create a secret store context for**Runtime-Kubernetes** environments ([behind the firewall]({{site.baseurl}}/docs/enterprise/codefresh-runner/)), run:
-`$NAME_IN_CODEFRESH` is a unique name given to your context, which will be referenced in`codefresh.yaml` later.
133
+
-`$CLUSTER` is the name of the cluster as it is configured in Codefresh
134
+
-`$NAMESPACE` is the Kubernetes namespace
135
+
-`$TYPE` is of either`secret` or`configmap`
136
+
- if`secret`, data will be base64 decoded during resolution
137
+
- if`configmap`, data will be replaced as is
138
+
-`$RESOURCE_NAME` is the name of the secret (optional)
139
+
-`$RUNTIME_NAME` is the name of the run-time environment to be configured as secret store. If not set,*any* runtime-environment will be considered.
140
+
141
+
##Using the secrets
142
+
143
+
Once Codefresh is linked to your secrets you can use them either in pipelines or any relevant section in the Codefresh GUI. See[Using secrets]({{site.baseurl}}/docs/configure-ci-cd-pipeline/secrets-store/) for the details.