Jesse Haka

@schonfeld I have added that permanently to all kubernetes nodes. It solves that and now people can run their clusters.

@schonfeld well when node fails and it goes to infinite loop.. it sounds that you have not added it permanently. If you restart one node and write `sysctl vm.max_map_count`, you...

I am thinking that is it so simple that if blob digest called X is deleted, then just scan layer folder is there file called X and if yes delete...

but that is how currently garbage collector is working right? It is first scanning all manifest blobs, and if there is blobs which are not referenced in manifests those are...

this is still the issue with 1.0.1.

this has maybe something to do with infrastructure annotations in gateway. I am trying to reproduce this now with latest main

@arkodg hmm, does it make it impossible to use groups as authorization if that is base64 encoded? Does envoy have then feature to decode base64 first to make these groups...

@kayrus spec.LoadbalancerIP is deprecated, see https://github.com/kubernetes/cloud-provider-gcp/issues/371 https://github.com/kubernetes/kubernetes/pull/107235 So I think the annotation for openstack could be something like `loadbalancer.openstack.org/floating-ip` all of these https://github.com/search?q=repo%3Akubernetes%2Fcloud-provider-openstack%20loadbalancerip&type=code should be removed and migrated to new...

@jeffyjf well if you look these annotations https://github.com/kubernetes/cloud-provider-openstack/blob/eeba48501bf743e3992093bd806a513ad103a347/pkg/openstack/loadbalancer.go#L69-L103 there are not many service.beta.kubernetes.io annotations. Which means that new ones will be using loadbalancer.openstack.org

it does not mean always that. When you create new loadbalancer and want to provision new floating ip, you do not need to define `loadbalancer.openstack.org/floating-ip` annotation. Only if someone wants...