crmendes

> For posterity's sake, I commented in #361 that `no-hooks` should be a flag-only option. I'm trying to use with helmfile command. If I set the HELM_DIFF_USE_UPGRADE_DRY_RUN=true, it resolves the...

yes, makes sense, definitely that is the best way to follow. I've just already tested only the command `helm upgrade --dry-run`, and yes, it shows me all the hooks as...

sorry @mumoshu, the command that is omitting the hooks is the `helm diff upgrade --dry-run` not the `helm upgrade --dry-run`. 

hi @cristichiru , first of all thanks for your concern! 🙂 Forget the python part... no I'm using the kong helm chart, that deploy kong-ingress-controller and using the image `revomatico/docker-kong-oidc:2.6.0-1`....

Just a note, this behavior is occurring both with `session_storage: cookie` and `session_storage: memcache`

On boot I mean on servers creation and yes, if I delete the pod and it started up again the endpoint appears on each server and works. I set all...

After more testing, either clusters creation and clusters failover (delete nodes and boot new ones) those messages appears some time and the kilo does not recover it self, but keeps...

I figured it out that after ~10min the kilo recovers from that timeout: ``` E0226 12:07:01.409656 1 streamwatcher.go:109] Unable to decode an event from the watch stream: read tcp 10.30.1.67:43406->10.43.0.1:443:...

Yes, the steps that I follow up is delete 2 old master nodes and boot 2 new ones, maintaining 2 or 3 worker nodes with kilo running on them. Only...

annotations on the node in region "cloud" (first) and a another node (second), on another NAT'ed network:  `wg` and `ip a` output on both nodes (left: cloud; right: NAT'ed):...