►
From YouTube: Intro + Deep Dive - Provider IBM Cloud - Sahdev Zala, Richard Theis, & Brad Topol, IBM
Description
Don’t miss out! Join us at our upcoming event: KubeCon + CloudNativeCon Europe 2021 Virtual from May 4–7, 2021. 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.
Intro + Deep Dive - Provider IBM Cloud - Sahdev Zala, Richard Theis, & Brad Topol, IBM
In this session, the project leads will provide an overview of the IBM Cloud Provider subproject, its open source activities, and learning resources. It will be followed by a discussion on the recent developments as well as future work in the IBM Cloud Provider and Kubernetes Cluster API Provider IBM Cloud. This session will be of value to a broad audience including active contributors, new contributors, and those with an interest in the IBM Cloud Provider features and capabilities or the Kubernetes Cloud Provider in general.
https://sched.co/ekHP
A
B
C
A
Well,
thank
you
richard
and
brad
all
right.
So
in
today's
talk
we
will
provide
an
overview
of
sig
club
provider.
There
will
be
a
separate
talk
for
c
cloud
for
itself,
so
you
know
I
would
highly
recommend
you
to
attend
that
to
know
more
about
the
cloud
forwarder
seek.
But
in
this
talk
I
will
just
brief
about
it.
A
A
A
Now
you
can
find
more
about
the
you
know,
code
at
the
url
that
I
have
provided
here.
The
seek
it
ensures
that
the
cubans
ecosystem
is
evolving
in
a
way
that
is
neutral
to
all
club
providers.
So
you
know
there's
no
favor
given
to
one
cloud
provider
over
other,
and
you
know,
everybody's
everybody
can
participate
in
the
ongoing
discussions
and
you
know
the
implementation
of
a
specific
cloud
provider.
A
The
seek
also
ensures
a
consistent
and
high
quality
user
experience
across
different
cloud
providers
and
it
owns
all
the
sub
projects.
They
were
formerly
known,
as
you
know,
sig
themselves.
You
know
for
different
cloud
providers
like
aws
or
sig
for
azure
gcp
or
see
ibm
cloud
seek
openstack,
sig,
vmware
and
so
on.
A
The
provider
ibm
cloud.
It's
a
sub
project
of
this
sig
cloud
provider.
As
I
mentioned,
there
will
be
a
separate
talk
on
seek
cloudwater
itself.
So
I
would
highly
recommend
you
attend
that
to
know
more
about
the
cloud
for
receive
and
you
can
also
see
and
refer
documentation
in
the
url
that
I
have
mentioned
at
the
at
the
bottom
of
the
slide.
Rest
of
this
talk
will
focus
on
the
provider
ibm
cloud
already.
So
this
is
a
project
of
you
know,
cloud
provider
see
it's
it's
around.
A
A
You
know
you
get
to
follow
the
evaluation
of
the
ibm
cloud
platforms
with
respect
to
kubernetes
and
you
know
related
cncf
projects,
all
right,
so
the
structure
of
the
project.
You
know
when
you
talk
about
it.
We
have
three
colleagues
khalid
ahmed
he's
from
ibm
multicloud
manager,
side.
We
have
richard
thiess,
who
is
one
of
the
speaker
here
today.
A
He
represents
ibm
cloud
cuban
service
and
red
hat
openshift
community
service
and
then
myself
I
am
representing
more
from
open
source
software
side.
You
can
find
some
of
the
link
here.
That
will
be
useful.
You
know
like
mailing
lists,
so
I
would
highly
recommend
to
be
part
of
the
mailing
list
to
get
updates
on
the
project.
We
have
a
slack
channel
which
the
provided
ibm
cloud
slack.
You
know
highly
recommend
to
be
you
know
to
to
to
be
there
to
see.
A
What's
going
on,
you
know
we
provide
the
updates
and
other
things
there
regularly
and
you
can
find
more
about
the
project
documentation.
On
the
on
the
link
I
have
provided
here
for
the
github
all
right
activities
we
meet
every
month,
so
it's
last
wednesday
at
2
p.m.
Eastern
time
we
have
a,
you
know,
30
to
45
minutes
or
sometime
an
hour
meeting
depending
on
the
agenda.
A
Now
all
the
recordings
for
the
meeting
are
also
available.
You
know.
So
if
you
have
missed
the
past
meetings,
if
you
cannot
attend
future
meetings,
you
can
refer
to
the
videos
and
and
take
a
look
there.
We
regularly
participate
in
the
sig
club
for
directional
activities.
You
know
their
bi-weekly
meetings
and
other
things.
A
The
project
owns
a
sub-project
called
cluster
api
provider,
ibm
cloud
which
is
an
extension
of
the
cluster
api
project
of
kubernetes
right.
So
the
cluster
api
project
is
itself
a
sub
project
of
kubernetes
and
it
provides
you
know:
optional
additive
functionalities,
on
top
of
core
communities
to
manage
the
life
cycle
of
cumin's
cluster.
A
Now
brad
will
be
giving
more
details
there
later
in
this
presentation,
and
then
you
know
we
are
staying
on
top
of
support
for
out
of
free,
ibm
cloud
provider
in
c
cloud
provider.
You
know
that
discussion
has
been
going
on
for
for
some
long
time
in
the
meetings
through
the
mailing
list
through
the
different
talks
that
some
of
the
providers
specific
code,
which
were
part
of
the
cuban
core
they
they
are
taken.
B
All
right,
thank
you
so
yeah
I
will
be
taking
you
through
iks
rocks
and
our
cloud
provider
and
we'll
start
here
on
iks,
which
is
ibm
cloud
kubernetes
service,
which
is
ibm's,
managed
kubernetes
service.
So
you
can
create
cube
clusters
and
ibm
cloud
and
there's
a
lot
of
other
managed
services
out
there
and
so
in
in
a
similar
fashion.
To
those
we
are
a
certified
kubernetes
provider
through
the
cncf
certification
program
for
kubernetes.
So
if
you'd,
like
more
information
on
that
service,
you
can
check
out
the
link
on
the
docs
there.
B
B
B
So
you
know
a
lot
of
folks
are
trying
to
stay
current.
There
was
a
discussion
on
the
long-term
support
for
kubernetes.
What
that
might
look
like
a
few
things
changed
this
year
with
covid
and
other
things
happen.
The
delay
of
119
release
was
noted,
and
116
was
extended
for
a
little
bit
more
having
support,
ideally
trying
to
allow
people
to
maybe
only
have
to
upgrade
once
a
year
their
clusters.
B
So
then,
the
current
discussion
that
is
going
on
in
the
community
and
feel
free
to
contribute
to
that
is
whether
or
not
cougs
should
have
three
releases
a
year
or
four
and
right
now.
What
I've
seen
is
a
little
bit
more
weighted
towards
three
people
prefer,
but
certainly
keep
keep
your
feedback
coming
to
the
community,
so
they
can
make
good
decisions
on
these
things
and
as
far
as
patch
releases
kubernetes
did
a
great
job
this
year,
getting
a
very
good
cadence
on
delivering
patches
for
the
support
releases.
B
They
generally
do
it
monthly
about
mid-month.
They
patch
all
the
releases
at
the
same
time,
which
has
been
really
helpful,
especially
for
managed
services
and
I'm
sure
for
products
as
well
to
be
able
to
deliver
those
patches
quickly
and
in
a
timely
manner,
very
consistent
manner
and
we've
been
doing
that
as
well.
B
So
next
slide,
please
so
red
hat,
open
shift
on
ibm
cloud
or
the
red
hat
openshift
kubernetes
service
is
another
managed
service,
again
openshift's
built
on
kubernetes.
So
this
is
a
also
a
kubernetes
certified
offering,
through
the
cncf
and
and
red
hat,
builds
on
that
kubernetes
base
capability.
To
give
you
some
additional
functions
with
brad,
we'll
talk
about
a
little
bit
later
and
if
you
want
more
information,
I
included
a
link
there
for
for
open
shift
and
next
slide.
Please
for
the
release.
Standpoints.
B
We've
delivered
three
releases
of
rocks
this
year,
so
very
similar
cadence
to
iks.
You
can
see
each
version
of
openshift
is
based
on
a
version
of
kubernetes,
so
the
latest
one
for
five
that
we've
delivered
is
based
on
cube118
and
we
fully
expect
a
4
6,
soon
from
red
hat
and
open
shift
that
will
be
based
on
cube,
1,
19
and
then
certainly
we'll
be
following
that
up
and
delivering
that
through
the
managed
service
as
well.
B
So
you
can
see
the
impact
of
the
velocity
of
kubernetes
carries
over
into
the
velocity
of
openshift
they're,
also
moving
very
quickly
now
on
the
chart
here,
we
we
show
four
three
four
and
five.
There
also
is
a
long
term
support
from
openshift
and
red
hat
on
311,
that's
based
on
cube111,
so
that
has
a
bit
of
extended
life.
We
fully
expect
for
a
version
of
four.
B
B
When
you
look
at
kubernetes,
it's
very
pluggable
a
lot,
a
lot
of
interfaces,
whether
it's
through
like
the
api
levels
crds
and
such
the
cloud
provider,
is
no
different
and
and
there's
various
unique
functionalities
in
each
cloud
and
that
we
need
to
provide
through
kubernetes,
controlled
interface,
and
that
interface
is
the
the
cloud
controller
manager
or
the
ccm
through
the
cloud
provider.
So
that's
the
architecture
that
kubernetes
has
today
to
support
various
clouds
and
we
leverage
this
architecture
both
of
our
managed
services
so
on
the
control.
B
Plane
side
is
where
you
find
the
api
server,
scheduler,
the
kube
controller
manager,
and
it's
also
where
you
find
in
our
managed
services.
The
cloud
controller
manager,
which
is
the
key
aspect
of
taking
advantage
of
the
cloud-specific
features
that
you
need
to
deliver.
Some
of
those
key
aspects
of
kubernetes
that
you
come
to
expect
now
on
the
worker
node
sides
where
you
have
the
kubelet
and
kuproxy.
You
know
they're,
obviously
running
on
nodes
within
the
cloud
and
those
don't
no
longer
have
direct
connections
to
the
the
cloud.
B
If
you
will,
that
was
under
the
old
architecture,
they
used
to
do
that
direct
connections
and
they're,
trying
to
free
that
up,
so
that
the
control
loops
are
contained
and
it's
much
cleaner
interface
going
forward
so
that
the
code
that
used
to
live
in
kubernetes
can
more
easily
be
extracted.
Dependencies
can
be
broken
that
were
specific
to
cloud
providers
that
we
could
get
these
rolled
out
into
their
own
repositories
to
to
make
it
easier
for
everybody
to
both
consume
kubernetes,
but
also
to
build
cloud
specific
features
for
kubernetes.
B
B
You
have
a
little
bit
different
load
balancers
that
are
available.
So
in
the
classic.
You
have
a
network
load
balancer
based
on
ipps
or
ip
tables.
It
runs
in
cluster
and
then,
when
you
go
to
the
vpc
infrastructure,
you've
got
a
layer,
7
load
balancer,
and
then
you
also
have
a
network
load
balancer,
which
is
new
in
our
119
release
that
we
just
delivered.
B
There's
also
the
instances
which
is
another
huge
one,
huge
component
to
the
cloud
provider
which
is
managing
the
nodes.
In
particular,
you
want
to
know,
say
where
the
zone
region
instance
type
of
the
node,
so
that
can
be
data
fed
back
to
kubernetes,
for
important
aspects
of
scheduling
and
and
so
on.
So
those
are
those
are
important
pieces
now
being
the
managed
service.
A
lot
of
the
bootstrapping
happens,
it's
part
of
the
managed
service,
and
we
take
advantage
of
that
through
the
cloud
provider
to
deliver
that
data
to
kubernetes.
B
The
community
has
moved
with
this
new
architecture.
They
saw
the
need
for
a
new
instances,
v2
interface
as
part
of
the
cloud
provider
that
was
new
in
119
as
an
alpha.
It's
going
to
progress,
I
I'm
hoping
to
a
beta
and
we're
looking
at
taking
advantage
of
that.
It's
a
little
bit
more
streamlined
interface
to
align
with
the
new
design
of
the
cloud
providers,
and
then
we
do
do
some
implementation
for
zones
which
is
needed
for
load,
balancer
and
scheduling.
B
B
So
as
always,
I
don't
have
it
on
here,
but
we
continually
take
the
data
that
we
collect
through
running
kubernetes,
both
within
the
managed
service
based
kubernetes
and
then
within
openshift,
and
our
managed
service
of
through
red
hat
there
delivering
what
we
know
and
back
to
the
kubernetes
community.
What
we
learned
running
kubernetes
at
scale,
problem
security,
things
enhancements
feedback.
We
always
try
to
deliver
that
back
also
being
part
of
the
cloud
provider
we're
looking
to
expand
our
role
here,
especially
if
we
can
open
source
our
ibm
cloud
provider.
B
Things
are
aligning
a
little
bit
better
as
the
kube
community
works
to
extract
and
migrate.
All
those
entry
providers
auditory
making
it
a
lot
more
easier
to
work
on
dependency
management,
builds
release
processes
they're
all
coming
together
to
make
it
get
us
to
a
point
where
this
is
going
to
be
much
easier
for
for
all
cloud
providers
to
to
deliver
in
the
future.
So
with
that
we'll
be
looking
at
improving
our
docs,
our
building
test
release
processes
aligning
our
goal
dependency
management
with
what
kubernetes
does
so.
C
Thank
you,
richard
yep,
so
the
ibm
cloud
provider
project
has
as
a
sub
project
the
cluster
api
provider,
ibm
cloud
subproject
and
if
you're
not
familiar
with
the
cluster
api
provider
projects
in
kubernetes,
basically
they
provide
a
a
declarative
model
or
approach
and
tooling
to
simplify
the
provisioning,
upgrading
and
operating
of
of
clusters,
and
so
we
have
our
active
project
in
this
space.
The
cluster
api
provider
ibm
cloud
and
just
just
to
see
some
of
the
basics
here,
there's
always
a
target
cluster.
That's
the
cluster.
C
C
There
is
a
cluster
control
command,
so
there's
a
command
line
interface.
That
is,
makes
life
easy
and
makes
it
easy
to
run
the
the
types
of
commands
for
for
managing
the
clusters-
and
you
know
ibm-
is
one
of
many
vendors
that
that
has
embraced.
You
know
this
approach,
so
you
can
see
the
architecture
here
on
the
right.
If
you're
interested
again,
we
have
an
active
project
in
this
space
and
feel
free
to
go
check.
C
C
C
But
openshift
is
a
kubernetes
distribution
from
red
hat
that
includes
extra
tooling,
to
simplify
cloud
native
development
and
also
provides
automation,
automated
operation
support.
So
when
you
start
doing
development
for
cloud
native
applications,
if
you're
just
getting
started
you're
going
to
start
running
in
production,
it
requires
a
lot
of
skills
right.
So
you
need
to
be
able
to
create
container
images,
and
you
typically
need
to
know
how
to
find
a
base
image
and
then
take
your
code
and
merge
it
into
the
base
image
and
create
the
new
image
and
push
it
to
a
registry.
C
And
if
you
work
with
kube
every
day.
Well,
maybe
you're
an
expert
at
that,
and
that's
not
so
difficult.
But
if
you're
a
large
organization-
and
you
say,
have
lots
of
java
programmers
lots
of
python
developers,
these
are
folks
who
want
to
get
the
benefit
of
cloud
native,
but
maybe
don't
have
all
those
cloud
native
skills.
So
one
of
the
things
that
openshift
provides
is
image,
creation
and
deployment,
tooling.
That
makes
it
real
easy
for
a
developer
to
just
push
a
change
to
a
git
repository.
C
This
is
called
source
to
image
and
and
through
openshift.
It's
able
to
recognize
that
find
the
right
base
image,
merge
your
new
code
changes
into
the
base
image
and
push
it
to
a
registry,
and
so
taking
care
of
all
those
details
is
reducing
the
amount
of
friction
for
a
developer,
who
doesn't
work
in
cloud
native
every
day
and
is
an
expert
at
docker,
configs
and
and
what
have
you
to
be
able
to
get
up
and
running
and
and
run
their
application
in
a
cloud-native
fashion
in
a
kubernetes
environment.
C
C
So
a
lot
of
features
that
that
become
very,
very
valuable
when
you're
ready
to
run
in
production,
so
obviously
ibm
has
just
standard
kubernetes
and
openshift
as
richard
covered.
But
those
are
the
differences
next
chart
and
so
that
pretty
much
concludes
our
presentation
and
we'd
like
to
thank
you
for
attending.