HNHacker News
TopNewBestAskShowJobs

joana035

393 karma · joined November 16, 2019

submissionscomments
joana035··on A better Kubernetes from the ground up
That is not fair, kubernetes uses the same existing technology in a well integrated fashion, including firewalling. That is what Network Policy and Service objects gives you.

Communication between pods running across different computers gets encapsulated in another IP packet. This is pretty standard across the industry.

joana035··on A better Kubernetes from the ground up
Correct, kubernetes is a destilation of those 15 years of experience acquired running something else that also has network, storage and compute concepts. I didn't said Google uses kubernetes, though :)

Still, kubernetes makes a wonderful job abstracting all the hard work of using the underlying tools.

Look how simple is to create a ipvs round-robin by just defining a "kind: Service" object, try to do the same using the bare tools in a way that is synchronized across N computers.

joana035··on A better Kubernetes from the ground up
I'm quite confident that one day kubernetes will make use of systemd-nspawn. Let's see... :)
joana035··on A better Kubernetes from the ground up
Sooner than later kubernetes will support live migration of workloads via checkpoint-restore of processes, like xen, and many other software already has.

https://en.m.wikipedia.org/wiki/CRIU

EDIT: https://github.com/kubernetes/kubernetes/issues/3949

joana035··on A better Kubernetes from the ground up
Kubernetes didn't need to be rescued in the first place. If you know how to manage any Linux box, setting up kubernetes is as easy as "# apt install kubelet kubectl".

Broadly speaking kubernetes saves time by providing an api for existing Linux technology. For example, iptables, ipvs, storage, self-healing, virtual ips, etc via yaml.

Kubernetes was created to give anyone "Google like, production grade" infrastructure without the vendor lock-in of the cloud. And kubernetes on physical machines is where it shines most.

EDIT: it is very easy to complain that kubernetes is complex, but try to do virtual ips with keepalived, corosync, pacemaker to understand how much time kubernetes saves by providing the same capability in a generic way which is easy to use. I have the feeling that people take kubernetes for granted without knowing how much manual work one has to go through in order to build a similar experience using the standard building blocks available.

EDIT 2: straight out of kubernetes home page: "Kubernetes builds upon 15 years of experience running production workloads at Google" that is a lot of saved time just by using kubernetes.

joana035··on I can't vacuum because us-east-1 is down
It just drives me nuts to know that with the same price you can get a 12CPU+128GB of memory on Hetzner, on AWS you get 4CPU+8GB memory.

I will not even mention the bandwidth costs :)

joana035··on Someone attacked our company
And I does not looks like a DDoS either, this amount of connections is quite normal for mid-sized apps, and connections can be kept open in case you app is slow, making your stats higher than it actually should be.

Btw, two servers plus a bit of architecture simplification solves this and cut the costs down to ~$400 or less.

joana035··on I can't vacuum because us-east-1 is down
This is FUD, full control to handle the situation, to the extent of your knowledge is awesome.

When AWS goes dark, pray and go grab a coffee, there is nothing you can do.

Keep pressing refresh on aws status page.

joana035··on Someone attacked our company
The article mention the use of lambda/serverless. If he had a server many of these issues would not exist in the first place :)
joana035··on Someone attacked our company
It's incredible that C10K was achieved in 1999. http://www.kegel.com/c10k.html
joana035··on Winding down my Debian involvement (2019)
Cannot say for a company, but in Debian it seems that source code control is being settled with https://salsa.debian.org. For upstream code it is pretty flexible and low expectations are set, a tarball is enough. It also works with git (branches and/or tags), cvs, hg, etc.

There is no need for complexity in order to transfer files, that is why File Transfer Protocol works well. If you refer to public FTP services, those were deprecated 3 year ago. See https://www.debian.org/News/2017/20170425

joana035··on Winding down my Debian involvement (2019)
From last two month there are 6 new Debian Developer and 10 new Debian Maintainers. This information is available at https://bits.debian.org

For me, working with packaging is a joy, once I learned how it works I see it as a thin wrapper around an upstream code base that, after built with whatever upstream tooling, is copied within a package alongside it's dependencies information.

