aws-sigv4-proxy-admission-controller
aws-sigv4-proxy-admission-controller copied to clipboard
aws-observability
This project creates a mutation admission controller that injects AWS SIGv4 proxy as a sidecar.
``` Internal error occurred: failed calling webhook “sigv4-aws-sigv4-proxy-admission-controller.k8s.aws”: failed to call webhook: Post “[https://sigv4-aws-sigv4-proxy-admission-controller-webhook-service.kube-system.svc:443/mutate?timeout=10s](https://sigv4-aws-sigv4-proxy-admission-controller-webhook-service.kube-system.svc/mutate?timeout=10s)”: no endpoints available for service “sigv4-aws-sigv4-proxy-admission-controller-webhook-service” ``` How to temporarily resolve if your cluster experiences this...
We are facing an issue where main container stops and aws-sigv4-proxy side car container is still hanging and not exited. Is there a process to handle graceful termination of side...
Hi, We faces the issue HPA stopped working because it can't read CPU utilization after injecting aws-sigv4-proxy as a sidecar by this admission controller. I have investigated the issue, then...
Metadata
Owner
Metadata
This project creates a mutation admission controller that injects AWS SIGv4 proxy as a sidecar.