| 1 Dec 2023 |
 Yann Diorcet | talosctl --talosconfig talosconfig get members
NODE NAMESPACE TYPE ID VERSION HOSTNAME MACHINE TYPE OS ADDRESSES
192.168.42.65 cluster Member talos-control-plane-0 13 talos-control-plane-0.dc3-a.pub1.infomaniak.cloud controlplane Talos (v1.5.5) ["192.168.42.65"]
192.168.42.65 cluster Member talos-control-plane-1 10 talos-control-plane-1.dc3-a.pub1.infomaniak.cloud controlplane Talos (v1.5.5) ["192.168.42.164"]
192.168.42.65 cluster Member talos-control-plane-2 12 talos-control-plane-2.dc3-a.pub1.infomaniak.cloud controlplane Talos (v1.5.5) ["192.168.42.253"]
192.168.42.65 cluster Member talos-worker-0 9 talos-worker-0.dc3-a.pub1.infomaniak.cloud worker Talos (v1.5.5) ["192.168.43.75"]
192.168.42.164 cluster Member talos-control-plane-0 9 talos-control-plane-0.dc3-a.pub1.infomaniak.cloud controlplane Talos (v1.5.5) ["192.168.42.65"]
192.168.42.164 cluster Member talos-control-plane-1 9 talos-control-plane-1.dc3-a.pub1.infomaniak.cloud controlplane Talos (v1.5.5) ["192.168.42.164"]
192.168.42.164 cluster Member talos-control-plane-2 9 talos-control-plane-2.dc3-a.pub1.infomaniak.cloud controlplane Talos (v1.5.5) ["192.168.42.253"]
192.168.42.164 cluster Member talos-worker-0 7 talos-worker-0.dc3-a.pub1.infomaniak.cloud worker Talos (v1.5.5) ["192.168.43.75"]
192.168.42.253 cluster Member talos-control-plane-0 13 talos-control-plane-0.dc3-a.pub1.infomaniak.cloud controlplane Talos (v1.5.5) ["192.168.42.65"]
192.168.42.253 cluster Member talos-control-plane-1 12 talos-control-plane-1.dc3-a.pub1.infomaniak.cloud controlplane Talos (v1.5.5) ["192.168.42.164"]
192.168.42.253 cluster Member talos-control-plane-2 15 talos-control-plane-2.dc3-a.pub1.infomaniak.cloud controlplane Talos (v1.5.5) ["192.168.42.253"]
192.168.42.253 cluster Member talos-worker-0 11 talos-worker-0.dc3-a.pub1.infomaniak.cloud worker Talos (v1.5.5) ["192.168.43.75"]
192.168.43.75 cluster Member talos-control-plane-0 6 talos-control-plane-0.dc3-a.pub1.infomaniak.cloud controlplane Talos (v1.5.5) ["192.168.42.65"]
192.168.43.75 cluster Member talos-control-plane-1 6 talos-control-plane-1.dc3-a.pub1.infomaniak.cloud controlplane Talos (v1.5.5) ["192.168.42.164"]
192.168.43.75 cluster Member talos-control-plane-2 6 talos-control-plane-2.dc3-a.pub1.infomaniak.cloud controlplane Talos (v1.5.5) ["192.168.42.253"]
192.168.43.75 cluster Member talos-worker-0 8 talos-worker-0.dc3-a.pub1.infomaniak.cloud worker Talos (v1.5.5) ["192.168.43.75"] | 15:51:18 |
| Yann Diorcet | Looks weird, no? | 15:51:28 |
 andrey | I'm not sure what you're trying to show | 16:38:53 |
| Yann Diorcet | Sorry for the noise. I may have find the issue, thanks to https://slack-archive.rancher.com/t/8996533/trying-to-add-nodes-with-rke-cli-the-node-appears-on-the-clu | 16:51:23 |
| Yann Diorcet | Adding cloud-provider: external to kubelet extra args seems to improve largly | 16:51:46 |
 Dave | With my terraform provisioned cluster every time I plan it results in kubeconfig output changes. Is that expected behavior? | 17:55:26 |
