How do you guys do it? Curious, because I only ever lived in the k8s/cloud native world.
47 karma · joined July 19, 2015
How do you guys do it? Curious, because I only ever lived in the k8s/cloud native world.
Currently, when planning to use kubernetes for your infrastructure, the choices you have are either self-hosting and operating your clusters or using one of the many managed public cloud offerings. Both options come with trade-offs. Be it vendor lock-in, high operational overhead or data privacy concerns.
Flynnt tries to be another option with different trade-offs.
How does flynnt compare to EKS, AKS, GKE, etc? In general, most hosted k8s service providers force you to use their compute service offering and don't allow adding arbitrary nodes from outside. So, flynnt is best compared to "EKS Anywhere", "GKE Anthos" or similar.
Privacy: We are a european company and will be 100% GDPR-compliant on launch. Our service is currently hosted in germany. Your data does not need to be moved into a cloud just for using higher-tier abstractions like kubernetes.
Pricing: Pricing will be fixed per cluster. As you can use whatever hosting provider you want, just choose the provider that fits your pocket. You can also mix different providers for your compute nodes. Just be aware of latency for inter-node communication.
My name is Phil and I am looking for users for the Closed Beta. If you are interested to give this a shot, just fill out the form on the website or shoot me an email (in profile).
Thanks for reading, your feedback is welcome, happy to answer questions.
For serious software you want a proper local/unit test setup anyway. Using this in your dev cycles is just the natural next step. Instead of waiting for the cdk/cfn deploy to finish, which really is way too slow, you just execute 'jest' or whatever test framework you have.
Sure, figuring out how to mock everything takes some upfront time, but it pays off in the long run.
Oh well, I guess experiences differ.
No one is positive and happy all the time and having to fake it "as a job requirement" sounds wrong on so many levels.
Cloud only ever is worth it when one uses the higher-tier services, like AWS Lambda and the likes. Even running Kubernetes in the cloud is only semi worth it, because it's not high enough in the stack and still touches too many low-level IaaS services.
Of course, higher tier means more vendor lock-in and more knowledge required and all that. But if you are not willing to pay that price, then OVH, Hetzner and the likes will have better offerings for you.
Userland docker builds
I encountered problems with the default kernel configurations during the writing of my bachelor thesis and wasn't able to really read up on what could have been done to solve those problems. For example i observed high cpu usage only on the first core (similar to what the author describes in the article) due to a high amount of network interrupts. I tried to make those interrupts to be handled by all cores, which was neither recommended (as i remember) nor did it really help.