I published my first JetBrains plugin, K8s ConfigMap Navigator. It does one job: it connects a key in a Kubernetes ConfigMap to the lines of application code that read that key, and it lets you go back the other way too.
This post covers the problem it solves, what it supports, and how the matching works under the hood.
The problem: a ConfigMap key and its reader live far apart
A ConfigMap is a Kubernetes object that holds plain configuration values for your app. A typical one looks like this:
apiVersion : v1 kind : ConfigMap metadata : name : orders-config namespace : prod data : MY_APP_CONNECT_TIMEOUT : "3000" MY_APP_BASE_URL : "https://api.example.com"
Enter fullscreen mode
Exit fullscreen mode
Kubernetes injects these values into the container as environment variables. Your application then reads them somewhere in the code.
Now imagine you need to change MY_APP_CONNECT_TIMEOUT , or you want to know if it is safe to delete it. You have to find who reads it.…