k0sctl init doesn't come to a working cluster about k0sctl HOT 5 CLOSED

Well, test it! Because without the –k0s (and therefore empty config) the cluster is not working proper. Kind Regards, [signature_345534028]<https://www.mirantis.com/> Robert Hartevelt Presales Northern Europe [signature_4209553835] ***@***.******@***.***> [signature_2249549919] +31 (0) 628 688344<tel:%20+1%20(786)%20325%2025%2096> From: Kimmo Lehto ***@***.***> Date: Thursday, January 18, 2024 at 2:03 PM To: k0sproject/k0sctl ***@***.***> Cc: Robert Hartevelt ***@***.***>, Author ***@***.***> Subject: Re: [k0sproject/k0sctl] k0sctl init doesn't come to a working cluster (Issue #640) For reference, here is what the k0s section looks like with --k0s: k0s: config: apiVersion: k0s.k0sproject.io/v1beta1 kind: Cluster metadata: name: k0s spec: api: k0sApiPort: 9443 port: 6443 installConfig: users: etcdUser: etcd kineUser: kube-apiserver konnectivityUser: konnectivity-server kubeAPIserverUser: kube-apiserver kubeSchedulerUser: kube-scheduler konnectivity: adminPort: 8133 agentPort: 8132 network: kubeProxy: disabled: false mode: iptables kuberouter: autoMTU: true mtu: 0 peerRouterASNs: "" peerRouterIPs: "" podCIDR: 10.244.0.0/16 provider: kuberouter serviceCIDR: 10.96.0.0/12 podSecurityPolicy: defaultPolicy: 00-k0s-privileged storage: type: etcd telemetry: enabled: true When k0s.config is not set, k0sctl will use the output of k0s config create to create a default config. This would then mean that the default config of k0s does not work, which I don't think is likely. — Reply to this email directly, view it on GitHub<#640 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ATRYPMLYE5GPVVWAIR2LSTTYPEMSLAVCNFSM6AAAAABCADRO3SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJYGQ2DCNRZGQ>. You are receiving this because you authored the thread.Message ID: ***@***.***>

Yes, you are right. But that doesn’t solve the issue at all, is it? Kind Regards, [signature_611900982]<https://www.mirantis.com/> Robert Hartevelt Presales Northern Europe [signature_341233520] ***@***.******@***.***> [signature_2672663628] +31 (0) 628 688344<tel:%20+1%20(786)%20325%2025%2096> From: Kimmo Lehto ***@***.***> Date: Thursday, January 18, 2024 at 1:25 PM To: k0sproject/k0sctl ***@***.***> Cc: Robert Hartevelt ***@***.***>, Author ***@***.***> Subject: Re: [k0sproject/k0sctl] k0sctl init doesn't come to a working cluster (Issue #640) "error: pod, type/name or --filename must be specified" This seems to be a syntax error in the command. The correct syntax should be kubectl exec -it mydep-66c55fb688-cbkg -- bash, you used kubectl exec -it -- bash mydep-66c55fb688-cbkgl. — Reply to this email directly, view it on GitHub<#640 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ATRYPMNQZIGHXANQULETE4LYPEIFHAVCNFSM6AAAAABCADRO3SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJYGM4DIOJRGU>. You are receiving this because you authored the thread.Message ID: ***@***.***>