-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create cluster is not working with the latest k8s version #197
Comments
The version which failed is |
Can you give me the specific command you typed in to start the installation? |
I pulled the last version of hetzner-kube from master, changed diff --git a/pkg/clustermanager/provision_node.go b/pkg/clustermanager/provision_node.go
index 2cd4399..1fa6a58 100644
--- a/pkg/clustermanager/provision_node.go
+++ b/pkg/clustermanager/provision_node.go
@@ -10,7 +10,7 @@ import (
const maxErrors = 3
// K8sVersion is the version that will be used to install kubernetes
-var K8sVersion = flag.String("k8s-version", "1.9.6-00",
+var K8sVersion = flag.String("k8s-version", "1.12*",
"The version of the k8s debian packages that will be used during provisioning")
// NodeProvisioner provisions all basic packages to install docker, kubernetes and wireguard and created cluster with |
@Zebradil configuration files of k8 1.9 and 1.12 are incompatible, that's not enough just to change the version number. But you could install 1.9 and gradually upgrade to 1.12. https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm-upgrade/ Config changes/deprecations: |
Thanks! I'll try it. |
So what should we do here now? I'm getting the same: stderr:Process exited with status 1 |
@gridworkz there are a PoC that run the new cluster on this PR #208 but need some more work, we'll update the project state when the new cluster config will work as expected ;) |
I think it is somehow related to #162.
I tried to switch to the latest available k8s version, but the cluster creation process failed with the following info:
I tried to figure out what's wrong but got stuck. It seems like
--debug
flag changes nothing.I checked created nodes and didn't even find
/root/master-config.yaml
file which (if I'm not mistaken) should be already there beforekubeadm token create --print-join-command
command.I understand, that there is only one supported version at the moment, but maybe someone can direct me where to dig and I can resolve the issue.
The text was updated successfully, but these errors were encountered: