Book Image

Hands-On Kubernetes on Azure - Second Edition

By : Nills Franssens, Shivakumar Gopalakrishnan, Gunther Lenz
Book Image

Hands-On Kubernetes on Azure - Second Edition

By: Nills Franssens, Shivakumar Gopalakrishnan, Gunther Lenz

Overview of this book

From managing versioning efficiently to improving security and portability, technologies such as Kubernetes and Docker have greatly helped cloud deployments and application development. Starting with an introduction to Docker, Kubernetes, and Azure Kubernetes Service (AKS), this book will guide you through deploying an AKS cluster in different ways. You’ll then explore the Azure portal by deploying a sample guestbook application on AKS and installing complex Kubernetes apps using Helm. With the help of real-world examples, you'll also get to grips with scaling your application and cluster. As you advance, you'll understand how to overcome common challenges in AKS and secure your application with HTTPS and Azure AD (Active Directory). Finally, you’ll explore serverless functions such as HTTP triggered Azure functions and queue triggered functions. By the end of this Kubernetes book, you’ll be well-versed with the fundamentals of Azure Kubernetes Service and be able to deploy containerized workloads on Microsoft Azure with minimal management overhead.
Table of Contents (16 chapters)
1
Section 1: The Basics
4
Section 2: Deploying on AKS
10
Section 3: Leveraging advanced Azure PaaS services
15
Index

Authentication versus authorization

Authentication (AuthN) is very often mixed up with authorization (AuthZ). Authentication deals with identity (who are you?) and, in general, requires a trusted identity provider. Multiple providers exist, such as Azure AD, Okta, or GitHub, and even social media platforms such as Facebook, Google, or Twitter can be used as a provider. Authorization deals with permissions (what are you trying to do?) and is very implementation-specific in terms of what application resources need to be protected.

It generally takes multiple attempts to understand the difference, and even then you can still get confused between the two. The source of confusion is that in some cases, the authentication provider and the authorization provider are the same. For instance, in our WordPress example, WordPress provides the authentication (it has the username and password) and authorization (it stores the users under admin or user roles, for example).

However, in most...