k3s-server /var/vcap/store/kubeconfig.yml generation must be synced with k3s.yaml file generation

[poblin-orange]

The k3s process generates a k3s.yaml kubeconfig file. This file is targeted to 127.0.0.1

The k3s bosh release generates a kubeconfig.yml, replacing 127.0.0.1 ip with

• spec.ip
• vip ip if an external vip must be used to access the cluster

A first start (empty k3s server /var/vcap/store), the bosh post-start might occur BEFORE k3s process has generated the k3s.yaml, resulting in a silent failure and an empty kubeconfig.yml