madnight Github contribution chart
madnight Github Stats
madnight Most Used Languages

Activity

05 Oct 2022

Madnight

started

Started On 05 Oct 2022 at 07:34:05

Madnight

started

Started On 05 Oct 2022 at 07:28:39

Madnight

started

Started On 05 Oct 2022 at 11:22:25
Issue Comment

Madnight

Cilium doesn't work

The cilium operator cannot connect to the ClusterIP 10.233.0.1 443 and CNI setup fails.

error retrieving resource lock kube-system/cilium-operator-resource-lock: Get "https://10.233.0.1:443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/cilium-operator-resource-lock": dial tcp 10.233.0.1:443: connect: connection refused
level=error msg="error retrieving resource lock kube-system/cilium-operator-resource-lock: Get \"https://10.233.0.1:443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/cilium-operator-resource-lock\": dial tcp 10.233.0.1:443: connect: connection refused" subsys=klog
level=warning msg="Network status error received, restarting client connections" error="Get \"https://10.233.0.1:443/healthz\": dial tcp 10.233.0.1:443: connect: connection refused" subsys=k8s
error retrieving resource lock kube-system/cilium-operator-resource-lock: Get "https://10.233.0.1:443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/cilium-operator-resource-lock": dial tcp 10.233.0.1:443: connect: connection refused
level=error msg="error retrieving resource lock kube-system/cilium-operator-resource-lock: Get \"https://10.233.0.1:443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/cilium-operator-resource-lock\": dial tcp 10.233.0.1:443: connect: connection refused" subsys=klog
error retrieving resource lock kube-system/cilium-operator-resource-lock: Get "https://10.233.0.1:443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/cilium-operator-resource-lock": dial tcp 10.233.0.1:443: connect: connection refused
level=error msg="error retrieving resource lock kube-system/cilium-operator-resource-lock: Get \"https://10.233.0.1:443/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/cilium-operator-resource-lock\": dial tcp 10.233.0.1:443: connect: connection refused" subsys=klog``` 
 kubectl get pods -A
NAMESPACE     NAME                                                 READY   STATUS     RESTARTS   AGE
kube-system   cilium-operator-7d9fc9bbb4-x4v8m                     1/1     Running    0          7m4s
kube-system   cilium-pv24r                                         0/1     Init:0/1   0          7m3s
kube-system   cilium-wckmc                                         0/1     Init:0/1   0          7m3s
kube-system   coredns-76b4fb4578-k8lkg                             0/1     Pending    0          6m49s
kube-system   dns-autoscaler-7979fb6659-wgf56                      0/1     Pending    0          6m47s
kube-system   kube-apiserver-local-k8s-cluster-master-1            1/1     Running    1          7m42s
kube-system   kube-controller-manager-local-k8s-cluster-master-1   1/1     Running    0          7m42s
kube-system   kube-proxy-4ds29                                     1/1     Running    0          7m26s
kube-system   kube-proxy-n9bsr                                     1/1     Running    0          7m16s
kube-system   kube-scheduler-local-k8s-cluster-master-1            1/1     Running    0          7m35s
kube-system   nodelocaldns-7cqj7                                   1/1     Running    0          6m47s
kube-system   nodelocaldns-ccvtk                                   1/1     Running    0          6m47s 
hosts:
  - name: localhost
    connection:
      type: local

cluster:
  name: local-k8s-cluster
  network:
    mode: nat
    cidr: 192.168.113.0/24
  nodeTemplate:
    user: k8s
    ssh:
      addToKnownHosts: true
    os:
      distro: ubuntu22
    updateOnBoot: true
  nodes:
    master:
      default:
        ram: 4
        cpu: 2
        mainDiskSize: 32
      instances:
        - id: 1
          ip: 192.168.113.10
    worker:
      default:
        ram: 2
        cpu: 1
        mainDiskSize: 32
      instances:
        - id: 1
          ip: 192.168.113.20
kubernetes:
  version: v1.23.7
  networkPlugin: cilium
  dnsMode: coredns
  kubespray:
    version: v2.19.0 

Forked On 05 Oct 2022 at 11:18:49

Madnight

@MusicDin I can confirm the issue is resolved with Kubespray v2.20.0

Could be that this issue has nothing to do with kubitect and should be report to upstream kubernetes-sigs/kubespray instead.

Commented On 05 Oct 2022 at 11:18:49

Madnight

started

Started On 05 Oct 2022 at 09:48:44

Madnight

started

Started On 05 Oct 2022 at 09:48:32

Madnight

started

Started On 04 Oct 2022 at 02:56:55

Madnight

started

Started On 04 Oct 2022 at 09:13:03

Madnight

started

Started On 03 Oct 2022 at 11:21:13

Madnight

started

Started On 01 Oct 2022 at 06:35:39

Madnight

started

Started On 29 Sep 2022 at 04:28:55

Madnight

started

Started On 29 Sep 2022 at 04:25:16

Madnight

started

Started On 29 Sep 2022 at 04:21:38

Madnight

started

Started On 29 Sep 2022 at 04:19:11

Madnight

started

Started On 28 Sep 2022 at 09:24:28

Madnight

started

Started On 27 Sep 2022 at 07:47:47

Madnight

started

Started On 27 Sep 2022 at 04:08:05

Madnight

started

Started On 25 Sep 2022 at 11:53:18

Madnight

started

Started On 25 Sep 2022 at 09:36:57

Madnight

started

Started On 25 Sep 2022 at 09:36:34

Madnight

How to Guide for Talos

/kind feature

Describe the solution you'd like First and foremost thank you very much for this great work!

I'd like to ask for a Guideline / How to Guide to bootstrap the cluster with Talos as I'm sure many people would appreciate and favor it over standard linux distros like e.g. ubuntu.

Forked On 22 Sep 2022 at 11:19:49

Madnight

@batistein Thanks for your fast response. Talos also provides OS Images https://github.com/siderolabs/talos/releases/download/v1.2.3/metal-amd64.tar.gz wouldn't it be possible to download the OS Image in Hetzner Resuce Mode. Something like

 installImage:
      image: 
        url: https://github.com/siderolabs/talos/releases/download/v1.2.3/metal-amd64.tar.gz
#        path: >-
#          /root/.oldroot/nfs/install/../images/Ubuntu-2004-focal-64-minimal-hwe.tar.gz
      partitions:
        - fileSystem: ext4
          mount: /boot
          size: 1024M
        - fileSystem: ext4
          mount: /
          size: all 

According to the Hetzner Docs https://docs.hetzner.com/robot/dedicated-server/operating-systems/installimage/ allows custom OS images.

After installation the dedicated server could just reboot and the bootstrapping of the server would be done. The rest (creating a k8s cluster) could either configured manually with talosctl or with a talosctl script that runs inside the bootstrap cluster.

Commented On 22 Sep 2022 at 11:19:49

Madnight

How to Guide for Talos

/kind feature

Describe the solution you'd like First and foremost thank you very much for this great work!

I'd like to ask for a Guideline / How to Guide to bootstrap the cluster with Talos as I'm sure many people would appreciate and favor it over standard linux distros like e.g. ubuntu.

Forked On 22 Sep 2022 at 10:02:38

Madnight

@batistein

Could you also write a comment on how to setup Talos on hetzner dedicated machines? I successfully provisioned my bare-metal server HetznerBareMetalHost with the HetznerBareMetalMachineTemplate (currently Ubuntu 20.04) + bootstrap cluster template KubeadmConfigTemplate, but i would like to use Talos instead of Ubuntu + kubeadm. I guess I need something like the cluster-template-hcloud-talos-packer.yaml but for dedicated servers (cluster-template-hetzner-baremetal-talos-control-planes.yaml or so).

Thanks in advance.

Commented On 22 Sep 2022 at 10:02:38

Madnight

started

Started On 22 Sep 2022 at 09:39:24

Madnight

started

Started On 22 Sep 2022 at 09:25:32

Madnight

started

Started On 22 Sep 2022 at 07:36:11

Madnight

started

Started On 21 Sep 2022 at 06:54:53

Madnight

started

Started On 20 Sep 2022 at 01:49:07