Webhook configuration using wrong namespace

[slushysnowman]

Bug description

A clear and concise description of what the bug is.

How to reproduce

Steps to reproduce the behavior:

1. Using Helm chart 0.1.2, deploy to a namespace other than capsule-system
2. Create a tenant, specifying allowed storage classes
3. Create a namespace in the tenant
4. Create a persistent volume claim in the tenant namespace

Error from server (InternalError): error when creating "test-deployment.yaml": Internal error occurred: failed calling webhook "pvc.capsule.clastix.io": Post "https://capsule-webhook-service.capsule-system.svc:443/persistentvolumeclaims?timeout=30s": service "capsule-webhook-service" not found

The namespace for the service is incorrect - it seems to be hardcoded, rather than referencing {{ .Release.Namespace }}

Expected behavior

Webhook configuration should reference the correct namespace. It seems to be fixed in the helm chart files here, but the latest tagged version of the helm chart doesn't include this fix yet.

Is there an ETA for when a new version of the helm chart with this fix will be released, or how we can get around this until then?

Additional context

• Capsule version: 0.1.0
• Helm Chart version: 0.1.2
• Kubernetes version: v1.21.2-eks-0389ca

[prometherion]

Thanks for reporting this: the bug was tracked with #448 and the related PR merged.

However, we missed releasing a new Helm version. Once #456 is merged I'll tag a new helm release and expected to get it published on our repo.

[prometherion]

@slushysnowman we just released the v0.1.3 Chart version.

Please, give it a try and if anything still doesn't work, don't hesitate to open back this issue!

[slushysnowman]

@prometherion - working great, thanks for picking this up so quickly!