When configuring Azure Kubernetes Service with Azure Container Network Interface (CNI), every pod gets an IP address of the subnet you’ve configured.
So how do you plan you address space? What factors should you consider?
Each node consumes one IP. Each pod consumes one IP. Each internal LoadBalancer Service you anticipate consumes one IP. Azure reserves 5 IP addresses within each subnet. The Max pods per node is 250. The Max pods per nodes lower limit is 10. 30 pods is the minimum per cluster. Max nodes per cluster is 1000. When a cluster is upgraded a new node is added as part of the process which requires a minimum of one additional block of IP addresses to be available. Your node count is then n + 1. When you scale a cluster an additional node is added. Your node count is then n + number-of-additional-scaled-nodes-you-anticipate + 1. With all that in mind the formula to calculate the number of IPs required for your cluster should look like this:
Microservices architectures are inherently distributed and building such solutions always bring interesting challenges to the table: resilient service invocation, distributed transactions, on-demand scaling, idempotent message processing and more.
Deploying Microservices on Kubernetes doesn’t solve these problems and Developers need to learn and use SDK’s on top of frameworks such as .NET, while building distributed Microservices architectures.
Microservices architectures are inherently distributed and building such solutions always bring interesting challenges to the table: resilient service invocation, distributed transactions, on-demand scaling, idempotent message processing and more.
Deploying Microservices on Kubernetes doesn’t solve these problems and Developers need to learn and use SDK’s on top of frameworks such as .NET, while building distributed Microservices architectures.
This morning I saw this tweet from Mr Brendan Burns:
AKS Cost Monitoring and Governance With Kubecost https://t.co/OStwIBsuPp
— brendandburns (@brendandburns) April 30, 2021 And I’m sure that once you also read through it, you’ll learn that you have to take several steps in order to achieve AKS Cost Monitoring and Governance With Kubecost.
By default Cloud Shell sessions run inside a container inside a Microsoft network separate from any resources you may have deployed in Azure. So what happens when you want to access services you have deployed inside a Virtual Network such as a private AKS cluster, a Virtual Machine or Private Endpoint enabled services?
Azure Functions provides you with an event-driven programming model and Dapr a set of essential cloud-native building blocks that you can use together to create great solutions.
Joins Carlos and create a solution that reads tweets, stores them in a database, access secrets, uses pub/sub between functions and much more!
Let’s see how Azure ARM, Terraform, Azure Service Operator for Kubernetes and other solutions compare to each other so you can choose the right weapon to win the Infrastructure as Code War!
In this workshop you’ll learn how to deploy, monitor, scale, secure and debug workloads in AKS:
Deploy an aplication. Configure monitoring and health checks for your application. Scale your application to meet demand. Enable SSL/TLS with an ingress controller. Secret Management with AKS & Keyvault. Debugging your Kubernetes application.
¿habéis visto todas las novedades del Ignite? Bueno, si no es así, estamos de enhorabuena porque nos hemos liado a la manta para contaros las novedades con el siguiente equipo:
Carlos Mendible Josue Yeray Julián Santiago Porras David Vidal Sergio Parra Sergio Hernández Alberto Diaz Victor Estival
Como cada año CATzure organiza una mesa redonda con los mejores expertos de Azure de España para conversar sobre el cloud, desarrollo y todo aquello que os aptezca.
Esta mesa redonda estuvo compuesta por:
Carlos Lande Carlos Mendible Elena Salcedo Pallo Ana Maria Bisbe Nacho Fanjul Fernando Escolar Carles Alonso
Aprende junto a Carlos que es Dapr, y como utilizar este nuevo runtime para desarrollar soluciones basadas en microservicios, entendiendo como resuleve los retos que implican las nuevas arquitecturas, tanto en cloud como en edge: resiliencia, gestión de estado, secretos, eventos, service discovery, etc…
En noviembre de 2019, algunos de los mejores desarrolladores de GitHub lanzaron la beta de GitHub Actions, la solución para CI/CD de GitHub. No tardo en popularizarse entre los mejores desarrolladores de cualquier entorno…
Si te apetece usarlo y puedes permitírtelo, mirate este video donde acompaño a Sergion Navarro Pino:
The intent of this post is to help you understand how to connect an Azure Function to a Storage Account privately so all traffic flows through a VNet therefore enhancing the security of your solutions and blobs.
The Case: # Supose you have the following Azure Function written in C# which only copies a blob from one conatiner to another:
¿Quieres conocer a un MVP desde dentro? El programa Microsoft Most Valuable Professional es un premio otorgado por Microsoft a los líderes más valiosos en las comunidades destacados como reconocimiento a su labor voluntaria en compartir sus conocimientos en la comunidad.
En este webinar con formato entrevista, Carlos Mendible, Microsoft MVP Azure & Developer Technologies, nos cuenta su trayectoria profesional, nos da sus consejos y sus puntos de vista de la situación del mercado actual.
Let’s learn how to use Dapr to build resilient, stateless and stateful microservices solutions that run on the cloud and edge solving the challenges you´ll face if you try to remove your applications SDK dependencies, port your applications (without code modifications) between clouds and implement event-driven architectures.
A common challenge when building cloud applications is how to manage the credentials in your code for authenticating to cloud services. In this session we’ll explore how to keep your credentials safe and how you can work without saving those credentials in the developers machines and therefore avoid an accidental upload to source control.
Let’s learn how to use Dapr to build resilient, stateless and stateful microservices solutions that run on the cloud and edge solving the challenges you´ll face if you try to remove your applications SDK dependencies, port your applications (without code modifications) between clouds and implement event-driven architectures.