How to run a cluster in single Docker container using kind. Source: Starting local Kubernetes using kind and Docker
Virtueller Kaffee und Themen rund um Virtualisierung, VMware, Citrix, Microsoft, OpenSource und andere Clouds, Docker und Wolken…
How to run a cluster in single Docker container using kind. Source: Starting local Kubernetes using kind and Docker
I wrote about setting up password-less phone sign-in authentication with Microsoft Authenticator and Azure AD recently which is a great option in Public Preview right now that everyone should be testing. Many of the companies I work with use Azure AD Connect to federate Azure AD with AD FS for Office 365 and other SaaS…
With new Declarative Config and DB-less deployment capabilities, Kong 1.1 is one of our most transformative releases to date. Source: Kong 1.1 – Declarative Config and DB-less deployment capabilities
Learn how to get your Kubernetes environment up and running on MacOS and spin up an image in a container with this tutorial. Source: How to set up your first Kubernetes environment on MacOS – Red Hat Developer Blog
In this part of our series on Kubernetes, we’ll look at how to get multiple containers running in order to put together an entire system. Source: Introduction to Kubernetes: From container to containers – Red Hat Developer Blog
Get a basic understanding of containers and images, so you can start using them successfully in a production environment. Source: Containers, Kubernetes, and microservices: Start here – Red Hat Developer Blog
Cloud computing, containerization, and container orchestration are the most important trends in DevOps… Source: Key Kubernetes Concepts
Source: Infrastrukturweite Verschlüsselung ist die letzte Feste der IT-Security
Public-Cloud Dienste sind easy – Transparenz eher nicht Endlich möchte ich mal wieder einen neuen Artikel vorstellen. Auf Grund der Anfragen und Diskussionen der letzten Wochen… Source: Public-Cloud nutzen – Kosten/Compliance transparent machen
Password-less phone-sign with Microsoft Authenticator is very different from traditional Azure MFA I’ve written many guides on over the years. Traditional Azure MFA (in all it’s many deployment models) required a user to know their password and once they entered it, they would get a push notification, time-based one-time password (TOTP), phone call, SMS, etc.…