DEiselt

The `FloatingIPPortAlreadyAssociated` error is to be expected from Openstack side as far as i know. I would also consider this a mere symptom of what is happening. By trying to...

After further investigation, this issue seems to resolve around the `testcluster_name`. ## Reproduction: I was able to reproduce it by using two separate application credentials and environment files, setting a...

Approach to solve this as discussed in container meeting on 17.08.: 1. make sure that $prefix is used in loadbalancer (#495) 2. make sure that the prefix is unique (#506)...

I closed the draft PR for the randomized portion of the `testcluster_name` in favor of #495 and #506 solving this issue. This way we can avoid relying on some random...

> Loadbalancers (kubeapi): k8s-clusterapi-cluster-$CLUSTER_NAME-$CLUSTER_NAME-kubeapi (not good: Lacks $PREFIX) This is related to / blocked by the above part of #495 . Once the load balancer name includes the $PREFIX, this...

@mxmxchere and i discussed further possible improvements. - enable automerge. This can be activate because Renovate has to wait for the Github Branch protection rules anyway. - limit number of...