This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
This architectural flaw allows attackers to easily map backend IP addresses and exploit them, often bypassing security layers entirely. While mTLS offers the most secure option, it requires custom tooling and is not yet supported by all loadbalancers. An article by Imperva from 2015 (!!!)
For now, though, I have a small collection of articles and links for your reading pleasure—not as many as I usually include in a Technology Short Take, but better than nothing at all (I hope!). Baptiste Collard has a post on Kubernetes controllers for AWS loadbalancers. Networking.
Here’s a quick look at using Envoy as a loadbalancer in Kubernetes. Having recently needed to dig into Open Policy Agent (OPA) , I took renewed interest in this slightly older article by Chip Zoller that compares OPA/Gatekeeper with Kyverno. I hope this collection of links has something useful for you! Networking.
I have a few more links than normal this time around, although I didn’t find articles in a couple categories. Don’t worry—I’ll keep my eyes peeled and my RSS reader ready to pull in new articles in those categories for next time. Nick Schmidt talks about using GitOps with the NSX Advanced LoadBalancer.
A specific angle I want to address here is that of infrastructure automation ; that is, the dynamic manipulation of physical resources (virtualized or not) such as I/O, networking, loadbalancing, and storage connections - Sometimes referred to as "Infrastructure 2.0". a Fabric), and network switches, loadbalancers, etc.
According to Martin, the term SDN originally referred to a change in the network architecture to include a) decoupling the distribution model of the control plane from the data plane; and b) generalized rather than fixed function forwarding hardware. What about virtualized loadbalancers? What about NX-OS, JUNOS, or EOS?
Once again this comes back to Intel’s rack-scale architecture work.) A traditional SRF architecture can be replicated with COTS hardware using multi-queue NICs and multi-core/multi-socket CPUs. Workloads are scheduled across these server/linecards using Valiant LoadBalancing (VLB). Gbps/watt versus 0.37
Mirantis published an article discussing a framework they built for bare-metal provisioning with OpenStack that allows OpenStack to place workloads onto bare-metal nodes instead of onto a hypervisor. I don’t have anything for this area this time around, but I’ll stay alert for articles to add next time. Servers/Hardware.
Recep talks about how the predominant architecture for network virtualization involves the use of overlay networks created and managed at the edge by virtual switches in the hypervisors. Some of these services naturally should run on the top-of-rack (ToR) switch, like loadbalancing or security services. So how does this work?
I never found the root cause, but we did find a workaround; however, along the way, someone shared this article with me. This is an interesting deep dive into Intel’s “Ice Lake” Xeon SP architecture. A bunch of home Wi-Fi routers are suspectible to attack; see this article for more details. Servers/Hardware.
Christopher Davis has an article discussing a recommended VPC subnet configuration. This is, of course, just one way of handling subnets within a VPC, but some of the principles outlined in Christopher’s article are definitely sound. This article is pretty high-level; I wish it had a bit more depth to it. Networking.
Welcome to Technology Short Take #25, my irregularly-published collection of links, articles, thoughts, and rants. This is an awesome overview of the OpenStack Folsom architecture , courtesy of Ken Pepple. According to this article by Rick Vanover, this feature allows you to protect your network against rogue/unauthorized DHCP servers.
Using 1 GbE would have required too many ports, too many cables, and too many switches; 10 GbE offered Expedient a 23% reduction in cables and ports, a 14% reduction in infrastructure costs, and offered a significant bandwidth improvement (compared to the previous 1 GbE architecture). This article was originally posted on blog.scottlowe.org.
Here’s a quick look at using Envoy as a loadbalancer in Kubernetes. Having recently needed to dig into Open Policy Agent (OPA) , I took renewed interest in this slightly older article by Chip Zoller that compares OPA/Gatekeeper with Kyverno. I hope this collection of links has something useful for you! Networking.
In this article, we will explore the top machine learning deployment tools and platforms that can help organizations streamline their deployment process, improve model performance, and achieve their business goals. Model published as data architecture, where the model is deployed as a file or a set of files and accessed through a data store.
Before I present this episode’s collection of links, articles, and thoughts on various data center technologies, allow me to first wish all of my readers a very merry and very festive holiday season. Mustafa Akin has an article on Docker’s new overlay networking functionality. Now, on to the content! Networking. This looks handy.
It looks like there will be a follow-up to this article as well, so you may want to check back on Ajay’s site. Bernd Malmqvist talks about Avi Networks’ software-defined loadbalancing solution, including providing an overview of how to use Vagrant to test it yourself. Cloud Computing/Cloud Management.
I never found the root cause, but we did find a workaround; however, along the way, someone shared this article with me. This is an interesting deep dive into Intel’s “Ice Lake” Xeon SP architecture. A bunch of home Wi-Fi routers are suspectible to attack; see this article for more details. Servers/Hardware.
Here’s a fresh new collection of links and articles from the around the web to propel myself back into blogging. These two articles are interesting (to me) because they combine both network automation and Kubernetes. David Holder walks through removing unused loadbalancer IP allocations in NSX-T when used with PKS.
Our platform is built on a sophisticated microservices architecture that consists of several distinct microservices which handle various features and functionality to deliver mission-critical solutions to our end users. Overcoming these challenges necessitates not only creative thinking but also practical solutions.
Whatever DNS name you supply for controlPlaneEndpoint —and it should be a DNS name and not an IP address, since in an HA configuration this value should point to a loadbalancer, and IP addresses assigned to AWS ELBs can change–will also be added as a Subject Alternative Name (SAN) to the API server’s certificate.
Note that even though fleet helps with scheduling containers across a cluster of systems, fleet doesn’t address some of the other significant challenges that arise from an architecture based on distributed micro-services in containers. However, the basic architecture I’ve shown you here can be extended.
This article discusses how gen AI is driving innovation in low-code software development, with regards to the technological aspects and implications. However, these platforms still require decision-making on architecture, logic, and workflow orchestration.
N-Tier architectures and micro-services applications must be tuned for performance. High speed low latency networks now allow us to add these nodes anywhere in a cloud infrastructure and configure them under existing loadbalancers. So the question is now not whether to deploy, but when, where, why and how?
With a well-planned deployment, and a good infrastructure, companies can efficiently load-balance their IT environment between multiple active, cloud-based, sites. So, if one site should go down – users would transparently be balanced to the next nearest or most available data center. . Featured Cloud Articles.
We organize all of the trending information in your field so you don't have to. Join 83,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content