Closed anoop7181 closed 3 years ago
Hi @anoop7181
Thanks for your interest in the operator. The error/stacktrace you are getting, is not an error, we purposely added an extra log statement in order to debug a possible bug. However, in Java/Kotlin you'll have to use a fake exception in order to log a stacktrace (see: https://github.com/openanalytics/shinyproxy-operator/blob/develop/src/main/kotlin/eu/openanalytics/shinyproxyoperator/controller/ShinyProxyController.kt#L207 (the actual comment is wrong..)). I understand this is confusing, so I'll adapt the statement before our first release.
Regarding your main issue: the problem is (probably) in your patch. What your patch currently is doing is "at the /spec/volumes
path, add an array with a single value name: "demoplanning", ...
". In other words, you are replacing the existing volumes array with a new array, which only contains the value you provided in your patch. Therefore, the configmap created and mounted by the Operator is removed from the list. This is the exact reason why you now see that ShinyProxy is using the default configuration. You can adapt your patch, so that it appends your element to the list of volumes:
kubernetesPodTemplateSpecPatches: |
- op: add
path: /spec/volumes/-
value:
name: "demoplanning"
azureFile:
secretName: demo-azure-secret
shareName: demoplanningdata
readOnly: false
- op: add
path: /spec/containers/0/volumeMounts/-
value:
mountPath: "/mnt/azure"
name: "demoplanning"
I hope this helps!
Thank you so much @LEDfan . I copied the earlier syntax from the documentation below https://shinyproxy.io/documentation/configuration/#kubernetes
Now it works and I see the volumes being mounted. Currently these volumes are mounted on the proxy container. Can you please let me know how can I get it mounted on to shiny app container.
Got it working but adding respective Kubernetes-pod-patches template into the container specs. The syntax is different from KubernetesPodTemplateSpecPatches.
For container spec pod template patch , used below syntax `- id: 01_hello_manifests_espression container-specs:
@LEDfan Thank you for the Operator. It has helped me ease the deployment on AKS.
Great that you found the correct configuration options! Good to know that the operator works on AKS as well and that it is useful to your.
I'm closing this issue now, feel free to open a new one if you encounter any issue!
I am trying to setup volume mounts using Kubernetes patch specifications. Unfortunately after applying it ,I noticed errors in operator pod logs. I created PV and PVC separately and the setup of Persistent volume and claim looks fine. I tested out this with another pod.
When I refer the same as below , it fails.
I do see during shinyproxy pod creation it detecting the volume correctly but below error throws up and shinyproxy is deployed as vanilla installation. Funnily I can access shinyproxy (vanilla installation) but none of customisations like authentication and new containers get applied.