I am following this out-of-process-adapter walk through to learn how to write an out-of-process mixer adapter.
The way it makes the mixer aware of the new adapter is by passing in the --configStoreURL in the mixs command line:
$GOPATH/out/linux_amd64/release/mixs server --configStoreURL=fs://$(pwd)/mixer/adapter/mygrpcadapter/testdata
The example works well with the standalone mixer server, but how do you do that (inject the adapter resource config into Mixer’s configuration store) in the context of a kubernetes cluster?
In the walk-through guide, it points to a Prometheus adapter for example:
You may look at Prometheus Out of process adapter for a working example.
Looking at the code, I can see the mixer adapter will be deployed to the kubernetes cluster as a service:
But it’s not clear to me how the mixer is made aware of this adapter. Can someone please help me connect the missing dots as our use case needs to happen in the context of kubernetes cluster.
It will be great if there is another walk through with the Promethues example outlining the steps of how to deploy a mixer adapter and then plug it in the mixer in the context of a kubernetes cluster.