John Price
Gang Gang
- Sep 19, 2008
- 384,624
- 30,385
He's looking for a business partner not a chefDon't get why he's running an influencer show and not a cooking show
He's looking for a business partner not a chefDon't get why he's running an influencer show and not a cooking show
what is this
We are workingget on Battlebit.
⣿⣿⣿⣿⣿⣿⣿⣿⠟⠋⠁⠀⠀⠀⠀⠀⠀⠀⠀⠉⠻⣿
⣿⣿⣿⣿⣿⣿⣿⠁⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢺⣿
⣿⣿⣿⣿⣿⣿⣿⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠆⠜⣿
⣿⣿⣿⣿⠿⠿⠛⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠉⠻⣿⣿
⣿⣿⡏⠁⠀⠀⠀⠀⠀⣀⣠⣤⣤⣶⣶⣶⣶⣶⣦⣤⡄⠀⠀⠀⠀⢀⣴⣿
⣿⣿⣷⣄⠀⠀⠀⢠⣾⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⢿⡧⠇⢀⣤⣶
⣿⣿⣿⣿⣿⣿⣾⣮⣭⣿⡻⣽⣒⠀⣤⣜⣭⠐⢐⣒⠢⢰
⣿⣿⣿⣿⣿⣿⣿⣏⣿⣿⣿⣿⣿⣿⡟⣾⣿⠂⢈⢿⣷⣞
⣿⣿⣿⣿⣿⣿⣿⣿⣽⣿⣿⣷⣶⣾⡿⠿⣿⠗⠈⢻⣿
⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⡿⠻⠋⠉⠑⠀⠀⢘⢻
⣿⣿⣿⣿⣿⣿⣿⡿⠟⢹⣿⣿⡇⢀⣶⣶⠴⠶⠀⠀⢽
⣿⣿⣿⣿⣿⣿⡿⠀⠀⢸⣿⣿⠀⠀⠣⠀⠀⠀⠀⠀⡟⢿⣿
⣿⣿⣿⡿⠟⠋⠀⠀⠀⠀⠹⣿⣧⣀⠀⠀⠀⠀⡀⣴⠁⢘⡙
⠉⠉⠁⠀⠀⠀⠀⠀⠀⠀⠀⠈⠙⢿⠗⠂⠄⠀⣴⡟⠀⠀⡃
L M A OWe don't even have off-site storage.
I mean, I could bring some backups home just in case, but I don't give a shit.
Management never thinks ahead, so why should I put in extra effort to cover their asses
He's looking for a business partner not a chef
in MC the winner gets like 250k and the trophyDon't they say the same thing on Masterchef? The winner basically becomes a franchisee
f*** YOU MASTERCHEF WAS TODAY I FORGOT
meh it's still entertainingwho cares, new masterchef isn't the same
I don't know how to persist volumes when deploying kubernetes on-prem.what is this
bro how are you going to ignore me. not cool.oppenheimer sounds boring
Dude you are way too f***ing smart, and it's awesome you battled through some real shit to get here.I don't know how to persist volumes when deploying kubernetes on-prem.
In Azure or AWS clusters, you could just leverage their built-in CSI drivers and create storageClasses based on pre-defined drives or via the dynamic provisioning. It "just works" in cloud because the cloud is awesome.
I don't know how to satisfy PersistentVolumeClaims in on-prem scenarios because there is no "default" disk provisioning. Users will have to build their own disks and then I don't have a good native way to manage that storage.
I was looking at some tools and things like OpenEBS, rook-ceph, and Longhorn seem pretty popular. Longhorn seems the easiest to use from a deployment/configuration experience, but I have no idea if it's overkill, underkill, just right, terrible, unreliable, etc.
So, I come to you as an expert developer, what's the best way to persist block storage in a kubernetes environment which is of course, ephemeral by nature.
The application won't need any disk, but we are leveraging Clickhouse now as an OLAP database to store info on files which are scanned and classified. Traditional SQL/PGSQL was just too slow on the query side to support the kinds of records we're loading - up to billions per-client. It is vital that Clickhouse - which will be deployed inside kubernetes as a statefulSet resource - has some kind of volume persistence so that if the node restarts, data is not lost. It would also be good to be able to take and automate snapshots and backups for this deployment.
What do you think?
i ain't reading all that shit bro the us game is onbro how are you going to ignore me. not cool.
Might be holding off until next March to go. Not 1000% sure though. I WILL be going though, just not sure if it will be in September or in March/April. Wouldn't mind going when the cherry blossoms come into bloom.@Oogie Boogie when you go to japan go to one of those hole in the wall shops the locals eat at
You are so disappointingi ain't reading all that shit bro the us game is on