Unable to inject proxy into my pod

Consul
1

Hello I’m trying to connect my pod to a consul cluster. I am running in minikube. I tried Get Started on Kubernetes | Consul - HashiCorp Learn and it worked fine. But now when Im trying todo basically the same thing with my own stuff my pod wont register with consul, probably because no sidercar proxy is injected into the pod.

Here is my values.yml

image
image504×913 50.7 KB

My chart has only a single dependency
image

My deployment and service

image
image865×1304 125 KB

After starting this, consul and my edge-pod starts up but I cannot see my edge-pod registered in consul, I only see:

image
image908×261 11.1 KB

My edge pod should also be there (probably messed something up).

These are all my pods running:

image
image747×177 13 KB

Output from injector pod, if that helps

image
image1075×121 22.3 KB

Would love some pointers

2

The reason I have commented-out ServiceDefaults

image
image2412×152 54.1 KB

3

Hi @josvegit ! Thanks for filing this issue!
It’s a little bit hard to read in the screenshots but I’m wondering if you’ve possibly put the connect annotation on your Deployment instead of your Pods?
Can you confirm that you’ve either set connectInject.default: true or set the annotation on your Pods?
Thanks!

1 Like
4

Hi thanks for helping!

I’m setting this in my values.yaml (I made a mistake before and posted my deployment and service twice).
image

When I describe my pod, it seems to have the correct annotations:
image

Maybe this image is better:

image
image809×828 141 KB

I’m quite sure its not the deployment annotations, I read that was a common issue.

I’m not even sure I should need the annotations with those configs in my values.yml but perhaps I have misunderstood.

5

I think I have found the issue not sure what the solution is though. If I edit my deployment (just to force an upgrade) and after that run a helm upgrade, the pod gets registered. So it seems that my pod starts before consul is ready and then there is no sidecar container injected into it ?

6

I guess I could also have initcontainers that simply waits for consul to become live, not sure if this is the best idea ?

7

Ahh gotcha. Yes sorry this is a known issue (Modify failurePolicy for MutatingWebhookConfiguration to fail pods when injector not running · Issue #962 · hashicorp/consul-helm · GitHub) that we’d like to fix ASAP. Please subscribe to that issue.

1 Like
8

ah ok, is this related Cannot install consul with ServiceDefaults on minikube - #2 by josvegit ?

9

It is, if consul is installed in the cluster I don’t get that error

10

Yes it’s a similar issue but that one won’t be “fixed”. We’ll always require the CRDs to be installed and the controller running.