►
From YouTube: PaaS on Kubernetes: Journey of Making Cloud Foundry Kubernetes Native - Sakala Venkata Krishna Rohit
Description
Don't miss KubeCon + CloudNativeCon 2020 events in Amsterdam March 30 - April 2, Shanghai July 28-30 and Boston November 17-20! The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects - Learn more at https://kubecon.io
PaaS on Kubernetes : Journey of Making Cloud Foundry Kubernetes Native - Sakala Venkata Krishna Rohit, SUSE
The two technologies for deploying cloud native apps are Kubernetes and Cloud Foundry. Cloud Foundry uses BOSH and Gardner for managing infrastructure and container orchestration. Project KubeCF is a set of Kube Operators which enables Cloud Foundry to use Kube instead. These operators provide you the following features : QuarksStatefulSet Operator - B/G Canary Active/Passive Deployments, Volume Management, AZ Suppor QuarksJob Operator - Errands, Persisted Output, Versioned Secrets QuarksSecret Operator - Auto Generate Pass., Keys, Certificates, Secret Rotation QuarksBoshDeployment Operator - Convert CF BOSH release manifests into Kube. Project KubeCF combines all these operators and brings features of a PaaS offering on top of Kube. In this session, I will also demo KubeCF showing how easy it is to do complete lifecycle management of an application using simple CF commands on kube.
https://sched.co/YWJW
A
Hello,
everyone
welcome
to
my
presentation
pass
onto
Benitez
journey
of
making
cloud
foundry,
Cube
native
myself,
I'm
Robert
and
I
work
as
a
software
engineer
at
Susi,
so
firstly,
I'll
be
talking
about
cloud
foundry
and
about
its
components
and
then
I'll
be
covering
about
bosh,
which
is
used
to
deploy
the
cloud
foundry
components
on
top
of
virtual
machines.
Later
I'll
be
talking
about
operators
that
we
have
created,
there
is
quark
stateful,
sweat,
quark,
secret
and
quarks
job.
These
operators
are
used
for
deploying
cloud
foundry
components
on
top
of
kubernetes.
A
A
For
those
of
you
who
don't
know
what
is
cloud
for
Andrea,
it
is
an
open
source
platform
as
a
service
offering
from
the
cloud
foundry
foundation
in
a
platform
as
a
service
offering
you
only
manage
your
data
and
logic
of
your
application.
The
rest
of
the
aspects
are
taken
care
by
the
software
that
is
cloud
foundry.
A
In
this
example,
another
example
of
a
path
offering
is
Haruko,
whereas
in
a
nice
offering
you
manage
your
runtime
load,
balancing
authentication
until
the
OS
layer,
so
a
classic
example
would
be
AWS,
Google
Cloud
and
in
an
on-prem
that
is
traditional
ID.
You
manage
everything
from
top
to
bottom,
that
is
you're
not
in
cloud.
A
So,
where
does
not
run
in
Cuban?
It
is
related.
Both
are
used
for
deploying
cloud
native
applications.
There
is
micro
service
architecture,
but
Cuban,
it
is,
is
more
of
a
cash
offering
as
a
container
as
a
service
offering
it
doesn't
care,
take
care
of
building
and
management
of
your
application.
You
need
to
create
service
deployment,
we
Hamel
files,
port
files,
etc,
whereas
in
Cloud,
Foundry,
building
and
management
of
your
application
is
taken
care
of
both
do
not
support
function.
A
A
Let's
get
a
bit
deep
into
cloud
for
Andrea.
What
is
Cloud
Foundry?
It
is
made
up
of
many
components
which
take
care
of
your
application.
Each
component
has
a
specific
role
in
managing
your
application.
For
example,
there's
a
component
called
router,
which
routes
the
request
received
to
the
specific
app
instance
and
then
building
deploying
a
life
cycle
and
life
cycle
management
and
also
scaling
and
self-healing,
are
all
managed
by
Cloud,
Controller
and
Diago
component
logs
and
metrics
from
your
abs
are
collected
through
log
aggregated
component
and
UA
handles
your
authentication
and
authorization.
A
That
is,
you
can
connect
to
LDAP
to
your
company
company's
user
directory
and
finally,
service
brokers,
which
are
used
to
connect
your
databases
and
external
software
solutions.
Software,
the
service
solutions,
soft
service
brokers
are
needed
here
because
you
can
only
run
stateless
applications
on
top
of
Cloud
Foundry.
So
if
you
want
to
connect
your
data,
you
need
to
use
service
broker
and
then
connect
to
the
database.
A
So
the
summary
here
is
that
Cloud
Foundry
is
a
pass
software
and
is
made
up
of
many
components
which
take
care
of
managing
your
application
as
a
software,
and
it
needs
to
be
highly
available
because
and
it
should
recover
in
the
in
a
case
of
failure,
it
should
have
monitoring.
It
should
have
zero
time
updates
because
for
all
of
your
application,
Cloud
Foundry-
that
is
the
path
software
is
the
crux.
This
is
where
Bosch
comes
into
the
picture.
A
It
is
used
to
deploy
Cloud
Foundry
components
on
top
of
virtual
machines,
and
it
has
all
the
necessary
features
to
be
highly
available,
so
you
can
think
of
Bosch
as
a
Cuban.
It
is
of
VMs,
ok,
so
your
apps
on
top
of
virtual
machines.
So
this
was
about
route
for
Andrea
and
Bosch.
So
what
is
our
goal?
We
at
suzay,
along
with
IBM
and
SAP
under
the
Cloud
Foundry
foundation,
want
to
move
away
from
virtual
machines
to
containers,
so
all
the
components
on
the
left
side
that
you
can
see
router
you
ad
ago.
A
These
are
the
components
of
Cloud
Foundry
traditionally
deployed
on
virtual
machines,
so
we
we
want
to
continuous
and
deploy
a
sports
in
cuban.
It
is
notes
other
than
another.
Interesting
thing
here
is
that
whatever
apps
you
deploy
using
cloud
foundering
well,
it
will
be,
will
also
be
deployed
as
parts
in
Cuban.
It
is
stateful
said
in
particular,
so
our
solution
was
to
replace
Bosch
with
a
set
of
operators.
A
Let's
just
the
basics
of
operator
operator
is
the
most
I
feel
like
it's
most
flexible
feature
of
kubernetes,
which
is
allowing
everyone
to
build
customized
solutions
on
top
of
it.
That
is
building
platforms
on
top
of
for
platform.
That
is
cube
and
it
is
and
I
guess
it
is
one
of
the
reasons
everyone
is
erupting
cube.
Now.
What
is
an
operator?
An
operator
is
a
collection
of
the
resource
and
a
controller.
A
There
are
many
predefined
resources
in
Thuban.
It
is
such
as
for
deployment
and
replica
set,
etc.
An
amazing
feature
of
Cuba
notice
is
that
it
allows
you
to
define
CR
DS,
that
is
customer
resource
definition,
which
allows
you
to
define
your
own
custom
resource.
So
we
have
created
our
own
custom
resource
named
Kwok,
stateful,
quacks,
Rob
and
quacks
secret
and
the
related
controllers
to
next
up
what
is
a
controller
for
each
resource?
There
is
a
controller
which
takes
care
of
it.
A
For
example,
we
create
a
replica
set
resource
using
cube,
cuddle,
create
with
the
replica
count
2,
then
the
replica
set
controller
will
capture
this
create
event
and
then
create
two
ports.
So
a
basically
a
controller
runs
in
a
loop
to
match
the
current
state
in
the
cluster
with
the
desired
state.
That
is
your
Yama
files.
Okay.
So
this
was
the
basics
about
operator.
A
Now,
as
I
said,
our
goal
was
to
replace
bosh
with
operators
and
we
had
to
replicate
all
the
features
of
borsch.
So
we
divided
the
features
of
borsch
into
three
sets
and
developed
in
an
operator
for
each
set.
Each
operator
is
an
extent
extension
of
a
particular
resource
in
cuban
artists
and
and
has
some
additional
features.
I
will
be
touching
upon
the
additional
features
of
each
operator.
Now.
A
The
first
one
is
quarks
job.
It
is
an
extension
of
the
cuban
Etta's
job
resource.
The
additional
features
here
are
that
we
support
errands
and
storage
of
the
output
of
a
job
pod
in
a
secret.
Iran's
are
basically
one-time
tasks
which
developer
can
run
anytime.
As
you
can
see
in
the
image
it
has
two
extra
fields
trigger
and
an
output
and
the
rest
of
it
as
a
job
template.
Let's
equip
them
of
this.
A
A
So
this
is
a
very
simple
operator,
just
an
additional
feature
to
run
errands
there's
another
operator,
quoc
secret.
It
is
also
a
simple
operator
which
is
used
to
generate
passwords
certificates
and
keys
and
saves
it
as
secret.
It
also
supports
rotation
of
these
secrets.
You
can
see
there's
a
type
field
in
the
spec
and
I've
written
it
as
password.
That
means
I'm
asking
the
operator
to
generate
a
password
and
with
this
store
it
in
a
secret
name,
jens
secret.
One.
A
A
A
A
A
A
Next
squawk
straight
full
set,
it
is
also
an
extension
of
the
straight
full
set
resource
in
Cuba
notice.
The
additional
features
are
that
it
supports
a
hazy
support.
That
is
basically,
it
creates
a
straight
full
set
in
each
of
the
availability
zone.
The
next
one
is
active
passive
deployment,
which
means,
if
they're
three
replicas,
then
one
replica
would
be
active
and
other
are
passive
and
in
half,
if
an
active
part
fails.
One
of
the
passive
parts
is
made
of
made
active
and
canary
updates.
Canary
updates
are
good
because
you
can
recover
from
an
update
failure.
A
A
A
A
A
A
Okay,
so
since
this
is
a
path
offering
Cloud
Foundry,
you
don't
you
know,
you
do
not
create
any
role
based
access
users,
that
is
cluster
admin
or
anything.
You
have
an
inbuilt
pre
hierarchy,
structure,
aaaghh
spaces
and
users
organization.
You
can
see
organization
as
your
company
and
then
inside
there's
a
team
that
is
space
and
then
user
would
be
the
team
member
and
you
can
allocate
quota
for
each
at
each
level
so
that
they
don't
overuse
the
resources.
A
Right,
so
in
a
past
offering
I
already
told
you
that
you
don't
need
not
take
care
of
your,
you
need
not
take
care
of
building
and
managing
your
application.
You,
the
only
thing
you
need
to
take
care
is
the
business
logic
where
the
code
about
the
code
so
I
have
a
simple
Python.
Flask
application
I
go
into
the
directory
and
execute
one
single
command
that
is
before
that
I
write
a
basic,
manifest
file.
This
is
required
for
Cloud
Foundry.
You
need
to
specify
the
number
of
instances
and
the
build
pack.
A
A
Cf
push
and
the
name
of
the
application
and
that's
a
Cloud
Foundry-
will
take
care
of
everything
else.
Now
you
will
see.
This
is
just
a
staging
thing
yep.
So
now
we,
you
have
seen
that
your
application,
Python
flask,
is
deployed
as
a
stateful
set
in
Cuba
notice
with
replicas
3.
So
you
didn't
build
your
docker
image.
You
didn't
write
any
service
file
or
deployment
ml
file.
Everything
is
taken
care
of
by
Cloud
Foundry
and
you
didn't
create
any
role
based
access.
Anything
else
out,
for
it
takes
care
of
it.
So
that's
a
pass
offering.
A
A
A
That's
what
the
github
link
is.
We'd
have
dot-com
slash,
lucid
or
cubes
here
right
now,
it's
under
Susy,
but
later
it
will
be
promoted
to
Cloud
Foundry
foundation
in
a
few
days,
and
we
are
active
on
cloud
for
any
slack
channel
is
cube,
CF
dev
yep,
that's
it
I'm
asked
not
to
take
questions
here,
but
I'm
I'll
be
off
I'll,
be
taking
questions
and
offline.
Thank
you.