Skip to main content

Basic Deployment - Details

← Back to Basic Deployment Tutorial

This document provides comprehensive information about the resources created by the Platform Application Operator and how to verify your deployment.

What Gets Created​

When you apply this Platform Application manifest, the Platform Application Operator creates many resources automatically to provide production-ready defaults:

Core Resources​

  • Deployment: Manages the pods running your container (default: 2 replicas)
  • Service: Exposes your application within the cluster (ClusterIP)

Additional Services​

  • Service (stable): For progressive rollout traffic splitting
  • Service (canary): For progressive rollout traffic splitting
  • Gateway: Gateway API resource for future ingress enablement

Autoscaling & Resilience Resources​

  • HorizontalPodAutoscaler (HPA): Automatically scales between 2-10 replicas based on CPU (target: 80%)
  • VerticalPodAutoscaler (VPA): Recommends and adjusts resource requests/limits
  • PodDisruptionBudget (PDB): Ensures availability during voluntary disruptions

Security & Networking​

  • WorkloadIdentity: Cloud IAM identity for the workload (Azure Managed Identity or AWS IRSA)
  • NetworkPolicy: Controls pod-level network traffic
  • PeerAuthentication: Configures mTLS for service mesh
  • AuthorizationPolicy: Istio security policies

Note: Even without enabling ingress, the platform creates these resources to provide production-ready defaults including autoscaling, progressive delivery support, and security hardening.

Understanding the Spec​

Default Autoscaling​

Even though you didn't specify autoscaling configuration, the platform automatically creates:

HorizontalPodAutoscaler (HPA):

  • Min replicas: 2
  • Max replicas: 10
  • Target: 80% CPU utilization

This means your application will:

  • Always run at least 2 pods for high availability
  • Automatically scale up to 10 pods under load
  • Scale down when traffic decreases

To customize autoscaling, see the autoscaling examples in advanced documentation.

For more information check out the Kubernetes documentation on Horizontal Pod Autoscaling.

spec.deployment.ports​

ports:
  - port: 8080
    protocol: http
  - port: 8443
    protocol: https

Defines which ports the container exposes. The platform creates a Service with these ports.

For more information check out the Kubernetes documentation on Services.

spec.deployment.readinessProbe​

readinessProbe:
  port: 8080
  path: /

Kubernetes uses this to determine when the container is ready to receive traffic. The platform automatically configures appropriate health checks.

For more information check out the Kubernetes documentation on Probes.

Kubernetes Core Concepts​

Tools & CLI​