📄
Spinnaker
  • Home
  • Introduction
    • Spinnaker
    • Kubernetes Concept
    • First deployment
  • Pipeline
    • Basics
    • Configuration
    • Highlander deployment
  • Blue/Green Deployment
    • Concepts
    • Built-in Strategy
    • Rollback pipeline
    • Merge pipelines
Powered by GitBook
On this page
  • Manifests
  • Kubernetes Objects used in this hands-on
  • Anatomie of kubernetes external request

Was this helpful?

  1. Introduction

Kubernetes Concept

basics building block on kubernetes of today's workshop

Manifests

You can define kubernetes objects in a manifest file format based on yaml standard. As you can see in the example below.

Example:

apiVersion: v1
kind: Service
metadata:
  # Name of the service
  name: wonderfulapp-service
spec:
  # Route traffic to any Pods matching these labels
  selector:
    app: wonderfulapp
    environment: dev
  ports:
    # publish TCP port 80, and expect pods to be listening on the same port
    - protocol: TCP
      port: 80

Kubernetes Objects used in this hands-on

Kind

Definition

Group

Version

API

A pod is the basic execution unit of a Kubernetes application.

apps

v1

workload

A ReplicaSet maintain a stable set of replica pods running

apps

v1

workload

define desired state for pods & replicaset

core

v1

workload

An abstract way to expose and loadbalance an application running on a set of pods

core

v1

service api

An API object that manages external access to the services in a cluster, typically HTTP

networking.k8s.io

v1beta1

service api

Anatomie of kubernetes external request

PreviousSpinnakerNextFirst deployment

Last updated 5 years ago

Was this helpful?

Pods
ReplicaSet
Deployment
Services
Ingress