| andrey | kubeconfig is generated via Talos API | 19:07:08 |
| andrey | so yes, it's not stored, always generated on the fly | 19:07:19 |
| Dave | kk ty, I'll remove that output then | 19:09:33 |
|  Peter Bücker changed their profile picture. | 19:12:13 |
| Peter Bücker | It would be interesting to see if anybody ever tried running something like Sysdig. Could also be something for #talos:matrix.org , happy to be redirected 🙂 | 19:12:54 |
 Tim Jones | Any reason a DaemonSet running the agent would be insufficient?? | 19:16:05 |
| Peter Bücker | That was one of my ideas indeed!
I suppose I was more concerned about the agent's capability to work in the restricted/minimal environment that Talos Linux provides. | 19:17:28 |
| Tim Jones | Indeed we often run into workloads like this that assume a lot of the host system. Like trying to read /etc/passwd which simply doesn't exist in Talos.
If the provider is willing to give you a decent trial period, or even work with us directly to improve compatability, we would do our best to help. | 19:21:27 |
| Dave | on the topic of terraform is there a way avoid applying configs to all nodes in a rolling manner if it will cause downtime on the nodes? I just added a plugin to containerd via file and all nodes went down at the same time so my ceph osds etc were all down simultaneously | 19:23:40 |
| Peter Bücker | That's great to know Tim Jones 🙏 I'll keep chipping away at this then and if any help is needed, will get in touch with the vendor to see what they can do to improve. Thanks a lot! | 19:24:35 |
 Justin Garrison | IIRC the latest sysdig agent mostly used eBPF and shouldn’t rely as much on volume mounts. Talia and bottlerocket should have very similar results because bottlerocket runs an isolated container runtime for workloads | 19:31:46 |
| Peter Bücker | Thanks Justin Garrison that's great to know! Sounds like this might actually be in the realm of possible. If I make the necessary progress with this and it turns out to work, I'd love to poke Sysdig so they include Talos in the list of supported operating systems 🚀 | 19:34:20 |
 Adam | At what point does the qemu-guest-agent start in Talos 1.6? Should I be expecting it to return an IP address in proxmox once it fully boots into maintenance mode? | 20:41:01 |
 Ian | Redacted or Malformed Event | 20:46:12 |
| Adam | Does this also apply to the qemu-guest-agent as well — https://github.com/siderolabs/talos/issues/7083 ? | 20:50:21 |
| Ian | I am trying to get Cillium working in Talos Linux without kube-proxy, and am following this guide https://www.talos.dev/v1.5/kubernetes-guides/network/deploying-cilium/. I seem to be getting errors when creating on of the containers, does someone know why this is?
Versions:
Server:
NODE: 10.0.0.142
Tag: v1.5.5
SHA: ad7361c7
Built:
Go version: go1.20.11
OS/Arch: linux/amd64
Enabled: RBAC
Pod Error:
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system cilium-operator-b4dfbf784-kdtm4 1/1 Running 0 2m30s
kube-system cilium-operator-b4dfbf784-np9zs 0/1 Pending 0 2m30s
kube-system cilium-t5jb9 0/1 Init:CrashLoopBackOff 4 (54s ago) 2m30s
Detailed Error of t5jb9:
Error: failed to create containerd task: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: unable to apply caps: operation not permitted: unknown
The error seems to be the same as the one documented here: https://www.talos.dev/v1.5/learn-more/process-capabilities/ | 20:56:57 |
|  Travis Scotto joined the room. | 21:09:31 |
| Travis Scotto set a profile picture. | 21:09:33 |
| Justin Garrison | If you verify it works I know someone at sysdig who can probably help | 21:43:52 |
|  Joseph Petrides joined the room. | 22:01:40 |
| Joseph Petrides set a profile picture. | 22:01:41 |
| andrey | Probably the command is wrong? You try to create a container with caps not allowed by Talos | 22:03:41 |
|  Chris Hunt joined the room. | 22:30:54 |
| Chris Hunt changed their display name from _slack_taloscommunity_U068AP01NJW to Chris Hunt. | 22:30:55 |
