MountVolume.SetUp failed for volume “realm-secret” : secrets “realm-secret” not found
I am trying to get keycloak up and running on my minikube.
I am installing keycloak with
helm upgrade -i -f kubernetes/keycloak/values.yaml keycloak stable/keycloak --set keycloak.persistence.dbHost=rolling-newt-postgresql
I see an error in dashboard that says:
MountVolume.SetUp failed for volume "realm-secret" : secrets
"realm-secret" not found
In my values.yaml
I have this configuration:
extraVolumes: |
- name: realm-secret
secret:
secretName: realm-secret
- name: theme
emptyDir: {}
- name: spi
emptyDir: {}
extraVolumeMounts: |
- name: realm-secret
mountPath: "/realm/"
readOnly: true
- name: theme
mountPath: /opt/jboss/keycloak/themes/mytheme
- name: spi
mountPath: /opt/jboss/keycloak/standalone/deployments
I also have a realm.json
file.
Question
What do I need to do with this real.json
file prior to installing keycloak? How do I do that ?
kubernetes keycloak
add a comment |
I am trying to get keycloak up and running on my minikube.
I am installing keycloak with
helm upgrade -i -f kubernetes/keycloak/values.yaml keycloak stable/keycloak --set keycloak.persistence.dbHost=rolling-newt-postgresql
I see an error in dashboard that says:
MountVolume.SetUp failed for volume "realm-secret" : secrets
"realm-secret" not found
In my values.yaml
I have this configuration:
extraVolumes: |
- name: realm-secret
secret:
secretName: realm-secret
- name: theme
emptyDir: {}
- name: spi
emptyDir: {}
extraVolumeMounts: |
- name: realm-secret
mountPath: "/realm/"
readOnly: true
- name: theme
mountPath: /opt/jboss/keycloak/themes/mytheme
- name: spi
mountPath: /opt/jboss/keycloak/standalone/deployments
I also have a realm.json
file.
Question
What do I need to do with this real.json
file prior to installing keycloak? How do I do that ?
kubernetes keycloak
add a comment |
I am trying to get keycloak up and running on my minikube.
I am installing keycloak with
helm upgrade -i -f kubernetes/keycloak/values.yaml keycloak stable/keycloak --set keycloak.persistence.dbHost=rolling-newt-postgresql
I see an error in dashboard that says:
MountVolume.SetUp failed for volume "realm-secret" : secrets
"realm-secret" not found
In my values.yaml
I have this configuration:
extraVolumes: |
- name: realm-secret
secret:
secretName: realm-secret
- name: theme
emptyDir: {}
- name: spi
emptyDir: {}
extraVolumeMounts: |
- name: realm-secret
mountPath: "/realm/"
readOnly: true
- name: theme
mountPath: /opt/jboss/keycloak/themes/mytheme
- name: spi
mountPath: /opt/jboss/keycloak/standalone/deployments
I also have a realm.json
file.
Question
What do I need to do with this real.json
file prior to installing keycloak? How do I do that ?
kubernetes keycloak
I am trying to get keycloak up and running on my minikube.
I am installing keycloak with
helm upgrade -i -f kubernetes/keycloak/values.yaml keycloak stable/keycloak --set keycloak.persistence.dbHost=rolling-newt-postgresql
I see an error in dashboard that says:
MountVolume.SetUp failed for volume "realm-secret" : secrets
"realm-secret" not found
In my values.yaml
I have this configuration:
extraVolumes: |
- name: realm-secret
secret:
secretName: realm-secret
- name: theme
emptyDir: {}
- name: spi
emptyDir: {}
extraVolumeMounts: |
- name: realm-secret
mountPath: "/realm/"
readOnly: true
- name: theme
mountPath: /opt/jboss/keycloak/themes/mytheme
- name: spi
mountPath: /opt/jboss/keycloak/standalone/deployments
I also have a realm.json
file.
Question
What do I need to do with this real.json
file prior to installing keycloak? How do I do that ?
kubernetes keycloak
kubernetes keycloak
edited Nov 23 '18 at 19:43
EpicPandaForce
49.2k14131255
49.2k14131255
asked Nov 23 '18 at 16:49
AnthonyAnthony
9,8752292179
9,8752292179
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The reason is you are referencing a secret named realm-secret
in extraVolumes
, but that secret with name realm-secret
is created neither by the helm chart (named stable/keycloak
) nor by you manually.
You can easily find that chart in https://github.com/helm/charts/tree/master/stable/keycloak.
Solution:
In values.yaml, the field extraVolume
and extraVolumeMount
is kept to provide an extra volume and extra volumeMount by user if they need. They will be used in keycloak pod. So if you need to provide extraVolumes
that will mount a secret, then you have to create that secret all by yourself. So, create secret realm-secret
in the same namespace in which you install/upgrade your chart. And only then install/upgrade the chart.
$ kubectl create secret generic realm-secret --namespace=<chart_namespace> --from-file=path/to/realm.json
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%2f53450402%2fmountvolume-setup-failed-for-volume-realm-secret-secrets-realm-secret-not%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The reason is you are referencing a secret named realm-secret
in extraVolumes
, but that secret with name realm-secret
is created neither by the helm chart (named stable/keycloak
) nor by you manually.
You can easily find that chart in https://github.com/helm/charts/tree/master/stable/keycloak.
Solution:
In values.yaml, the field extraVolume
and extraVolumeMount
is kept to provide an extra volume and extra volumeMount by user if they need. They will be used in keycloak pod. So if you need to provide extraVolumes
that will mount a secret, then you have to create that secret all by yourself. So, create secret realm-secret
in the same namespace in which you install/upgrade your chart. And only then install/upgrade the chart.
$ kubectl create secret generic realm-secret --namespace=<chart_namespace> --from-file=path/to/realm.json
add a comment |
The reason is you are referencing a secret named realm-secret
in extraVolumes
, but that secret with name realm-secret
is created neither by the helm chart (named stable/keycloak
) nor by you manually.
You can easily find that chart in https://github.com/helm/charts/tree/master/stable/keycloak.
Solution:
In values.yaml, the field extraVolume
and extraVolumeMount
is kept to provide an extra volume and extra volumeMount by user if they need. They will be used in keycloak pod. So if you need to provide extraVolumes
that will mount a secret, then you have to create that secret all by yourself. So, create secret realm-secret
in the same namespace in which you install/upgrade your chart. And only then install/upgrade the chart.
$ kubectl create secret generic realm-secret --namespace=<chart_namespace> --from-file=path/to/realm.json
add a comment |
The reason is you are referencing a secret named realm-secret
in extraVolumes
, but that secret with name realm-secret
is created neither by the helm chart (named stable/keycloak
) nor by you manually.
You can easily find that chart in https://github.com/helm/charts/tree/master/stable/keycloak.
Solution:
In values.yaml, the field extraVolume
and extraVolumeMount
is kept to provide an extra volume and extra volumeMount by user if they need. They will be used in keycloak pod. So if you need to provide extraVolumes
that will mount a secret, then you have to create that secret all by yourself. So, create secret realm-secret
in the same namespace in which you install/upgrade your chart. And only then install/upgrade the chart.
$ kubectl create secret generic realm-secret --namespace=<chart_namespace> --from-file=path/to/realm.json
The reason is you are referencing a secret named realm-secret
in extraVolumes
, but that secret with name realm-secret
is created neither by the helm chart (named stable/keycloak
) nor by you manually.
You can easily find that chart in https://github.com/helm/charts/tree/master/stable/keycloak.
Solution:
In values.yaml, the field extraVolume
and extraVolumeMount
is kept to provide an extra volume and extra volumeMount by user if they need. They will be used in keycloak pod. So if you need to provide extraVolumes
that will mount a secret, then you have to create that secret all by yourself. So, create secret realm-secret
in the same namespace in which you install/upgrade your chart. And only then install/upgrade the chart.
$ kubectl create secret generic realm-secret --namespace=<chart_namespace> --from-file=path/to/realm.json
edited Jan 22 at 5:19
answered Nov 23 '18 at 17:32
Shudipta SharmaShudipta Sharma
1,177413
1,177413
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.
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%2f53450402%2fmountvolume-setup-failed-for-volume-realm-secret-secrets-realm-secret-not%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