@alexellisuk Not in production, but the evaluation in my thesis showed that it scales well. You can check out the results in the docs or the linked thesis repository
Iโm at #KubeCon this week! Come by the STACKIT booth and say hi. Iโm happy to chat about sharding in Kubernetes controllers: https://t.co/VeDNse9wBG
I recently submitted my Masterโs thesis on sharding Kubernetes controllers for making them horizontally scalable. Read the full thesis here: https://t.co/c7IRcBfEJO
Super happy about how my Master's project on #Kubernetes controller sharding turned out: https://t.co/VeDNse9wBG
It's ready for usage and experimentation. Check it out, give it a spin, and reach out with feedback!
@the_sttts@ibuildthecloud@Mangirdas What would be the limit then? etcd or API server? I guess the controller-side can scale out nicely as long as the watch cache is restricted to what the controller shard is actually responsible for.
@the_sttts@ibuildthecloud@Mangirdas Maybe sharding controllers and their caches can help? Some ideas I'm experimenting with these days: https://t.co/VeDNse9wBG
@alexellisuk@tsaha Leader election prevents you from scaling controllers horizontally. I looked into the topic for a study project and working on it again right now for my Masterโs thesis: https://t.co/VeDNse9wBG
The idea is to apply sharding mechanisms to make controllers scalable
@ibuildthecloud One can instruct API server to write leases to a different etcd cluster and configure this one to use the in-memory store. We are using this option to write events to a dedicated etcd cluster which still has persistent storage but doesnโt do costly delta snapshots.
Talking at #Rejekts23 was fun! ๐ ๐๐ป Let me do another round! ๐
I opted in for a spontaneous lightning talk about my study project on Kubernetes Controller Sharding at 6:15 pm.
If youโre interested, here is the live stream: https://t.co/0jaLR8K9vA
Iโm excited to be speaking at @rejektsio in Amsterdam! Join our talk in which we will share our learnings from implementing credentials rotation for #Kubernetes clusters at scale in @GardenerProject. Looking forward to having a chat at the event!
We welcome @rafaelfranzke (@SAPdach) & @timebertt (Stackit) to #Rejekts2023 in Amsterdam!๐ท๐ด
They will walk us through methods to manage a plethora of credentials in a secure way & share learnings from cluster admins as well as app devs!
For late๐ซs๐https://t.co/LlqJAF5785
@stefanprodan@fluxcd I explored the idea of controller sharding last year in a study project: https://t.co/VeDNse9wBG
It builds on the same idea (label selector per instance) but doesn't require explicit configuration and also adds an instance that takes over labeling. Might be interesting for you :)
@thockin@alexellisuk @crenshawdotdev @CloudNativeFdn If you had metrics for owner references you were able to join time series in PromQL for grouping. Owner references as such are core api machinery concepts and applicable to all resources. Generically finding the top-most owner is probably not possible in PromQL
@alexellisuk@honratha There is a containerd cri configuration option which tells it to pull images for registry x from mirror y: https://t.co/UxNuDxuDN0
We didnโt try supporting it for the legacy dockershim, so I donโt know if this works with docker as well.
@alexellisuk@honratha We ended up deploying a cache per upstream registry listening on different ports as well. So far this works great for speeding up image pulls for different public upstream registries in our dev setup.
@alexellisuk@honratha I think this might be a limitation in the protocol. I remember looking into the same thing and checking debug logs how things are actually fetched from the mirror: the host (registry name+port) of the image name was never sent over the wire but only the repository+tag.
Seattle Kubernetes Meetup is back after 3 years!๐ฅณ https://t.co/K6MQN5BuPe I'll be there to talk about scaling controllers and present @timebertt's paper on this topic.