I’ve got a working drone installation. I am now trying to button up the kubernetes secrets add-on. New jobs fail to create the environment variables I’ve defined in my yaml. I was unable to obtain error logs from kubernetes-secrets, until I turned on debug logging (DEBUG=true). The error is time="2018-11-28T15:22:52Z" level=debug msg="secrets: invalid signature in http.Request". I’ve checked the agent and secrets SECRET_KEY, they match. Is there anything else I might’ve missed?
Doh! Shoulda caught that, thanks for the extra set of eyes. That resolved my initial issue.
Now I’m told that the requested key does not exist. I have installed drone into its own namespace, called drone. I set the env var in kubernetes secrets to KUBERNETES_NAMESPACE=drone. The kube config I install defines three clusters (dev, prod, staging), but the default context is set to the cluster drone is running on (dev). The secret is named drone-secrets and it is in the drone namespace.
Tcpdump shows me there’s a mismatch, between what the agent sends and what the plugin expects. It seems the drone/drone-kubernetes-secrets expects a request with secret#key and the agent sends each in their own field. I managed to fix this issue locally, but I lack a familiarity with the dep command to completely fix the issue and open a PR (I ran dep ensure -update github.com/drone/drone-go but it still updated a bunch of other stuff).