Mixing
Kubernetes storing key-value pair in Secret.yml
I am wondering if it is possible to store a key-value pair in Secret.yml.
I want to be able to store an encryption key as a value and an id as its key which I can use to retrieve the encryption key stored in Secret.yml.
Is such functionality available with Kubernetes?
EDIT
I should have said in my original message, I want to be able to store multiple pairs and add pairs during the lifespan of my application and use different encryption key on the fly without/minimal update to my application.
kubernetes kubernetes-secrets asked Nov 19 '18 at 13:47
boringDeveloper
84
add a comment |
I am wondering if it is possible to store a key-value pair in Secret.yml.
I want to be able to store an encryption key as a value and an id as its key which I can use to retrieve the encryption key stored in Secret.yml.
Is such functionality available with Kubernetes?
EDIT
I should have said in my original message, I want to be able to store multiple pairs and add pairs during the lifespan of my application and use different encryption key on the fly without/minimal update to my application.
kubernetes kubernetes-secrets asked Nov 19 '18 at 13:47
boringDeveloper
84
add a comment |
I am wondering if it is possible to store a key-value pair in Secret.yml.
I want to be able to store an encryption key as a value and an id as its key which I can use to retrieve the encryption key stored in Secret.yml.
Is such functionality available with Kubernetes?
EDIT
I should have said in my original message, I want to be able to store multiple pairs and add pairs during the lifespan of my application and use different encryption key on the fly without/minimal update to my application.
kubernetes kubernetes-secrets asked Nov 19 '18 at 13:47
boringDeveloper
84
I am wondering if it is possible to store a key-value pair in Secret.yml.
I want to be able to store an encryption key as a value and an id as its key which I can use to retrieve the encryption key stored in Secret.yml.
Is such functionality available with Kubernetes?
EDIT
I should have said in my original message, I want to be able to store multiple pairs and add pairs during the lifespan of my application and use different encryption key on the fly without/minimal update to my application.
kubernetes kubernetes-secrets kubernetes kubernetes-secrets asked Nov 19 '18 at 13:47
boringDeveloper
84
asked Nov 19 '18 at 13:47
boringDeveloper
84
edited Nov 19 '18 at 14:10
asked Nov 19 '18 at 13:47
boringDeveloper
84
asked Nov 19 '18 at 13:47
boringDeveloper
84
asked Nov 19 '18 at 13:47
boringDeveloper
84
84
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
Yes, secrets are key value pairs. You can create them using kubectl:
kubectl create secret the-secret-name --from-literal=KEY=VALUE
Then, you can look at / edit the yaml specification via
#get
kubectl get secret the-secret-name -o yaml
#edit
kubectl edit secret the-secret-name
A secret looks like this:
apiVersion: v1
kind: Secret
metadata:
name: the-secret-name
type: Opaque
data:
# the value is base64 encoded
KEY: VkFMVUUK
Most of the time, it's better to use two key value pairs in your situation though. The reason for this is that it's more complicated/expensive to look for a key with an unknown name than to lookup a value under a key.
answered Nov 19 '18 at 13:57
tback
6,70142856
add a comment |
Kubernetes secret stores data as key value pair(ref: https://kubernetes.io/docs/concepts/configuration/secret/).
apiVersion: v1
kind: Secret
metadata:
name: mysecret
type: Opaque
data:
key: dmFsdWU=
Here value is base64 encoded.
answered Nov 19 '18 at 13:55
nightfury1204
1,43048
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53376021%2fkubernetes-storing-key-value-pair-in-secret-yml%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Yes, secrets are key value pairs. You can create them using kubectl:
kubectl create secret the-secret-name --from-literal=KEY=VALUE
Then, you can look at / edit the yaml specification via
#get
kubectl get secret the-secret-name -o yaml
#edit
kubectl edit secret the-secret-name
A secret looks like this:
apiVersion: v1
kind: Secret
metadata:
name: the-secret-name
type: Opaque
data:
# the value is base64 encoded
KEY: VkFMVUUK
Most of the time, it's better to use two key value pairs in your situation though. The reason for this is that it's more complicated/expensive to look for a key with an unknown name than to lookup a value under a key.
answered Nov 19 '18 at 13:57
tback
6,70142856
add a comment |
Yes, secrets are key value pairs. You can create them using kubectl:
kubectl create secret the-secret-name --from-literal=KEY=VALUE
Then, you can look at / edit the yaml specification via
#get
kubectl get secret the-secret-name -o yaml
#edit
kubectl edit secret the-secret-name
A secret looks like this:
apiVersion: v1
kind: Secret
metadata:
name: the-secret-name
type: Opaque
data:
# the value is base64 encoded
KEY: VkFMVUUK
Most of the time, it's better to use two key value pairs in your situation though. The reason for this is that it's more complicated/expensive to look for a key with an unknown name than to lookup a value under a key.
answered Nov 19 '18 at 13:57
tback
6,70142856
add a comment |
Yes, secrets are key value pairs. You can create them using kubectl:
kubectl create secret the-secret-name --from-literal=KEY=VALUE
Then, you can look at / edit the yaml specification via
#get
kubectl get secret the-secret-name -o yaml
#edit
kubectl edit secret the-secret-name
A secret looks like this:
apiVersion: v1
kind: Secret
metadata:
name: the-secret-name
type: Opaque
data:
# the value is base64 encoded
KEY: VkFMVUUK
Most of the time, it's better to use two key value pairs in your situation though. The reason for this is that it's more complicated/expensive to look for a key with an unknown name than to lookup a value under a key.
answered Nov 19 '18 at 13:57
tback
6,70142856
Yes, secrets are key value pairs. You can create them using kubectl:
kubectl create secret the-secret-name --from-literal=KEY=VALUE
Then, you can look at / edit the yaml specification via
#get
kubectl get secret the-secret-name -o yaml
#edit
kubectl edit secret the-secret-name
A secret looks like this:
apiVersion: v1
kind: Secret
metadata:
name: the-secret-name
type: Opaque
data:
# the value is base64 encoded
KEY: VkFMVUUK
Most of the time, it's better to use two key value pairs in your situation though. The reason for this is that it's more complicated/expensive to look for a key with an unknown name than to lookup a value under a key.
answered Nov 19 '18 at 13:57
tback
6,70142856
edited Nov 19 '18 at 14:02
answered Nov 19 '18 at 13:57
tback
6,70142856
answered Nov 19 '18 at 13:57
tback
6,70142856
answered Nov 19 '18 at 13:57
tback
6,70142856
6,70142856
add a comment |
add a comment |
Kubernetes secret stores data as key value pair(ref: https://kubernetes.io/docs/concepts/configuration/secret/).
apiVersion: v1
kind: Secret
metadata:
name: mysecret
type: Opaque
data:
key: dmFsdWU=
Here value is base64 encoded.
answered Nov 19 '18 at 13:55
nightfury1204
1,43048
add a comment |
Kubernetes secret stores data as key value pair(ref: https://kubernetes.io/docs/concepts/configuration/secret/).
apiVersion: v1
kind: Secret
metadata:
name: mysecret
type: Opaque
data:
key: dmFsdWU=
Here value is base64 encoded.
answered Nov 19 '18 at 13:55
nightfury1204
1,43048
add a comment |
Kubernetes secret stores data as key value pair(ref: https://kubernetes.io/docs/concepts/configuration/secret/).
apiVersion: v1
kind: Secret
metadata:
name: mysecret
type: Opaque
data:
key: dmFsdWU=
Here value is base64 encoded.
answered Nov 19 '18 at 13:55
nightfury1204
1,43048
Kubernetes secret stores data as key value pair(ref: https://kubernetes.io/docs/concepts/configuration/secret/).
apiVersion: v1
kind: Secret
metadata:
name: mysecret
type: Opaque
data:
key: dmFsdWU=
Here value is base64 encoded.
answered Nov 19 '18 at 13:55
nightfury1204
1,43048
answered Nov 19 '18 at 13:55
nightfury1204
1,43048
answered Nov 19 '18 at 13:55
nightfury1204
1,43048
answered Nov 19 '18 at 13:55
nightfury1204
1,43048
1,43048
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53376021%2fkubernetes-storing-key-value-pair-in-secret-yml%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
