Ever since I joined Microsoft (Sept 2019) and started working in the Azure Technical Trainer team, I deployed a demo Azure Kubernetes Service (AKS) with a few sample containers. Helping me in walking training attendees through the architecture, the management concepts and what it takes to run containerized workloads using the advanced capabilities coming with Kubernetes on Azure.
Knowing this AKS cluster got deployed about 20 months back, it also meant my setup was getting a little bit out-of-date. Interesting enough, it ran for almost 500 days (I considered waiting to publish this article to celebrate its anniversaryā¦)
Hey everyone,
Thanks for joining the Azure Spring Clean online event again, in which the Azure community steps up once more, sharing the best tips & tricks on how to keep your Azure environments clean. Discussing optimizations, covering new services and features or overall giving you a view on how to manage your Azure subscriptions even better.
You can check out all other blog posts or videos, which can guide you with best practices, lessons learned, or help you with some of the more difficult Azure Management topics at Azure Spring Clean.
Hi all,
Iāve deployed me an AKS - Azure Kubernetes Service environment that I use in my Azure training class deliveries almost every week (yes, every AZ-course touches on AKS and Containersā¦)
The Problem My AKS environment was running fine all this time (a bit over a year), allowing me to rely on existing deployed Kubernetes services, as well as building new services as a live demo. Until this morning, where all of a sudden, my own services didnāt start at all, but the kube-system services did. The error message I noticed for this service was ImagePullBackOff and ErrImagePull.
Hi all,
This is one of the nail biting challenges of our industry, failing in running a straight-forward task. Especially when it is failingā¦
What happened? I was creating a pipeline in Azure DevOps to deploy an ARM template for VM setups with VM Extensions. To prep this deployment, the artifacts (DSC scripts) should be copied to Azure Blob Storage, in order for the Azure DevOps build agent to āfindā it. Easy-peasy, there is a predefined task for that, called Azure Blob File Copy
Hey there,
Iāve been doing quite a lot with Docker and the different Azure Container Services offerings like Azure Container Instance and Azure Kubernetes Services.
As you probably know, the starting point of a containerized application is the Dockerfile. Look at this like an instruction script, which tells Docker what needs to happen, in order to grab the application source code, compile it and produce the container image.
Besides the complexity of running containers by itself, I personally think writing a Dockerfile is equally difficult and complex. So I am more than happy to know that Visual Studio (2017 and 2019) comes with some interesting Container Tools. Aside from helping in debugging containerized workloads, providing some interaction with the Docker engine, it also helps in compiling a Dockerfile for you.
Today, Nov 10th, was the official date of the long-announced ādotnet5 Frameworkā, and it is described as a major release. Still being new in the developer world myself, I know the basics of ASP.NET 3.7 and 4.5, so I can imagine jumping to a 5.0 release is indeed a big thing.
.NET 5.0 improvements The biggest improvements announced by the Product Team are:
Migration-friendly for older .NET versions Production-ready from day 1 of release (thorough-tested for http://www.dot.net and http://www.bing.com websites) Enhanced performance ClickOnce client app publishing Smaller container image footprint Supportability for Windows Arm64 and WebAssembly (Blazor) Support will go into Feb 2022, which seems the release date for DotNet 6.0 LTS
Hey everyone,
Wow, itās September already! Where has summer been? And honestly, where has the (nice) year been? Most of you, just like myself, are probably still working from home, and I guess the same are your kids.
Where September used to feel like a fresh start (remember that smell of your new school outfit, the new school equipment, fresh-sharpened pencils, the excitement of learning new things, meeting new class mates,ā¦ almost seems like I want to go back to school myself.
Hi all,
Earlier this week, I got blown away by an interesting Terraform issue.
The Problem Running a deployment that ran fine for months. I initiated a new deployment using the usual āterraform initā step, which ran fine. Followed by the usual āterraform planā, and BOOM, the following message appeared:
Panic: not a collection type
Since this was a new template I created, I assumed an issue with the syntax or anything similar. As I couldnāt find anything, I tried running the same steps with a āvalidā template. Only to find out it produced the same error message.
Hey,
As some of you know me for years already, you also know IĆ¢ā¬ā¢m rather bad in coding (although Iām learning Blazor since a few weeks, but more on that journey in future postsā¦), and always Ć¢ā¬Ågot scaredĆ¢ā¬Ā about DevOps. Especially the Dev part in the word Ć°ÅøĖÅ . I still remember being in Bangalore, India early 2016 to deliver an Azure workshop to Microsoft GSI Partners (Wipro, Tech Mahindra, Accenture,ā¦) as a freelance trainer together with Microsoft AzureCAT engineers. While my sessions were totally in my Azure comfort zone (Networking, Storage, Azure Active Directory), I also learned a lot from the Azure App sessions my colleagues delivered. But then all of a sudden, I had to jump in on Wednesday afternoon, taking over the Ć¢ā¬ÅDevOps practicesĆ¢ā¬Ā session due to some urgent facts. Oh man, down went my comfort level. Me, the guy they saw earlier in the week, delivering Azure Infra sessions with ease, now needing to talk about DevOps, something I didnĆ¢ā¬ā¢t know at all? I hardly used Visual Studio at that time, let alone I could talk about this process.
As most of you know, I enjoy writing technical (Azure related) books, but every now and then I am not writing myself, but rather do technical reviewing. A few weeks ago, I was approached by Packt, asking me to review their Azure for Architects - third edition
Donāt let the reference to āthird editionā fool you, there has been a massive rewrite of several chapters, with fresh new content, more technical information and new chapters were added as well.
Cookie Consent
We use cookies to enhance your browsing experience and analyze site traffic.
Cookie Preferences
These cookies are required for the website to function and cannot be disabled.
These cookies help us understand how visitors interact with our website.
These cookies enable features like comments and embedded content.