woopwoop24

there is a good talk from kelsey hightower on when it makes sense to ue k8s and the number was like 20 servers. i think with what you are describing i would not even think about using k8s.

the whole topic is kinda absurd. for me it lies in the same spectrum as rewriting old books, because of some pc bullshit. Hope one day we can appreciate the differences instead of going for the lowest common denominator

because everyone could have a different opinion on what it actually means instead of just a simple time based measurement. The whole thing is just absolute bonkers

i bet the processes will allow it if they really see the risk of losing you. If even then they don't care --> leave as fast as you can. Company is not your friend and usually not interested in "wasting" money on giving you more salary then they have to.

at least my 2 cents

i quite like that and always try with new projects to make it as easy as possible to start collaborating for new mates and addings lots of safety nets so everyone feels comfortable to add changes to the system(s)

and to an extend how do you keep track of which unique part is active in which site if e.g a website gets hacked and resets your current password, because in case of a password manager i just create a new one and be done, on top of my mind i would have the question for you: would you recreate all websites with a new unique part or just create a system for outliers? not to offend, just had several of these incidents in my years and for me a password manager is much more piece of mind

i think as we get older, we get better at distancing ourselves and realizing that work is just work. But as the one always the most dissatisfied with what we do and how we do it and what is left out, i try to understand and give empathy than the easier solution which would be head through the wall :)

what are you doing when a password from a weak site gets compromised exposing your algo? How do you memorize your "unique" key?

i don't get why people would choose AWS in the first place ever for any small/amateur project. It is ridiculously expensive, not transparent about the costs which could be coming your way and you need a shitload of components to get by. just get some fixed price machine at some shitty provider and see how it goes, if you need a bigger one, just by a bigger machine. And if you outgrow that it might be a reasonable idea to just rent some colo space and calculate the upfront costs against a small server you build yourself. an intel nuc with 16gb memory and 4 cores is about 200$ and draws nothing in power. buy 2 connect them direct and hook them up to the colo provider. unlimited fiber and there you go. AWS is such a joke

not always a we

invest in solar, wind and storage

and not tolerate that bavaria is doing a texas

Risk = Likelihood * Impact

If someone is capable enough to combine things, he does not need to be told this advise. All the others we tell just to follow common advise and not live by obscurity because it is crap most of the time. Strong security does not need obscurity

tl:dr not a big fan

so much +1 for the worst possible alignment of the keys above the arrow keys, is why mine is not used anymore it just pisses me off constantly. (i reprogrammed the keyboard but it still is a bad experience even when disabled or remapped) the speakers on the bottom are also not doing a great either. i think i will get a framework as the next one. Also PopOS is confusing to configure, much rather have plain debian and live with the pain of setting it up, but it behaves deterministic.

helm is a bad solution to a lazy thought out problem. why would i template yaml from another yaml and without versioning and weird if else constructs just for deploying which clearly should be json? because we devops are obviously not able to abstract the problem. oh you switched from nginx to haproxy, lets change all the labels in my git comitted repos where my yaml lies. oh the author changed the way the helm chart works, lets do manual compare to see what changed. Oh k8s changed the api version again, lets change all the yaml. and helmfile on top of helm -> more abstraction in the wrong direction -> love it.

i would much rather use something like starlark and program my deployment needs against the correct library version of the k8s api which my cluster has and get the final yaml for free instead of templating and forking and maintaining dead weight every damn version.

male 34, had it nov 2020, symptoms started dez/jan 2021. still chest pain, nausea, unrefreshing sleep and weird heart palpations and high pulse. got better over time, i am hoping the will release bc007 soonish, so that might be a solution for all of us struggling with our lives and wanting a normal life back. extremely frustrating knowing what was possible and not able to reach that again still happy to hear that most of the people recover just fine.

good idea at the same time sad because you will miss the opportunity to learn new music styles which are not based on your preferences, what you would archieve with something like radio. same concept in social media or netflix vs television or print media.

or is there a mode for a 1 in 5 tracks are random to your preferences just so you can have the option to learn something completely new?

if it was mine i would most certainly opt for ansible or something likewise, the overhead of logging into a machine and doing all the things by hand/manual is more complicated and error prone than a playbook would be (at least for me and me forgetting all the steps all the time ^^).

But who are we to judge, impressive to earn 2,5k every month with it, kudos.

advise another engineer gave me, when i was younger, was: "be confident and expect you are 100% the candidate they are searching for" e.g. don't say something i would like to hear back or whatever, say something like: "i am happy to tell you more in phonecall or face to face" expecting that the person on the other end wants to meet you, or even more so has no other choice than to pick you after reading your resume.

