You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Logs
If applicable, add logs to help explain your problem.
# v1.5.0 installed
❯ helm list
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
akv2k8s akv2k8s 25 2024-01-05 14:09:01.384911 +0000 UTC deployed akv2k8s-2.5.0 1.5.0
# Example app running
❯ kubectl get pods --namespace xm-test -l app=akvs-secret-app
NAME READY STATUS RESTARTS AGE
akvs-secret-app-79b489bc7f-plcrt 1/1 Running 0 72m
# Upgrade to v1.6.0
❯ helm upgrade akv2k8s --install --create-namespace --namespace akv2k8s --repo http://charts.spvapi.no --version 2.6.0 akv2k8s --set "controller.enabled=false" --set "env_injector.authService=false"
Release "akv2k8s" has been upgraded. Happy Helming!# Verify upgraded
❯ helm list
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
akv2k8s akv2k8s 26 2024-01-05 15:30:47.644243 +0000 UTC deployed akv2k8s-2.6.0 1.6.
# Restart example deployment
❯ kubectl rollout --namespace xm-test restart deployment akvs-secret-app
deployment.apps/akvs-secret-app restarted
# Pod isn't re-created
❯ kubectl get pods --namespace xm-test -l app=akvs-secret-app
NAME READY STATUS RESTARTS AGE
akvs-secret-app-79b489bc7f-plcrt 1/1 Running 0 80m
# Events show EOF from POST to https://akv2k8s-envinjector.akv2k8s.svc:443/pods?timeout=10s
❯ kubectl get events --namespace xm-test
LAST SEEN TYPE REASON OBJECT MESSAGE
12s Warning FailedCreate replicaset/akvs-secret-app-8597ff46d Error creating: Internal error occurred: failed calling webhook "pods.env-injector.admission.spv.no": failed to call webhook: Post "https://akv2k8s-envinjector.akv2k8s.svc:443/pods?timeout=10s": EOF
33s Normal ScalingReplicaSet deployment/akvs-secret-app Scaled up replica set akvs-secret-app-8597ff46d to 1
# Check logs (see below)
❯ kubectl logs akv2k8s-envinjector-8889bcb89-d6n28
# Rollback to previous version
❯ helm rollback akv2k8s 25
Rollback was a success! Happy Helming!# Confirmed downgraded
❯ helm list
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
akv2k8s akv2k8s 27 2024-01-05 15:35:35.912045 +0000 UTC deployed akv2k8s-2.5.0 1.5.0
# Pod is now restarting as expected, secrets injected
❯ kubectl get pods --namespace xm-test -l app=akvs-secret-app
NAME READY STATUS RESTARTS AGE
akvs-secret-app-79b489bc7f-plcrt 1/1 Terminating 0 85m
akvs-secret-app-8597ff46d-jd5s7 1/1 Running 0 12s
Looking to upgrade ASAP to 1.6.0 or higher as 1.5.0 is currently mutating security contexts as per #591 and causing issues. Currently on 1.5.0 to fix #547 for Certificate Injection.
The text was updated successfully, but these errors were encountered:
Not sure if this relates to changes in #631 given the error trace looks like it is running registry functions when this occurs... or something with the net/http package given GHSA-4374-p667-p6c8 required it was bumped in #621
Note: Make sure to check out known issues (https://akv2k8s.io/troubleshooting/known-issues/) before submitting
Components and versions
Select which component(s) the bug relates to with [X].
[ ] Controller, version:
1.6.0
(docker image tag)[x] Env-Injector (webhook), version:
1.6.0
(docker image tag)[ ] Other
Describe the bug
Replicaset returns event
Error creating: Internal error occurred: failed calling webhook "pods.env-injector.admission.spv.no": failed to call webhook: Post "https://akv2k8s-envinjector.akv2k8s.svc:443/pods?timeout=10s": EOF
, env injector logs showsinvalid memory address or nil pointer dereference
error.To Reproduce
Steps to reproduce the behavior:
--set "controller.enabled=false"
and `--set "env_injector.authService=false")Expected behavior
Secret injection to work without error.
Logs
If applicable, add logs to help explain your problem.
Logs produced by
akv2k8s-envinjector
:Additional context
Looking to upgrade ASAP to 1.6.0 or higher as 1.5.0 is currently mutating security contexts as per #591 and causing issues. Currently on 1.5.0 to fix #547 for Certificate Injection.
The text was updated successfully, but these errors were encountered: