404 Not Found
  • Introduction
  • Monitoring related
    • K8s cluster monitoring
    • Monitor Jenkins with G.A.P on K8s cluster
    • Monitoring tools | projects
      • Grafana
      • AlertManager
      • Prometheus
      • Wavefront
  • Logging related
    • BOSH logs
    • How to gather systemd log
    • K8s cluster logging
    • Logging tools | projects
      • vRealize Log Insight
      • Fluentd
      • syslog vs fluentd
  • Having fun with docker
    • Using docker-compose for redmine
    • Customize Fluentd docker image
  • K8S or Apache Mesos
  • K8S Related
    • Main Architecture
      • Master components
        • API Server
        • etcd
        • Controller Manager
        • Kube Scheduler
      • Worker components
        • kubelet
        • kube-proxy
    • K8S Storage
      • Volume Provisioning
      • Understand CSI
      • How to write CSI
      • VMware CNS
      • K8S storage e2e experiment under VMware vSphere
      • Experiment on Persistent Volume Access Mode
      • Design: Storage in Cluster-API architecture
    • K8S Networking
      • Ingress
      • Endpoints
    • K8S Policies
      • Resource Quotas
    • K8S Management Platform
    • K8S Tests Tool
    • K8S Extension
      • CRDs
        • Custom Resources
        • Custom Controllers
        • How to user code-generator
        • K8S Operators
        • Operators Development Tools
          • Kubebuilder
          • Metacontroller
          • Operator SDK
      • Custom API Server
    • K8S Resource CRUD Workflow
    • K8S Garbage Collection
  • K8S CONTROLLER RELATED
    • IsController: true
    • Controller clients
  • PKS RELATED
    • How to Access VMs and Databases related to PKS
    • PKS Basics
    • BOSH Director
    • Backup and Restore on Ent. PKS with Velero
  • CICD RELATED
    • Configure Jenkins to run on K8S
    • Customize Jenkins JNLP slave image
    • Jenkins global shared libs
  • Google Anthos
    • Google Anthos Day from KubeCon 2019 San Diego
    • Migrate for Anthos
    • Config Connector
  • SYSTEM DESIGN RELATED
    • Design Data Intensive Application - Notes
      • RSM
        • Reliability
        • Scalability
      • Data models and Query Languages
      • Storage and Retrieval
    • How Alibaba Ensure K8S Performance At Large Scale
  • Miscellaneous
    • Knative
    • Serverless
    • Service Mesh
    • gRPC
    • Local persistent volumes
    • ownerReferences in K8S
    • File(NAS) vs Block(SAN) vs Object storage
    • KubeVirt
    • Why K8S HA chooses 3 instead of 5..6..7 as the size of masters?
    • goroutine & go channel
    • How to make docker images smaller
Powered by GitBook
On this page
  • Introduction
  • Architecture
  • Terminology

Was this helpful?

  1. PKS RELATED

PKS Basics

PreviousHow to Access VMs and Databases related to PKSNextBOSH Director

Last updated 5 years ago

Was this helpful?

Introduction

Pivotal Container Service (PKS) enables operators to provision, operate, and manage enterprise-grade Kubernetes clusters using BOSH and Pivotal Ops Manager.

Architecture

Terminology

PKS: Pivotal Container Service (PKS) enables operators to provision, operate, and manage enterprise-grade Kubernetes clusters using BOSH and Pivotal Ops Manager.

What CFCR are providing:

  • Deploying Solutions:

    CFCR offers the following solutions to improve the experience of deploying Kubernetes clusters:

    • Repeatability and consistency when deploying “Kubernetes-as-a-service” within an organization

    • A single control plane to provision and manage Kubernetes services

  • Managing Solutions:

    CFCR offers the following solutions to improve the experience of managing Kubernetes clusters:

    • High-availability and multi-AZ support: BOSH can deploy multiple master/etcd/worker nodes across multiple availability zones, and monitor their health.

    • Scaling: BOSH allows the operator to scale the number of instances in the cluster up and down by modifying the manifest.

    • VM healing: BOSH continuously monitors the health of all VM instances and recreates VMs. Self-healing VMs and monitoring via BOSH.

    • Upgrades: BOSH manages the rolling upgrade process for a fleet of Kubernetes clusters.

On-Demand Services SDK and the On-Demand Broker:

  • The on-demand services SDK: provides a generic on-demand broker (ODB) that answers API calls from the Cloud Controller.

  • Service authors: add service-specific functionality to the on-demand services SDK through an executable called a Service Adapter. These components combine to create a BOSH deployment.

  • Tile authors customize the tile interface used by operators. The tile consumes the BOSH deployment to generate a BOSH manifest for deploying on-demand instances of the service

References:

BOSH: an open-source tool for release engineering, deployment, lifecycle management, and monitoring of distributed systems

BOSH Release: A release is a versioned collection of configuration properties, configuration templates, start up scripts, source code, binary artifacts, and anything else required to build and deploy software in a reproducible way. Release could be a Git repo or a single tarball

BOSH Development: A deployment is a collection of VMs, built from a stemcell, that has been populated with specific releases and disks that keep persistent data. These resources are created in the IaaS based on a deployment manifest and managed by the Director, a centralized management server.

BOSH Stemcell: A stemcell is a versioned Operating System image wrapped with IaaS specific packaging.

CFCR: a BOSH release that offers a uniform way to instantiate, deploy, and manage highly available Kubernetes clusters on a cloud platform using BOSH.

Official PKS website:

PKS documentation:

https://bosh.io/docs/
https://bosh.io/docs/release/
https://bosh.io/docs/deployment/
https://bosh.io/docs/stemcell/
https://docs-cfcr.cfapps.io/
https://pivotal.io/platform/pivotal-container-service
https://docs.pivotal.io/runtimes/pks/1-4/index.html