Please provide more details such as your Drone version, your server and runner configuration, and steps that can be used to reproduce. There are three ways that a Kubernetes pipeline can execute as a Docker pipeline:
you are using drone exec which does not integrate with Kubernetes
you are running an older version of Drone which does not support different types of pipelines
you installed Drone in single-machine mode with runners (agents) disabled. this is a legacy configuration and should not be used.
when you set DRONE_KUBERNETES_ENABLED=true you are enabling an experimental kubernetes integration that was deprecated some time ago. This deprecated integration does not recognize the type attribute. Instead you should install the kubernetes runner: https://docs.drone.io/runner/kubernetes/overview/
Any timeline for addressing this issue in kubernetis runner:
The pipeline status is not correctly passed to containers, impacting plugins that rely on this value. This primarily impacts notification plugins, such as Slack, which will always report the pipeline status as success.
We should update the docs to clarify … the updated status is passed to the container, however, unlike the docker runner it is passed by file instead of environment variable. Existing plugins need to be patched to read this file. You can look at this patch to the Slack plugin where we source the environment file to get the updated status.
If there is a specific plugin that you are using from the plugins/* organization let us know, and we can make sure it is reading this file.
Yes, this flag enables an experimental feature that was deprecated and replaced by the kubernetes runner.
I installed drone via helm chart
The chart in helm stable is unofficial (we are not involved) and seems out of date and out of sync with the project and how it has evolved. For this reason we began publishing our own charts. See Official Helm Chart
I was trying to use the chart and found that the DRONE_RPC_SECRET must be specified as a string, not supporting the secretKeyRef.
I would like to specify the secrets using the standard secret management facilities: