This week Intel released a statement regarding Microarchitectural Data Sampling (MDS), another vulnerability in the "speculative execution" feature of modern processors. This is for HyperThreading and is the feature that allows the CPU to work out what commands will be run next, if they would affect the current running command and if not, run it on the same core.
Imagine you are driving a car on a freeway. Your speedometer is telling you you’re going 62 mph. But you “gotta go fast”. Faster than then 65 mph speed limit. So you go for it: first 68mph, then 75mph, then 80mph. Then you pass a police officer hiding in a speed trap. To your dismay, they pull you over and give you a ticket. All is not lost: there is a silver lining here.
Find out why Cloudsmith thinks Puppet is one seriously classy company., why brand equity is important, and what impact a dot com has.
AKS is the managed service from Azure for Kubernetes. When you create an AKS cluster, Azure creates and operates the Kubernetes control plane for you at no cost. The only thing you do as a user is to say how many worker nodes you’d like, plus other configurations we’ll see in this post. So, with that in mind, how can you improve the AKS cluster performance of a service in which Azure pretty much manages almost everything?
Infrastructure as code is an important methodology for ensuring that your distributed systems are treated as cattle and not pets. Your Kubernetes and Rancher clusters are no different. You should be able to provision your Rancher clusters, your Kubernetes clusters, and all of your apps with automation.
Back in 2017, I wrote a post titled “3 pro tips for Developers working with Kinesis streams”, in which I explained why you should avoid hot streams with many Lambda subscribers. When you have five or more functions subscribed to a Kinesis stream you will start to notice lots of ReadProvisionedThroughputExceeded errors in CloudWatch.
Infrastructure management has come a long way. (Mostly) gone are the days of manual configurations and deployments, when using SSH in a “for” loop was a perfectly reasonable way to execute server changes. Automation is a way of life. Configuration management tools like Chef, Puppet, and Ansible — once on the bleeding edge — are now used by most enterprises.
Have you ever found yourself trying to reconstruct an event from the past only to come up blank because you cannot go so far back in time? If only you could bring back that missing piece of the puzzle! In the world of IT, logs are the way machines and software record events. They help us understand when an event happened, where they happened and most importantly, why they happened.
From legacy internet service to 5G possibilities, Spiceworks examines the evolution of telecommunications in the workplace. The internet has been a transformative force around the globe, both at home and in the workplace. Organizations rely on internet service providers (ISPs) to provide vital access to email, the World Wide Web, and cloud services that connect us. As communications and commerce increasingly take place online, there’s no question internet access is crucial to business success.
Today we are announcing the support for Windows containers with Kubernetes 1.14 in Preview mode. As many users may know, Rancher 2.1.0 supported Windows containers in experimental mode. Now that SIG Windows and Microsoft have announced the general availability of containers in Windows Server 2019 with Kubernetes 1.14, we have upgraded Rancher to both support the latest version of Windows containers (and Kubernetes) and after the preview is over, make it generally available.
