I'll post more later (reply here to remind me), but I have your exact setup. It's a great way to learn k8s and yes, it's going to be an uphill battle for learning - but the payoff is worth it. Both for your professional career and your homelab. It's the big leagues.

For your questions, no to all of them. Once you learn some of it the rest kinda falls together.

I'm going into a meeting, but I'll post here with how I do it later. In the mean time, pick one and only one container you want to get started with. Stateless is easier to start with compared to something that needs volumes. Piece by piece brick by brick you will add more to your knowledge and understanding. Don't try to take it all on day one. First just get a container running. Then access via a port and http. Then proxy. Then certs. Piece by piece, brick by brick. Take small victories, if you try to say "tomorrow everything will be on k8s" you're setting yourself up for anger and frustration.

Yeah with Amazon's sheer size this has definitely been done before, curious what limits op is going to hit. My guess is they have a quota for submissions, and they'll be banned from submitting tickets.

I mean go for it? They literally can't do anything, you might as well complain that fire is hot though. It's part of being in the Internet. They provide safety gloves, via VPCs and firewalls, but if you choose not to use them then.. yeah I mean youre probably gonna get burned

Uh sorry dude, but no this isn't a script kiddy, these are bots that scan every IP address every day for any open ports, it's a constant thing. If you have a public IP, you have people, govs, nefarious groups scanning it. AWS will tell you the same as if you were hosting it locally, close up the ports, put it on a private network. Use a vpc and WAF in AWS' case.

I get scanned constantly. Every hour of every day dark forced attempt to penetrate our defences.

Shows that no matter what you do, people will be mad at you.

Hm, I'm more excited for SpongeBob 4: Spacewhales

Honestly wonder if it was to prevent protests from moronic religious groups who claim to hold a monopoly on the word "messiah"

Unprecedented is not a bad word. It means there's no precedent. I mean we're finally pushing back.

It seems to run on some form of electricity!

The only reason this would need to be a bill is if people are upset that they are failing the exam. Which means they qre failing the exams, to the surprise of no one.

What we should be doing instead is making our neighborhoods more accessible to those without cars. I'm sure they feel like their mobility is gone if they lose their license, but that shouldn't be the case to begin with.

So tone deaf, and clearly they're just trying to steer the narrative.

They call out that it's never taken lightly and it has to happen. We know. Stop killing games just says you have to do something when you turn off the servers. Either release the server source code so it can be engineered by the community, release a self hostage server alternative, even just documents or guides on how to get started.

But they're going to try to make it about the mean old gamers want them to go broke

Have you seen the surface-linux project on GitHub? They've been maintaining a kernel for it. Idk if it'll work with your distro but I'd start there

Very happy for you! Seconded to just banking it. If it was 50k that would be different. Throw half in a CD and the other just plan out ongoing expenses. Make sure backups are working, maybe use a bit of the cash to try recovering from a backup just in case.

If your cost is 250 a month, then in reality you only have 2 years of runway there, if you don't grow. Good intention and I respect that, but I think keeping beehaw going long term is better than anything else you would do with the money

Hm, probably sitting at home playing too many videos games

Personally I agree. I've seen way more startups kicking off with these waves of layoffs. It's a silver lining, not much more, but I'm happy to see people finally realizing they don't want the big tech solutions anymore.

Not at all. Proxmox does a great job at hosting VMs and giving a control plane for them - but it does not do containers well. LXCs are a thing, and it hosts those - but never try to do docker in an LXC. (I tried so many different ways and guides and there were just too many caveats, and you end up always essentially giving root access to your containers, so it's not great anyway). I'd like to see proxmox offer some sort of docker-first approach will it will manage volumes at the proxmox level, but they don't seem concerned with that, and honestly if you're doing that then you're nearing kubernetes anyway.

Which is what I ended up doing - k3s on proxmox VMs. Proxmox handles the instances themselves, spins up a VM on each host to run k3s, and then I run k3s from within there. Same paradigm as the major cloud providers. GKE, AKS, and EKS all run k8s within a VM on their existing compute stack, so this fits right in.

Just focus on one project at a time, break it out into small victories that you can celebrate. A project like this is going to be more than a single weekend. Just get proxmox up and running. Then a simple VM. Then a backup job. Don't try to get everything including tailscale working all at once. The learning curve is a bit more than you're probably used to, but if you take it slow and focus on those small steps you'll be fine.

At issue was a 2018 ballot initiative, Proposition 12, that bans the sale of pork products in California unless the sow from which the butchered pig was born was housed with at least 24 square feet of floor space.

6 foot by 4 foot. That's the minimum the law asks for and Iowa producers are upset by that? If an adult lays down on the ground that can easily take up that much room.

I think at this point I agree with the other commenter. If you're strapped for storage it's time to leave Synology behind, but it sounds more like it's time to separate your app server from your storage server.

I use proxmox, and it was my primary when I got started with the same thing. I recommend build out storage in proxmox directly, that will be for VM images and container volumes. Then utilize regular backups to your Synology box. That way you have hot storage for drives and running things, cold storage for backups.

Then, inside your vms and containers you can mount things like media and other items from your Synology.

For you, I would recommend proxmox, then on top of that a big VM for running docker containers. In that VM you have all of your mounts from Synology into that VM, like Jellyfin stuff, and you pass those mounts into docker.

If you ever find yourself needing to stretch beyond the one box, then you can think about kubernetes or something, but I think that would be a good jump for now.

And holt reminded him that it's still a narrative that needed to be corrected. What about the one where Terry was profiled? Or holt was denied his promotion?

It's pretty clear that you wouldn't approve of any cop show that tries to work through these issues, so I'm not going to bother arguing with you. I think they did a great job, a lot of those episodes were very hard to watch because they were confronted with choosing a career under one pretended and then saw the reality. To do that with a comedic tone is incredibly hard, and I think they did well.