►
From YouTube: Kubernetes Cloud Provider IBM project Overv... Sahdev Zala, Richard Theis, Guang Ya Liu & Brad Topol
Description
Don’t miss out! Join us at our next event: KubeCon + CloudNativeCon Europe 2022 in Valencia, Spain from May 17-20. Learn more at https://kubecon.io The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.
Kubernetes Cloud Provider IBM project Overview and Deep Dive - Sahdev Zala & Richard Theis & Guang Ya Liu & Brad Topol, IBM
The Kubernetes IBM Cloud Provider is a subproject of Cloud Provider SIG. Lots of exciting work is going in the project such as a new repository for IBM Cloud Provider code, and kubernetes-sigs/cluster-api-provider-ibmcloud work on IBM VPC Gen 2. In this session, the project leads will provide an overview of the project and details of the ongoing work and future roadmap. This session will be of value to a broad audience including active contributors, new contributors, and anyone with an interest in the Kubernetes IBM Cloud Provider and kubernetes-sigs/cluster-api-provider-ibmcloud.
A
A
All
right,
thank
you,
brad
all
right,
so
I
will
provide
an
overview
and
you
know
the
activities
structure
of
the
project,
and
then
we
will.
You
know
straight
deep
dive
into
the
three
repositories,
the
main
reapers.
We
have
actually
it's
four
repositories,
but
the
three
main
repositories
for
cluster
api
provider
driving
cloud.
There
is
one
for
ppc
block
storage
and
then
we
have
two
under
ibm
cloud
provider
all
right.
So
let
me
just
brief
about
the
broader
special
interest
group
cloud
provider.
A
This
c
cloud
provider
is
a
group
of
people
interested
in
various
aspects
of
running
kubernetes
on
different
cloud
provider
clouds.
It
owns
cloudborder
provider
interface
code,
which
is
responsible
for
running
all
the
cloud
provider.
Specific
control
groups
right.
You
can
read
more
about
the
code
on
the
link
I
have
provided.
A
A
We
also
participates
in
various
activities
happening
in
the
sig
cloud
provider,
and
you
know,
as
a
member
of
this
project
or
you're
just
following
it.
You
basically
are
staying
on
top
of.
What's
going
on
in
the
ibm
cloud
platform,
with
respect
to
kubernetes
and
related
cncf
projects,
we
strictly
don't
discuss
any
commercial
kind
of
you
know
activities
or
any
discussions
related
to
it.
It's
all
about
an
open
source
side
of
communities
and
you
know
related
development.
A
So,
as
I
mentioned,
we
have
a
total
four
court
repositories
under
the
project.
This
year
has
been
great
for
the
project.
We
added
three
uni
three
new
repositories,
the
bottom
three
and
we
will
you
know,
do
a
briefing
on
each
of
them,
but
before
that
real
quick,
just
about
the
structure
of
the
project,
how
it
works.
So
we
have
three
colleagues
from
different
areas
of
ibm
cloud.
A
A
We
meet
every
month
every
last
wednesday
at.
But
if,
if
you
you,
you
know,
you
miss
the
past
meetings,
you
cannot
attend
it.
Then
you
can
always
look
at
the
meeting
recordings,
which
is
available
on
kubernetes,
youtube
channel
and
again
in
the
link.
You
can
read
more
about
the
project
all
right,
so
I
mentioned
that
we
added
you,
know
three
new
repositories,
but
this
one,
the
cluster
api
provider
ibm
cloud,
has
been
around
for
some
time
now.
A
As
you
already
know,
there
is
a
cluster
api
project
within
the
kubernetes
project
right,
it's
basically
about
the
about
managing
the
cluster
life
cycle,
creating
scaling,
upgrading
and
you
know,
destroying
the
cluster
by
cuban
installed
declared
apis.
So
it's
basically
cuban
is
to
manage
kubernetes
right.
So
there
is
a
management
cubist
cluster
which
manages
the
workload
cluster
where
the
applications
are
running
and
similar
to
cube
ctl
that
we
use
for
working
with
the
kubernetes.
A
Again
there
is
a
link
to
read
more
about
cluster
api.
There
is
a
whole
book
out
there.
Actually
so
various
cloud
providers
they
extend
the
cluster
api
and
for
ibm
cloud.
We
are
extending
it
under
cluster
api
provider,
ibm
cloud,
it
abstracts
the
infrastructure,
specific
details
and,
as
I
said,
you
know
this,
this
repository
has
been
around
for
some
time.
We
already
had
the
support
for
classic
infrastructure,
but
this
year
we
added
support
for
ibm,
vpc,
gen,
2
and
power
vs.
A
A
These
this
repo,
the
ibm
vpc
block
csr
driver
was
was
was
moved
to
the
kubernetes
six.
Just
recently,
I
would
say
you
know
just
just
a
couple
months,
so
it
provides
a
csi
plugin
for
creating
and
mounting
vpc
box
storage
for
your
applications
running
on
kubernetes
cluster
or
open
chip
cluster
on
ibm,
ppc
infrastructure.
A
A
B
Thank
you,
so
yeah
I'll
be
covering
iks
and
rocks
and
providing
the
details
on
our
cloud
controller
manager,
our
cloud
provider
project.
So
we'll
start
with
iks.
Just
to
give
you
a
little
background
on
our
kubernetes
service,
it
is
our
our
managed
offering
for
deploying
kubernetes
clusters
on
ibm
cloud
and
our
cloud
controller
manager.
Our
ibm
cloud
provider
is
used
as
part
of
this
service,
so
this
service
is
certified.
B
Kubernetes
conformant,
which
is
a
really
nice
program
from
the
cncf
to
certify
offerings,
is
kubernetes
compliant
and
so
that
customers
can,
you
know,
build
their
apps
on
cloud
native,
a
certified
platform
for
deploying
those
container
apps
on
kubernetes,
regardless
of
cloud
provider.
If
you
want
more
details
on
our
service
from
ibm,
you
can
check
out
that
link
all
right,
let's
jump
to
the
next
slide
and
we'll
talk
about
releases.
B
B
This
is
a
current
view
of
our
support
structure
from
iks.
We
support
119
and
later
fully
122
is
coming
out
soon
and
our
118
release
is
now
deprecated
and
we'll
be
out
of
support
very
soon.
So
this
is
very
similar
structure
to
the
communities
community,
which
just
came
out
with
patch
releases
119
to
122
this
week.
So
they
have
four
releases
and
support
at
the
moment,
but
119
will
be
dropping
out
of
support
soon.
B
So,
let's
move
on
to
the
next
slide
and
we'll
talk
rocks
so
rox
is
the
open
shift,
managed
service
on
ibm
cloud
and
openshift
builds
on
kubernetes
and
it
is
also
certified.
Kubernetes
can
form
it.
So
openshift
provides
some
additional
features
which
brad
will
talk
about
a
little
bit
later
and
if
you
want
more
information
on
the
managed
service
feel
free
to
check
out
that
link
on
the
slide
and
then
we'll
jump
to
the
next
slide.
B
in
the
just
like
our
our
kubernetes
users,
openshift
users
often
find
themselves
in
a
different
or
a
difficult
position
at
times
to
keep
pace.
One
of
the
benefits
of
openshift
in
this
space
is
that
red
hat
as
a
provider
of
openshift
takes
on
additional
extended
support
of
certain
releases.
So
you'll
see
on
the
slide
that
we
talk
about.
B
So
on
both
of
these
managed
services
and
then
many
managed
services
across
cloud
providers.
They
implement
what
the
community
calls
the
cloud
controller
manager,
which
is
the
control
loop
within
kubernetes,
owned
by
the
the
cloud
provider
sig,
which
is
the
interface
for
this
control
loop,
to
manage
an
interface
with
the
cloud
to
deliver
certain
features
to
the
kubernetes
cluster
that
kubernetes
itself
doesn't
implement
because
they're
cloud
provider
specific
and
that
the
cloud
controller
manager
is
then
responsible
for
implementing
those
key
features
for
the
cloud
now.
B
B
B
So
for
most
cloud
providers,
there's
two
main
things:
number
one
is
load
balancers
and
number.
Two
is
instances
we'll
start
with
load,
balancers
or
ibm
cloud.
We
provide
four
different
flavors
of
load
balancers
and
it
depends
on
the
infrastructure
on
which
you
run.
So,
if
you're
on
our
classic
infrastructure,
you
get
the
first
two
network
load
balancers
and
they
run
in
cluster.
B
They
leverage
basic
in
cluster
networking
ip
tables.
Ipvs
are
the
two
different
conversions
there
and
then,
if
you
move
to
our
vpc
infrastructure,
vpc
gen2,
we
have
a
couple
load
balancers
there
as
well
different
flavors
and
they're
configured
slightly
differently.
Details
are
in
our
docs.
As
far
as
how
that
is
concerned,
we
also
with
our
open
source
project
for
the
cloud
provider.
B
We
you
could
certainly
dig
into
the
code
details
to
find
out
how
that's
all
done
with
the
the
docs
associated
with
that
at
the
cloud
provider
level
and
how
those
load
balancer
types
are
configured
and
then
the
next
major
part
of
the
cloud
provider
is
it's
pro.
It's
responsible
for
node
initialization,
and
this
is
extremely
important.
So
I'm
talking
like
kubernetes
nodes
getting
brought
up
and
brought
into
the
cluster
they
get
stored
in
the
fcd
database.
B
The
node
is
coming
online,
but
the
node
stays
tainted
until
the
cloud
provider
comes
in
and
clears
the
taint
for
the
node
so
that
it
is
initialized
by
the
cloud
provider.
So
it's
a
really
important
part
of
the
bootstrap
process
for
your
cluster,
but
the
cloud
provider
is
functional.
It's
able
to
understand
that
node
comes
coming
in,
get
some
data
about
the
node
so
that
it
can
provide
it
to
kubernetes.
B
You
know
some
of
the
key
data
that
it
needs
to
know
is
the
type
of
instances
you're
dealing
with
yeah.
You
know
what
what
what
zone
is
it
in
and
so
on,
so
that
those
can
be
used
to
bootstrap
the
node
into
kubernetes
cluster
right
now
in
our
managed
service
offerings,
we
rely
on
an
internal
bootstrapping
process
to
help
us
with
this.
B
But
sad
I've
already
talked
about
how
we
have
the
vpc
block
plug
in
there,
which
is
a
separate
repository,
separate
control.
Loop,
so
we'll
move
on
to
the
next
slide
and
we'll
look
at
some
of
the
activities
that
that
were
focused
on
at
the
moment.
So
one
of
the
big
things
this
year
is
to
deliver
the
open
source
version
of
our
cloud
provider.
So
we
have
two
repos
out
there.
One
builds
the
core
the
other
one's
used
for
vpc,
some
of
the
vpc
component.
B
There's
a
bit
of
a
history
is
why
it's
done
that
way.
Ultimately,
we
like
to
have
one
just
one
repo,
but
that's
out
there
available
to
build
check
out
the
code.
It's
based
on
kubernetes,
1.22,
okay-
and
this
is
one
of
the
main
drivers
to
deliver.
The
open
source
was
to
support
openshift,
ipi
or
upi
installs
on
ibm
cloud.
So
this
is
installation
done
outside
of
the
managed
service.
Now
openshift
provides
this
type
of
installation
on
a
lot
of
cloud
providers.
B
B
Now
the
cloud
provider
community
and
the
sig
has
determined
that
those
are
all
deprecated
all
those
cloud
providers
that
treat
they
need
to
move
out
of
tree,
and
that
is
going
to
be
the
new
path
forward
and
eventually
those
entry
cloud
providers
will
be
removed
from
the
code
base
in
kubernetes
okay.
So
it's
really
important
for
consumers
to
switch
to
auditory
cloud
providers
and
the
49
release
of
openshift
is
really
where
the
red
hat
folks
worked
with
a
lot
of
the
cloud
providers
to
start
transitioning
from
these
entry
providers
to
out
of
tree.
B
So
they
did
a
lot
of
work
with
like
openstack
folks
and
amazon
and
microsoft,
and
obviously
us
ibm
to
try
to
support
ccm
based
installs
of
openshift
on
various
cloud
providers.
So
we
started
our
work
in
4.9
for
continuing
here
in
4.10
of
openshift.
Our
goal
is
to
complete
in
4.10
and-
and
that
is
a
lot
of
changes
will
be
required
for
our
cloud
provider
to
support
this
type
of
installation
mechanism,
because
at
the
moment
it
was
designed
for
our
managed
services.
B
So
that's
another
second
big
piece
that
we're
working
on
with
that
you
know.
Different
features
will
hopefully
be
coming
areas
of
networking.
We've
been
looking
at
different
things
in
the
load,
balancers
or
in
routing,
and
then
having
this
up
in
openshift
in
the
community,
also
having
the
open
source
up
there.
C
Thank
you.
So
one
question
that
we
typically
get
at
this
session
is:
what's
the
difference
between
kubernetes
and
openshift,
and
essentially
openshift
is
a
kubernetes
distribution
that
includes
extra
tooling,
to
simplify
cloud
native
development
and
provide
automated
operation
support
so,
for
example,
in
just
vanilla
kubernetes.
C
You
find
a
base
image
and
you
use
the
docker
commands
to
to
then
take
the
base
image
and
then
add
your
code
to
that
image
and
you'll
you'll
create
a
new
image
using
those
commands
and
then
you'll
push
it
to
a
registry
and
so
a
lot
of
us.
You
know
the
folks
on
the
on
on
this
presentation,
we're
very
familiar
with
doing
those
steps,
we're
very
comfortable
doing
it,
but
there's
a
lot
of
developers
out
there
like
java
developers
that
aren't
very
familiar
with
those
steps,
and
so
what
openshift
provides
you
is.
C
C
So
it's
it's
reducing
the
friction
for
developers
who
wouldn't
commonly
know
those
low
level
cloud
native
development,
steps
of
dealing
with
the
containers
and
dealing
with
the
image
and
building
the
container
image.
So
you
know
openshift's
going
to
take
care
of
that
with
its
sourced
image.
Make
that
a
lot
easier
for
for
those
types
of
developers.
C
It
also
probably
provides
nice
techniques
for
recognizing
when
images
change
or
when
the
configurations,
change
and
even
being
able
to
automate
automate,
actually
the
deploy
when
those
changes
occur.
So
that
management
aspect
is
also
made
simpler
through
openshift
openshift's
security
is,
is
a
big
big
feature
of
of
of
it.
It
has
good
security
guard
rails,
so
with
vanilla
kubernetes,
you
can
do
a
lot
of
things
that'll.
Let
you
out
of
the
box
do
a
lot
of
things
that
aren't
very
secure.
C
C
If
you
ever
take
a
container
and
let
it
run
as
privileged,
it
gives
you
boot
access.
There
is
a
lot
of
surface
area
for
a
security
breach
when
you
do
that,
so
out
of
the
box,
openshift
is
going
to
keep
you
from
doing
that
and
you'd
be
surprised
how
many
images
are
out
there
that
you
didn't
realize
are
are
built
to
run
as
privileged.
C
Similarly,
openshift
gives
you
it.
It
prevents
you
from
running
with
a
default
namespace
again
using
the
default.
Namespace
is
not
a
secure
and
you
really
need
to
learn
to
not
use
it,
and
so
openshift
keeps
you
from
doing
that,
and
a
final
security
feature
that
I
want
to
cover
is
the
notion
of
security
context
constraints.
C
Basically,
openshift
provides
you
several
security
profiles
that
you
can
choose
for
your
pods
container
and
what's
nice
about.
That
is
that
that
enables
you
to
not
have
to
worry
about
all
the
individual
security
knobs
and
try
and
get
all
the
individual
security
settings
correct,
because
if
you
have
like
25
settings,
the
odds
are
and
you're
trying
to
set
each
one
individually,
and
you
think
you
know
what
you're
doing
the
odds
are
you
may
not,
and
so,
instead
of
you
setting
all
the
individual
knobs,
you
could
just
pick
a
security
context
profile
and
use
the
one.
C
That's
that's
best
for
your
for
your
pods
container
and
the
nice
thing
is,
then
you
know
what
features
what
security
enablement
your
pods
container
is
gonna
get
when
you
pick
that
security
context,
so
you'll
know,
will
I
have
root
access
or
not?
Will
I
have
access
to
all
the
block,
storage
or
only
a
portion
of
it?
Will
I
have
to
run
as
user?
So
all
those
types
of
features
and
you'll
know
exactly
what
you're
guaranteed
to
get
the
security
context
constraints
give
you
that
ability
day
two
operations.
C
This
is
another
place
where
openshift
really
shines.
It
has
automated
cluster
size
management,
so
it
can
automatically
provision
new
worker
nodes
to
increase
your
increase.
Your
cluster
size,
that's
a
huge
feature
that
you
don't
get
with
vanilla,
kubernetes
automated
day
two
operations.
It
can
do
automated
installation,
automated
updates.
C
It
worries
about
making
sure
the
right
version
of
openshift
is
running
on
the
right
version
of
rel,
so
that
you're
guaranteed
you've
got
full
stack
consistency.
It
uses
a
capability
of
identifying
what
are
called
cluster
versions,
and
so
it
does
cluster
version
management
to
do
all
that
automation
of
of
the
life
cycle
management.
C
So
those
are
huge
features
for
your
day.
Two
and
your
it
operation.
Side
of
your
house
and,
of
course,
openshift
also
provides
multi-cloud
management
support,
provides
a
unified
cloud
console
to
view
and
manage
multiple
openshift
clusters.
So,
as
you
get
into
production
and
you're
dealing
with
multiple
clusters
on
multiple
clouds,
this
is
where
openshift's
going
to
shine
as
well.