andrewrynhard

6 ms·

1.
by andrewrynhard 3y ago
With Kubernetes you can schedule workloads in a number of different ways. Let’s say you insisted on having a shell and package manager. Run your favorite distro’s container as a DaemonSet. With the proper mounts and permissions you can do a
2.
by andrewrynhard 3y ago
In machined (PID1 of Talos).
3.
by andrewrynhard 3y ago
In the case of Talos, Kubernetes can provide the flexibility you want from a more traditional Linux distribution.
4.
by andrewrynhard 4y ago
Have you tried our Slack fir support?
5.
by andrewrynhard 4y ago
This is correct. You could have a privileged pod that mounts up the host and you can do things from there but even then the OS is read only.
6.
by andrewrynhard 4y ago
Oh I am well aware of RH CoreOS.
7.
by andrewrynhard 4y ago
I would say that CoreOS is gone because RH destroyed it. Not because people didn't use it.
8.
by andrewrynhard 4y ago
We mention CAPI but certainly not 2.0 since the CAPI we are referring to is "Cluster API" and they only have 1.0.
9.
by andrewrynhard 4y ago
For folks who are all in on a single cloud provider it might not make sense, but if you run Kubernetes in multiple clouds, on-premise, edge, etc. then it starts to make a lot of sense since you get consistency.
10.
by andrewrynhard 4y ago
The same spirit as CoreOS but it is something entirely different. Written from PID1 up solely for the purposes of running Kubernetes.
11.
by andrewrynhard 4y ago
It is a 50MB squashfs.
12.
Is Vanilla Kubernetes Too Heavy for the Raspberry Pi?(talos-systems.com)
4 points by andrewrynhard 5y ago|0 comments
13.
Talos – Modern OS for Kubernetes at the Edge(talos-systems.com)
6 points by andrewrynhard 6y ago|0 comments
14.
by andrewrynhard 6y ago
Have you guys taken a look at Talos?
15.
by andrewrynhard 6y ago
For a project similar to bottlerocket, checkout https://github.com/talos-systems/talos . It is geared for cloud, VMware, and bare metal users. We have integrations with Cluster API for each, with the bare metal provider
16.
by andrewrynhard 7y ago
First of all, thank you for taking the time to write this out. The feedback is very valuable. I will do my best to address each comment. Let me start by laying out our design constraints. We knew we wanted a handful of simple features: -
17.
by andrewrynhard 7y ago
The rootfs in stored in the booloader partition and in the initramfs. As for NFS, I can see us adding support for that, but the out of the box experience for Talos in any of clouds will be painful if we exclusively require NFS. Since we adh
18.
by andrewrynhard 7y ago
Thanks! I haven't heard of Zulip, I will be taking a look!
19.
by andrewrynhard 7y ago
I haven't tested in Virtualbox yet. Would you mind either join our slack or creating a GitHub issue where we could provide better support?
20.
by andrewrynhard 7y ago
I spent a lot of time in v0.2 building Talos for ARM, and it works, but there is a good amount of work to be done to make it official. We need to setup ARM nodes to run our builds from, and refactor our build logic to account for multiple a
21.
by andrewrynhard 7y ago
Please file an issue on GitHub and we would be happy to look into this.
22.
by andrewrynhard 7y ago
Interesting. We PXE boot Talos in packet. One user is even go so far as to PXE boot Talos on every boot.
23.
by andrewrynhard 7y ago
You absolutely could. The rootfs is read only so what you can do is limited. Kubernetes also landed support for ephemeral containers in 1.16: https://github.com/kubernetes/enhancements/issues/277 . It still ne
24.
by andrewrynhard 7y ago
We do support storage volumes. A recent change in Rook seems to have broken how it works with Talos, but we know storage is important and we are working on fixes. We would love to land support for Nvidia GPU containers. Your not the first t
25.
by andrewrynhard 7y ago
We have our provider here: https://github.com/talos-systems/cluster-api-provider-talos Perhaps OS isn't the right thing to call, but I don't know a better alternative :D
26.
by andrewrynhard 7y ago
I agree with this to an extent. There are certainly places where replacing can be expensive. For example, bare metal, or if the machine contains a large amount of data and moving that data to a new node is time consuming.
27.
by andrewrynhard 7y ago
We are taking two approaches to this. The first is that you could roll out a replacement node and shutdown the old one. In bare metal scenarios this is much harder so we implemented in place upgrades, but they work very similar to creating
28.
by andrewrynhard 7y ago
Yes we do. I personally am working on the channel based approach for our 0.3 release that we just started developing. I would love it if you could make a meeting some time soon to chat some more. User feedback will be really help. Since Tal
29.
by andrewrynhard 7y ago
As an engineer I understand this completely. We are already discussing internally how we can improve our site and documentation. Our goal is to create a vibrant community and getting all the sales fluff out of the way is something I support
30.
by andrewrynhard 7y ago
We have added an API to help with the practical issues in removing SSH. In doing that it has also opened up interesting opportunities in automation that we are currently fleshing out. The difference here is that Talos is purpose-built for K

More ›