joana035··on Transitioning from Docker to Podman
Is always good to report packaging bugs so then people can fix them, do you have examples of python packages that can be improved?
joana035··on Transitioning from Docker to Podman
Kubernetes is a consistent management api for linux (so then you don't need to interact with iptables, mount and all that "hard stuff").

I don't think kubernetes is a solution for context of building an image (a rootfs tree into a .tar.gz file).

Unless you are using kaniko which extends the kubernetes api to add the capability of creating images, but that is handled by kaniko itself via the same api.

joana035··on Transitioning from Docker to Podman
That is the main reason why podman exist, so then one can accomplish that task without an extra daemon, dind, nor using the host's dockerd daemon.

This way you don't need to grant "docker" group to the "ci" user and you avoid having your cluster compromised one commit away :)

joana035··on Transitioning from Docker to Podman
Check the first link in the "resources" section at the bottom of the article page.
joana035··on Transitioning from Docker to Podman
You're welcome :)
joana035··on Transitioning from Docker to Podman
Here you go: https://www.freedesktop.org/software/systemd/man/systemd-not...
joana035··on Transitioning from Docker to Podman
>> beastly 5G docker image > my beastly 12GB image that even includes Matlab wants a word with you

Perhaps in the next 10 years we will be rediscovering packages. :P

If you are in the business of charging complex prices per bits over the network, then docker seems to be quite a good investment and making it as popular as possible is a good strategy to print money. /s

joana035··on Transitioning from Docker to Podman
It is because to build the image using docker requires the docker client to talk with a dockerd daemon, so one has to configure the client to access the dockerd which allow untrusted code to run as root in the host.

Docker-in-docker is a workaround to make docker work in CI.

Basically a security nightmare and bad design that podman doesn't have.

joana035··on Transitioning from Docker to Podman
> I actually like the idea of Docker as a better systemd (or rather, the interface is better). No bespoke file format, programmable API, no need to google for the right journalctl switches, and then of course the advantages of containers and images over processes and system packages. I’m not suggesting everything should be a container nor that docker is the ideal implementation, but it certainly points in the right direction.

Docker was created to give an extra life for legacy applications depending on outdated packages, the concept of gluing all dependencies withing a compressed rootfs and shipping that, with low effort.

Docker became popular because of that, but seems that did more harm than good for the ecosystem in terms of security, that why podman might have a great future. The docker interface is bad and comparing that with systemd is quite a stretch. ;)

Anyhow, aren't systemd units ini files? The journalctl ships with man pages though.

Aren't containers just processes with namespaces and cgroups?

joana035··on Your Computer Isn't Yours
I definitively don't want to live in this kind of world :P

But there is already companies selling computers with linux pre-installed like system76, dell and others.

joana035··on Your Computer Isn't Yours
And those are true heroes.

It is an immense effort to make proprietary hardware to work well, specially Apple hardware.

joana035··on Your Computer Isn't Yours
I'm happy GNU/Linux user for many years and I don't remember when was the last time I had to do those kind of things.

Choose a mature/stable distro and that is it. Be prepared to trade a bit of convenience for privacy in case of weird/non-free hardware/firmware.

joana035··on Microsoft and the NSA
Microsoft become a PRISM provider in 2007 and Skype in 2011.
joana035··on AWS NLBs and the mixed up TCP connections
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/placemen... check it out :)
joana035··on AWS NLBs and the mixed up TCP connections
It still data center.

And when you choose the low latency instance placement means that all your virtual machines are placed in the same rack and/or host.

Basically throwing availability over the window.

joana035··on Obscurix – Arch Linux-based OS configured for privacy, security and anonymity
Linux security modules, always good to have. AppArmor, SELinux, Smack, and TOMOYO are good examples.
joana035··on How to put machine learning models into production
Airflow is a good replacement and works well, easy to deploy and to add datasources/steps.
joana035··on BleedingTooth: Linux Bluetooth Zero-Click Remote Code Execution
Worth noting the fix has been sent to linux-next instead and distros were not informed: https://twitter.com/mjg59/status/1316484882877435904
← PreviousPage 5 of 7Next →