ps. looking at your resume i would also restructure, not leading with awards and what is "Wrote Software for Upwork " supposed to mean? also a lot of your github repos lack proper readme's. And i don't know what you put in your cover letter but i cannot see what you want to do or learn or what you are burning for.

i would suggest you take some money and hire someone from the outside to tell management and the devs exactly that. They will listen because it is coming from the outside. Then after that you can decide whether to change something or not, Does not matter what. personally i would also go for the low hanging fruits first: - backups of the database - git push all the code which lives on production

rewrites are super dangerous, double if the team is junior then they would need to double all the features, migrate, develop the skills they lack now, otherwise same mess in the end with a new framework and so on.

based on?

if you have more than one pod running at the same time, otherwise will be downtime if the container spawns somewhere else or am i missing something?

tl:dr if you need it, go for it :) my 2 cents is not needed at home and even for some of my clients the complexicty vs a simple setup and a few min downtime still speaks for MTTR instead of HA which noone can debug.

not about stress but to have HA proxmox cluster you will need at least 3 machines or fake one with a quorum machine without vms on it. Sure your vms will run if one machines goes down, but do you have HA Storage underneath? ganesha would work but more complexity or another network storage with more machines. Don't get me wrong it is fun to play with, but i doubt any homelab needs HA and cannot have a few minutes downtime. Or what do you do in case your internet provider goes down or when you have a power outage? i don't want to provoke, i have fiber switches and 10G at home and have 2 locations to switch in case one location goes down but i can live with multiple days of downtime if i have to, or if not i take my backups and fire some VM's on some cloudprovider and be back online in a few min and pay for it because backups are in both locations.

i would much rather develop a simple LB + autoscaling group with a deployment pipeline (lambda or some other control loop) and containers on it than a k8s cluster the client is not prepared for. if they outgrow this, most likely the following solution is better than going 100% "cloud" the first time. Most clients go from java 8 Jboss monolith to spring containers in k8s and then wonder why it is such a shitshow. but yeah pays the bills so i am not complaining that often ^^

HA is overrated, i'd much rather go for a low mean time to repair. Backups, reinstall, ansible playbook is my way to go if hardware fails, which is quite rare to be honest. HA goes beyond hardware in terms of "electricity, internet connection, storage, location etc.., IMO people quite often underestimate what it means to have real HA --> second location with identical setup to shift workload or even have active-active instead of active-passive. i have an intel nuc as plain debian server with containers on it. 2 raspberry pi's(act as loadbalancers with traefik and authelia on top) and a hetzner vm all connected through wireguard. All is configured via ansible and i rely on LE certificates to connect via https or directly via wireguard vpn to http if i want it only exposed via vpn. encrypted backups are copied via wireguard to an offsite storage box.

full down to back online if hardware is not damaged is less than 15 min.

it is very easy to do and rock solid, unattend-upgrades does the trick. i tried almost every combination and even though i am a k8s user from version 1.2 onwoards the complexity for k8s at home or even vsphere is too much for me vs. this super simple and stable configuration i now have.

info@diffus.org

you can PM me if you have more questions or want to talk in detail :) happy to help

around one offer every two days is the usual, some of them are absolute crap, some so so but some are not bad. i am on freelancermap, linkedin and xing. have to say since covid worked exclusively in banking and insurance, so not so sure what happended outside of my bubble. what is keeping you from doing it?

Germany, freelancer in "devops" we call it these days (infra automation, container, k8s etc..) with about 7 years of experience in linux and 10 years overall in consulting.

i charge around 100€-125€/h (+19% VAT) depending if onsite or remote. i have seen people go for 150€ but these are the ones kicked out first if there is an issue or company needs to save money.

i still believe most of the companies are better off with just deploying containers on vm's with autoscaling groups with a LB in front of it and some kind of terraform + ansible | CI-pipeline deployment to manage it.

all the complexity you have to buy with dealing with k8s. you have to update it frequently, update all the charts, fix all the breaking things in a developing ecosystem, and still have to deal with the hard parts of dynamic certs, storage and network. and you would still need to dedicate "normal" vms to host databases and your monitoring and your storage because if your cluster goes down, so is your management layer.

i have been with k8s since 1.3 and it is so disproportionate that i will not touch it for most of the times

time to actually stop the US government to access data in europe at all. It always has been and always will be a slap in the face to the rest of us, that it is accepted and allowed at all. fuck the NSA

i am using mine as gateways into my networks. All deployed with wireguard and traefik and authelia to let me login to anything with 2fa if i want it exposed, got tired of the very bad solutions some companies like synology provides with 2fa and dyndns.

no firewall ports just plug it in and ready to go in a second, and i use ssd's instead of sd cards for speed and reliability. Works without thinking about it for at least 1 year now.