Following blog post, but namerd complains about certificates

I’m following this blog post to set up a basic infrastructure on Azure AKS, but the namerd pods fail to start, complaining that the secret certificates does not exist. That’s not so strange, because I haven’t created it, but I’m having a difficult time figuring out what I should put in it.

A couple of posts earlier there’s some talk about setting up TLS communication between services, but that’s not what I’m after. And I’m too new to the entire k8s sphere to understand from the config map exactly what type of certificates I need, and where to put them…

Basically, any advice on how to get past step 1 of that blog post on a clean Kubernetes cluster would be greatly appreciated.

Hey @tlycken – thanks for bring this to our attention! That’s… not good. Looks like the namerd.yml config was inadvertently broken as part of:

I’ll fix the config to be apply-able without any additional configuration. In the meantime, before applying namerd.yml, you can apply the certificates.yml file from the same directory. I think this should work to bring namerd up successfully:

kubectl apply -f https://raw.githubusercontent.com/linkerd/linkerd-examples/master/k8s-daemonset/k8s/certificates.yml
kubectl apply -f https://raw.githubusercontent.com/linkerd/linkerd-examples/master/k8s-daemonset/k8s/namerd.yml

Let us know how it goes, thanks!

The fix for this issue is here:

Thanks again for bringing it to our attention!

Thanks a lot!

I had already made local copies of the files from the blog post, so applying the patches you linked to was really simple, and after that it seems to work as expected :slight_smile: