Discover and read the best of Twitter Threads about #Kubernetes

Most recents (10)

Did you ever ask yourself if cgroups (containers, pods, whathaveyou) can impact the @golang runtime? I did and here's what I learned... (thread) 👇#Docker #Kubernetes #Linux
So ~2y ago, while working with a lot of customers moving into containers and #Kubernetes, I naturally hit the (now well-known) Java/JVM cgroups issues (all you need to know -> lightbend.com/blog/cpu-consi… and ).
Now, @golang being the language of my (your?) choice, this made me curious and I started to ask questions:
Read 25 tweets
Setting the @github branch protections rules automatically and declaratively, rather than manually and one at a time is just ... DOPE ! 🔥

@falco_org, mate you'll be really protected soon 👨‍🚒👩‍🚒

These little things make me so happy dunno why ! 😁
I'm using prow 👩‍🔧 .. An underestimated but awesome tool by the #kubernetes community. It can be used for setting up CI/CD systems but also to declaratively bake custom GitHub workflows on your repos via a hook and plugins system.

Grab it here 👇

github.com/kubernetes/tes…
Particularly a tool called branchprotection (no fantasy here 😅). Here the link to its source code 👉 github.com/kubernetes/tes…
Read 3 tweets
A heartwarming story on the power of open source community, a thread - @khnidk and I have been working on a rather large change in #Kubernetes to allow support for ipv4/ipv6 dual stack. It's a MASSIVE change which touches many parts of the code (as you can imagine). 1/10
This week is code freeze for the 1.15 release and we are trying to get this change in. It needs review by the sponsoring sig of the KEP. Which in this case is sig-network 2/10
So Kal did the work and got the PR ready and handed it over to sig-network. Extremely tight timeline given the size. Could we have gotten it to them earlier, sure. We probably could have done a lot of things to make this easier on everyone. 3/10
Read 11 tweets
Hey, you are all at #kubeconEU and drinking from the fire hose this week. I'd like to pitch to you to consider contributing actively to the community if you haven't already to help us all avoid the tragedy of the commons. Here's some things to get your started (1/16)
Every SIG is short handed when it comes to reviews! example sig-node put out a call for folks to help with issue triage. IMHO all sigs need help with both Issue triage and PR reviews - groups.google.com/forum/#!msg/ku… (2/16)
There is a few of us working on migrating Kubernetes project infrastructure over to the CNCF, this work crosses a whole bunch of SIGs. Here's where to find info on that work - github.com/kubernetes/com… (3/16)
Read 16 tweets
vRealize #NetworkInsight 4.1 has officially landed! With new capabilities in: #Container insights with #K8s and Enterprise #PKS, Application Discovery and Load Balancer insight. Also: @vmwarensx -T 2.4 support, #VMware Identity Manager! More in thread. RN: docs.vmware.com/en/VMware-vRea…
Application Discovery in #NetworkInsight 4.1 brings application context discovery direct from the infra. You can pull #CMDB data from @servicenow, using @VMwarevSphere or @awscloud tags or use a regular expression on the VM naming convention. Also; this honeycomb 🤤
#NetworkInsight App Discovery cont.: The honeycomb widget can be used to filter out the right applications to save. For example, you can select all apps that are talking to the internet or apps that are shared services. Stay tuned for a deep dive blog post, soon!
Read 11 tweets
Tinder moved to #Kubernetes and @EnvoyProxy, is averaging appx 50 containers, 15 pods per node. Interesting for a few reasons from my perspective
#1/ Bigger nodes running many containers is not so rare. At @signalfx we are seeing this more and more in the field. Is it too early to say that #Mainframe is making a comeback? #MillenialMainframe #GenerationM
#2/ "One reason we were able to move so quickly was due to the rich metrics we were able to easily integrate"
Seeing this everywhere. You can't fly a #jetplane without instruments and you can't run advanced #infrastructure without great #observability and #metrics
Read 4 tweets
1/ I don't buy the FUD that #kubernetes is hard. It is not harder than anything we have used in the datacenter (at least since I have been in IT).
2/ The adoption #kubernetes has seen, has been miles above what we saw with previous open source systems like openstack/cloudstack/opennebula/euca
3/ Folks who have been managing DC and smaller clusters for a while are used to that type of infrastructure.
Read 8 tweets
I've been administering #kubernetes clusters now for over a year. I've always been curious about Fargate, and the claim "it's really easy!". So I deployed an app to Fargate. Here's what happened....
Firstly, I still needed all the same infra that a Kubernetes cluster needs. So I had to define a VPC, subnets, security groups and all that jazz. That makes sense - the idea that AWS/Cloud is "free" is honestly deeply flawed
Then I had to define my ECS cluster. Hang on a minute? Isn't this supposed to be the container orchestration equivalent to "serverless" ? Why am I having to define the cluster?
Read 11 tweets
Let's talk about #Kubernetes and how you probably don't really need it, and how you should be tackling some hard problems for your org and your customers, not the k8s problems.
1/x
Let's start with use case no. 1:
You're dev team (in a scrappy startup, or big boy enterprise) and you've got a few devs but need to host your code/service somewhere, and you want to use k8s (assuming GKE/EKS/AKS being used and not rolling your own)
2/x
Pros:
+ Step up from current/recent deployment methods out there in the industry
+ GKE/EKS/AKS aren't horrendous!
+ Cost reductions are possible compared to many previous solutions
3/x
Read 19 tweets
#Spinnaker may be popular, but it has HUGE hidden cost when using with/on #Kubernetes.
1. The primitives are all IaaS-based
2. Many config changes require admin management and halyard reboot, meaning you need continuous deployment for your continuous deployment
3. There’s no abstraction for container platform in spinnaker, so you have to have a new “account” per k8s
4. There’s no namespace abstraction in Spinnaker, so you need a new account for each cluster+namespace permutation.
5. If you use RBAC in K8s, you have to synchronize Spinnaker permissions manually or write a tool.
6. The usability cliff to use Spinnaker is multiplicative when combined with the usability cliff of K8s, making onboarding new team members a nightmare.
Read 6 tweets

Related hashtags

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just three indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3.00/month or $30.00/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!