Brian Lachniet

I don't think that there was anything else I needed to do in order to tie the stateful set to the PVs. The [persistent volumne claims](https://github.com/kelseyhightower/consul-on-kubernetes/blob/ea5115f5773a037a3f0c00e715c4b12f236be61f/statefulsets/consul.yaml#L100) in the stateful set...

I was having the same issue with the v0.9.0 Consul container. I updated the paths used in my pull request to update to v0.9.0, #15, which resolved the issue.

Before now, I had never heard of vcpkg. It sounds a bit like a Maven Central, npm, or NuGet, but for C++ projects. @grdowns, is that a fair comparison? If...

Any suggestions on the upgrade process here? Should we deploy `kube-flannel-ds` (v0.13.0) alongside the already running `kube-flannel-ds-amd64` (v0.12.0), and then delete `kube-flannel-ds-amd64`? Is there a better approach?

FWIW, the `checkOnSave` configuration you showed above is working for me. Here's my config. ```lua local rt = require("rust-tools") rt.setup({ server = { on_attach = function(_, bufnr) -- Hover actions...