liveBook · Manning

Policy

As explained in Google Anthos in Action

A policy is a declarative rule that specifies required behavior, configuration, or access conditions for managed resources.

A policy is a declarative rule that specifies required behavior, configuration, or access conditions for managed resources. In Kubernetes and Anthos environments, policies regulate workload access, service-mesh traffic, cluster configuration, and security-sensitive resource settings. section 4.3.3 section 13.7

Use policies to establish controls at several operational boundaries:

  • Restrict traffic between workloads or between users and workloads by request identity, protocol, and custom Istio attributes. section 4.3.3
  • Enforce secure service-to-service communication with mTLS, including workload identity, encryption, and automated key and certificate rotation. section 4.3.3 section 13.7
  • Prevent dangerous Kubernetes configurations, such as privileged containers or host namespace sharing, through Gatekeeper policy controls. section 13.4
  • Apply infrastructure and security requirements consistently across managed clusters, using selectors when a policy should target only part of the fleet. section 13.7

Restricting service-mesh access

An operator can define an Istio authorization policy that allows or denies requests according to workload identity, protocol, and other Istio attributes. Each Envoy proxy evaluates authorization locally, so traffic is controlled at the workload boundary for HTTP, HTTPS, HTTP2, gRPC, and TCP services. section 4.3.3

Figure 4.5 Istio authorization architecture
04-05

Use the architecture figure to trace how Istio authorization policies relate to the service mesh, namespaces, workloads, and Envoy enforcement points. section 4.3.3

How Google Anthos in Action covers it

How deep it goes
Explains policy purposes, enforcement locations, supported traffic types, security risks, and cluster scope, but does not show policy manifests.
Examples
Uses Istio authorization rules, ACM mTLS policies, Gatekeeper controls, and risky Kubernetes manifest fields as concrete policy cases.
What it assumes
Assumes familiarity with Kubernetes clusters, workloads, service meshes, and managed Anthos components.
What you can do after
Operate policy controls to restrict service traffic, secure cluster communication, and prevent dangerous workload configurations.
How it connects
Connects policies with Istio, Envoy, mTLS, JWT, Gatekeeper, ACM, Anthos, and Kubernetes.

Also explained in

Compare how 13 books explain policy →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Google Anthos in Action. The section links point to the parts of the book it draws on.