Hussein Galal

This will require a change to the helm chart spec so that it can support adding more flags to helm install and helm repo commands

@jawabuu currently passing timeout to the helmchart installation is not supported in the Helmchart spec https://github.com/k3s-io/helm-controller/blob/master/pkg/apis/helm.cattle.io/v1/types.go#L20-L29, and I dont think there is a plan for adding it to the spec...

@jawabuu we only do helm install --upgrade when the chart is already deployed https://github.com/k3s-io/klipper-helm/blob/master/entry#L39, so if the chart is not really installed and timedout, it will attempt to re-install it...

It can be a good idea to add extra-args to helm command in the chart spec cc @brandond

#10 Added Docker support to run chesshub.io with mongodb and elasticsearch.

@LarsBingBong Thanks for opening the issue, from the logs there seems to be a misconfigured kubelet certificate on the api node, according to the code the node 192.168.23.70 (The API...

@LarsBingBong Thanks for providing the information, so as for your question: ``` @galal-hussein how can I control, on a cluster using the ccm how it's effecting the --node-external-ip flag? As...

@LarsBingBong yes for sure, I meant for this configuration --node-ip=x.x.x.70 is to be configured on all cp nodes

I think k3s is the one that is panicking and losing leader election, our etcd fork has a patch to prevent panicking if removed from the cluster, I think cluster-init...

either way, is un-tombstoning would be the right idea even, so we will have to document that if you delete the first node, you need to remove the etcd data...