Seems to me that disgust for the practice grows exponentially with reposter's audience size. If I see something worth resharing with friends, I'd never consider Instagram as an outlet to do so. Instead, I opt for a personal sharing channel like a DM or iMessage thread.
I really enjoy Gitlab's UI/UX, but I wish it were easy to manage a self-hosted Gitlab presence. The architecture diagrams[1] frankly read as supporting justification to go with the hosted solution.
> Spinnaker is an open-source, continuous delivery system built by Netflix and Google
Politely correct me if I'm wrong...isn't Spinnaker originally a Netflix system, having nothing to do with Google? Unless perhaps the author is alluding to open source contributions by Google after the tool went open source?
I don't know enough about the data to contribute any thoughts on it. Could be valid, could be incomplete/inaccurate. However, I don't think this is an either/or situation, and wouldn't it be great if we contributed some time and focus on making sure that there is a world left in which the impoverished can be helped?
I can only think about this and be fearful due to the staggering number of Docker tutorials that happily whisk away the details as a sales pitch for streamlining the development process. Similar to the Node ecosystem, there's bound to be lots of junk out there that will never be updated.
Oof, you know there're problems with USB-C when even Google in their official press shots show a dongle being used with their hardware key. Not very elegant, is it.
Every time I'm reminded that Washington was only granted statehood after the Civil War, I realize how young an area this is and how little we truly know about it. We live in the wild out here and every day we seem to discover a new way that it'll kill us all.
I have to echo this sentiment because LYAH came across as foreign and generally unhelpful. It seems that in educators' pursuits to make CS more accessible to a wider audience, this becomes one example of how not to do it.
> 1. Look at how many flights work out well https://flightaware.com/live/ there's something like a million people in the air at any given time. It's extremely unlikely that your plane will be the unlucky one. Take a screenshot and keep it on your phone.
Can that work against a fearful mind though? Look at all of these planes flying safely! Statistically, in a strange way, the chances of a crash are only increasing in light of all of those safe flights I'm watching on Flight Aware.
At the fundamental layer, start with cgroups and namespaces. If you're looking for practical knowledge, start with making and running a Docker image - usually a basic "hello world" web server (nginx) is a good one to start on :)
Your experience is a real shame, truly. If Kubernetes could fix their horrendous documentation and onboarding story, I think you'd have a much better experience. After bruising past that battle, I found Kubernetes to be the perfect mix of sanity and opinionated architecture. I think part of it is also due to how rapidly it's evolved over the past 2 years, so hopefully you get a chance to revisit it once some of those rough edges are smoothed over!
Certificate authorities. Think VeriSign, InCommon, Let's Encrypt, etc. The folks that we generally implicitly trust to authenticate popular websites. Your laptop comes distributed with many certificate authorities that are configured to be trusted by default.
Agreed. Whether or not your listed events are the exact same set of reasons for his ousting, it's a good thing for our industry that his brand of unethical leadership is being shown the exit. As if TK is the only leader than can deliver the same type of value. Good riddance! Lyft just got their opportunity, hopefully they learn from Uber's mistakes.
The author's misunderstanding of role and function of these tools played a big part in their declared winners of each section. I'd say on the whole that this comparison article is useless.
We're talking about the difference between linear fluctuations and order-of-magnitude changes. For visual aid, please refer to this relevant XKCD: https://xkcd.com/1732/
For single-provider solutions, I'd say that's debatable. You might be fine with <insert cloud provider here>'s PaaS spin-up services for Kubernetes. The instant you want to span multiple cloud providers, you'll rub up against all the minor differences between each of their implementations, and I think that's where the value in SaltStack/Ansible/Chef/Puppet is in modern times. Manually orchestrate your infrastructure once, then deploy it to any cloud provider.
Great. We can now salt food, salt passwords, configure things using Salt(Stack), and now also use saltpack as a messaging format. Can we stop overloading the term "salt"? Makes it ridiculous to search for things on Google.
The difference is that I can put together components of Kubernetes that actually work. Sorry to be inflammatory, but I've been working on the bleeding edge of Swarm and it simply doesn't deliver what's promised (ex: flaky management of iptables, missing idioms/abstractions, etc.).
Single-host Docker in production, yeah that's not terribly complex, but the new price of admission for production is a complete orchestration layer, and there is 0% chance I consider taking a Swarm cluster to production any time soon. And that's to say nothing of the DDC disaster...
It's an interesting dilemma in my mind. I remember reading through the SRE book about how SREs a required to have both depth and breadth. Seems like a nearly impossible target to hit IMO, so how are you supposed to simultaneously reconcile deep/broad abilities with humility when hiring for SREs?
Yep, that's my exact experience with Swarm (1.13). I want the higher-level abstractions like K8s Pods and Deployments, but I absolutely cannot wait around for Swarm to stabilize those kind of things.
I'm actually right in the middle of putting that together as well. I quickly arrived at analysis paralysis when choosing how to bootstrap Kubernetes and run it in production given the tremendous flexibility. Tons of options[1], but nearly all of them are incompletely documented. Ended up walking through Kelsey Hightower's K8s the hard way[2] repo to peel it all apart.
End result will probably look something like Terraform -> SaltStack -> Kubernetes.
One thing I've found lacking in Nginx is active health checks. I know this is a feature in Nginx Plus, but I'm curious to know if there are any elegant open source solutions for this.
If this works out, this is the final piece of the puzzle for Apple moving to ARM chips in their Macs. Windows emulation is too big of a feature to leave out. Then again, who knows with Apple of late. Either way, very interesting news!
Absolutely – as someone looking to enter the container orchestration space, I have been spending time evaluating Docker Swarm (1.12) and Kubernetes. While consensus seems to be that Swarm is immature and "productionability" is questionable, Docker's documentation, while by no means perfect, was by far more approachable than whatever Kubernetes has thrown together.
Perhaps that comes as consequence of Docker shooting for the all-built-in approach, but I'd like to see a better overview and ramp-up in the Kubernetes space – their "101" and "201" docs are laughable.
My title is DevOps Engineer and I still don't know what the hell that actually means – but who cares, I was hired to bring a new mindset, not a new toolset, to the development team I sit with. You're right, there's lots of devs here that don't know how to deploy code well or what configuration management is, but part of my job is spreading awareness and continually asking the question: how can we do this better. That is the spirit of DevOps, and that will never die.