blixtra

8 ms·

31.
by blixtra 7y ago
Flatcar Container Linux is a drop-in replacement for CoreOS Container Linux which in my mind (I conceived the fork) makes it more than "an (almost) equivalent alternative". You can literally update straight into Flatcar from Cor
32.
by blixtra 7y ago
Most of our Flatcar Container Linux users run Kubernetes. It's really an ideal match for a minimal container OS.
33.
by blixtra 7y ago
A former rkt dev here. rkt was archived by the CNCF with our blessings. Was just speaking to other rkt folks at FOSDEM about archiving the project on GH as well, which should happen shortly. We will also announce deprecation of rkt in Flatc
34.
by blixtra 7y ago
Chris from Kinvolk here. Our Flatcar builds are already completely independent of CoreOS builds. This is quite exciting for us as we can finally start updating the included software versions. We've been doing this a while for the edge
35.
by blixtra 7y ago
The whole point of CoreOS Container Linux was to deliver a steady stream of security/software updates. We've been eager to update packages for Flatcar Container Linux but have wanted to maintain as much compatibility as possible f
36.
by blixtra 7y ago
Just to reiterate what others have said, because this comes up quite a bit. You should not use CoreOS or Flatcar images as the base for your containers. They are intended to be the host operating system upon which you run the containers. Th
37.
by blixtra 7y ago
Chris from Kinvolk here. We're happy to talk about what you need on the security front. Some of the folks working on Flatcar Container Linux have a very strong security background; worked on AWS' EC2 security team, do regular pent
38.
by blixtra 7y ago
Happy to answer any questions about Flatcar Container Linux ( https://www.flatcar-linux.org/ ). It should be noted that we went a step further than CoreOS by releasing the update service we use to manage updates as an open so
39.
by blixtra 7y ago
We started Flatcar Container Linux to provide the option of continuing as is. We don't like to see perfectly good software be discarded simply because of an acquisition. We understand the hassle with porting configurations and have fou
40.
by blixtra 7y ago
Kinvolk ( https://kinvolk.io ), the Kubernetes Linux experts | Berlin, Bengaluru ONSITE or REMOTE | Full Time Kinvolk is a company focused on services and products for open-source cloud native Linux technologies. While having star
41.
by blixtra 7y ago
Kinvolk ( https://kinvolk.io ), the Kubernetes Linux experts | Berlin, Bengaluru ONSITE or REMOTE | Full Time Kinvolk is a company focused on services and products for open-source cloud native Linux technologies. While having star
42.
Comparative Benchmark of Arm, AMD, and Intel for Cloud-Native Workloads(kinvolk.io)
65 points by blixtra 7y ago|22 comments
43.
Comparative Benchmark of Arm, AMD, and Intel for Cloud-Native Workloads(kinvolk.io)
4 points by blixtra 7y ago|0 comments
44.
Performance Benchmark Analysis of Istio and Linkerd(kinvolk.io)
20 points by blixtra 7y ago|2 comments
45.
by blixtra 7y ago
True, the current Lokomotive repository consists of mostly code forked from Typhoon, something we state in the article. There are a number of small and largish modifications: support for Packet, additional PSPs, etc. But this is just the ba
46.
Lokomotive: An engine to drive cutting-edge Linux technologies into Kubernetes(kinvolk.io)
43 points by blixtra 7y ago|3 comments
47.
Flatcar Linux Edge Brings New and Experimental Linux Technologies to Kubernetes(kinvolk.io)
2 points by blixtra 7y ago|0 comments
48.
Hardware vulnerabilities in cloud-native environments(kinvolk.io)
3 points by blixtra 8y ago|0 comments
49.
Runc “Breakout” Vulnerability Mitigated on Flatcar Linux(kinvolk.io)
1 points by blixtra 8y ago|0 comments
50.
Abusing the Kubernetes API Server Proxying(kinvolk.io)
2 points by blixtra 8y ago|0 comments
51.
Exploring features and conventions of BPF ELF loaders(kinvolk.io)
2 points by blixtra 8y ago|0 comments
52.
by blixtra 8y ago
As to why we'd do it in the first place, the answer is that our mission as a company is to support foundational Linux technologies for cloud-native infrastructure. We're not looking to create new technologies, but to improve and s
53.
by blixtra 8y ago
That's a very valid question and one we also asked ourselves before taking on the task. There are three main considerations that made us feel this is doable. Firstly, Flatcar is a minimal Linux distro, with more effort made to reduce t
54.
by blixtra 8y ago
Chris from Kinvolk here. Flatcar Linux is generally available and we are committed to keeping it as a drop-in replacement for Container Linux for the long-term. We were excited about the idea of CoreOS when it was announced in 2013 and thin
55.
by blixtra 8y ago
Chris from Kinvolk here. It's open for general use now. :)
56.
Flatcar Linux: The CoreOS Operating System Lives on Beyond Red Hat(thenewstack.io)
4 points by blixtra 8y ago|0 comments
57.
by blixtra 8y ago
Chris from Kinvolk here. As Jimmy mentioned, we've done a good chunk of the work on rkt with CoreOS and are happy to support customers using rkt, and have done so for CoreOS, BlaBlaCar, NASDAQ and others in the past. But we've cho
58.
Flatcar Linux, a Container Linux fork, is ready for production(kinvolk.io)
2 points by blixtra 8y ago|0 comments
59.
Towards unprivileged container builds(kinvolk.io)
3 points by blixtra 8y ago|0 comments
60.
All Systems Go! 2018 announced – The foundational userspace Linux conference(all-systems-go.io)
2 points by blixtra 9y ago|0 comments

More ›