►
From YouTube: CERTS Magic with Saiyam - Episode 4
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hello,
everyone
and
welcome
to
cloud
native
tv.
My
name
is
sayam
parhak,
I'm
a
cncf
ambassador
and
working
as
director
of
technical
evangelism
at
sibo,
so
welcome
to
cloud
native
tv
and
welcome
to
the
search
magic
show.
A
This
is
a
an
official
live
stream
of
cncf
and,
as
such
is
subject
to
cncf
code
of
conduct.
Please
do
not
add
anything
to
the
chat
or
questions
that
would
be
in
violation
of
that
code
of
conduct.
Basically,
please
be
respectful
for
of
all
your
fellow
participants
and
presenters
so
clown
native
tv,
and
this
is
the
search
magic
show
and
it
happens
bi-weekly,
but
there
are
shows
running
every
day
on
crowded
tv,
so
make
sure
you
subscribe.
A
That
now
and
search
magic
is
a
show
about
community
certifications,
and
I,
where
I
come
with
new
concepts,
new
certifications
and
talk
about
the
favorite
ones,
which
are
cka
ck
adcks
and
we
go
over
through
the
curriculum
and
try
to
cover
some
of
the
topics,
explain
them
in
a
different
way
and
try
to
do
some
hands-on
scenarios
as
well
and
in
between.
If
there
are
any
tips
and
tricks,
then
we
also
go
over
them.
Sometimes
we
do
have
a
case,
sometimes
it's
all
by
myself.
A
So
it's
it's
just
go
like
this.
So
all
the
streams
all
the
past
episodes.
A
So
this
is
the
fourth
episode
and
the
past
three
episodes
are
there
on
youtube
on
the
cscf
youtube
channel,
so
make
sure
you
check
them
out
what
we
have
covered
till
now
is
we
have
covered
introduction
to
certifications,
why
certifications
are
important
and
why
you
would
need
the
certifications,
so
that
is
pretty
important
like
why
all
any
of
the
certifications
matters
then,
in
the
second
episode
we
went
over
through
the
the
cluster
setup
and
the
basic
humanities
architecture.
A
So
we
went
from
zero
in
the
kubernetes
architecture
to
the
explanation
of
end
to
end
each
component,
what
it
means
by
tim,
and
we
also
went
through
a
kubernetes
setup,
which
was
the
cube
and
cryo
setup
and
in
the
last
stream,
which
is
episode
3,
I
discussed
about
the
human
objects.
A
So
we
did
the.
A
And
the
pods
deployments
demon
sets
stateful
sets,
I
mean
not
the
we
didn't
do
the
examples
of
all
these,
but
at
least
we,
you
know,
discovered
what
what
a
part
is.
What
about
spec
is
how
do
we
create
a
pod,
and
how
do
we
run
it?
How
do
we
run
it
in
a
different
name
space?
What
is
deployment?
What
do
you
mean
by
replicas?
How
do
we
run
the
deployments?
How
do
we
do
the
dry
run
and
save
the
yaml
files
and
and
all
those
different
things
we?
A
How
do
we
scale
it?
How
we
scale
down?
How
do
we
roll
out?
How
do
we
record
the
deployment
and
we
undo
the
roll
back
the
changes,
so
all
these
things,
which
are
very,
very,
very
relevant
to
the
the
certification
point
of
view,
so
this
is
what
we
have
covered
till
now
and
today,
before
we
go
into
the
more
into
the
cka
stuff.
What
I
would
what
I
would
like
to
do
is
I
actually
want
to
cover
something
which
is
actually
related
to
the
certification.
A
So
I
thought
like
we
should
take
the
certifications
to
the
next
level,
because
the
show
is
certs
magic
and
it's
about
humanity's
certifications
and
in
right
now,
at
the
moment
it
is
not
limited
to
ckck
dcks,
so
we
have
a
few
other
certifications
which
are
there
in
the
industry
and
that
you
can
actually
take
up
for
free.
So
we'll
talk
about
those
first
first
is
the
get
calico
certified
kelco
operator
level
one.
A
So
this
is
a
very
interesting
certification
provided
by
tigera,
it's
free
of
cost,
and
you
get
to
learn
about
kubernetes
networking,
then
installing
the
calico.
A
What
what
a
network
policy
is-
and
you
know
how
to
use
the
network
policy,
best
practices,
network
policy
for
hosts
and
the
node
ports,
and
then
everything
you
need
to
know
about
networking.
Basically,
the
pod
connectivity,
how
the
power
to
port
networking?
How
does
that
go?
Evpf
data
plane,
the
next
generation
data
plane
that
is
there
encryption
and
then
the
ip
address
management
peering
with
bgp.
A
Also
everything
you
need
to
know
about
the
community
services
so
introduction
to
community
services,
how
what
is
q,
proxy,
calico
native
service
and
advertising
services.
So
this
is
actually
a
free
certification
and
there's
also
a
book
which
is
more
about
the
community's
networking
written
by
alex.
I
I
did
a
stream
with
alex
on
my
channel
as
well.
So
a
great
guy,
great
shout
out
big
shout
out
to
alex
his
explanations
are
actually
very
simple
to
understand,
so
make
sure
you
take
that
course.
A
Next
one
is
certified,
get
certified
on
the
essentials
for
sto,
so
hto
again
is
is
the
most
popular
service
mesh
out
there
and,
like
solo,
has
come
up
with
this
sort
of
certification,
where
you
learn
the
essentials
of
like
what
is
your
data?
Plane
is
what
is
involved
proxy.
You
know
how
to
install
sto
and
then
the
day
two
operations
of
sto
then
how
to
slowly
introduce
stu
in
your
organization.
A
So
you
can
just
log
into
sumo
logic,
and
there
are
like
fundamental
certifications
and
a
lot
of
good
things
like
advanced
metrics
security
and
compliance
for
kubernetes,
monitoring
and
troubleshooting.
I
think
this
one
would
be
really
interesting,
so
I
think
you
can
you
can
take
that
another
one
is
in
the
cloud
native
ecosystem
which
is
getting
popular.
Is
the
chaos
engineering,
so
chaos,
engineering
certification
is
also
there
and
you
can
take
that
certificate
as
well.
A
And
the
next
one,
and
by
far
I
think,
the
most
cool
one
is
the
rancher
operator
level
one.
So
you
will
get
to
understand
all
the
concepts
of
rancher
and
the
rke,
which
is
rancher
kubernetes
engine,
a
kubernetes
certified
community,
a
certified
cn
a
cncf
humanities
distribution
by
rancher.
Actually,
we
have
rancher
if
you
have
rke2
also
now,
but
I
think
this
is.
This
is
really
good
certification,
and
this
is
really
good
in
terms
of
learning
the
concepts
of
the
the
rancho
communities
engine.
A
What
rancher
is
how
to
install
actual
docker,
accurate,
kubernetes
and
all
those
stuff
so
designing
the
provisioning.
The
clusters,
then
the
cluster
roles,
rke
templates,
how
you
can
play
with
that
troubleshooting
clusters,
the
answer,
api
server,
container,
runtime,
node
conditions
and
all
those
things.
So
I
think
they
are
really
really
good,
and
even
after
that,
you
have
advanced
things
like
enable
advanced
monitoring,
configure
notifiers,
alerting
namespaces
projects.
What
is
the
project
in
in
rancher?
So.
A
Workloads,
persistent
storage,
conflict
map
secrets,
so
I
think
that's
a
complete,
complete,
complete
course
that
will
give
you
a
lots
and
lots
of
understanding
of
the
concepts
as
well
as
it's
a
certification
as
well
that
you
get
at
the
end.
After
doing
a
sort
of
test
that
that
you
know
you
get
so
yeah
that
that
was
pretty
much
it
for
the
certifications.
So
I
think
they
are
pretty
good
and
I
hope
you
take
them
all
now
you
also,
while
attending
the
stream.
A
You
get
a
chance
to
win
a
50
discount
coupon
on
kubernetes
certifications,
which
are
cka
ckddcks.
A
A
Topic,
which
was
you
know,
which
came
up
actually
in
the
last
three
and
the
previous
one
where
people
were
asking
about
the
things
and
the
tolerations.
What
are
they
how
they
work?
And
you
know
basically
people
usually
get
confused
in
the
in
the
attendance
and
toleration
concept.
So
I
I'll
try
to
simplify
the
concept
and
make
sure
like
we'll
try
to
you
know,
make
you
understand
the
concept
of
things
and
toleration.
Apart
from
that,
we'll
also
look
at
node
affinity,
so
first
node
affinity,
then
things
and
tolerations.
A
Okay,
so
yes,
it
falls
under
the
category
of
workload
and
scheduling,
so
we
will
be
covering
node
affinity
and
things
and
alterations
so.
A
So
we
are
talking
about
scheduling,
scheduling
means
like
whenever
you
create
a
pod
or
a
deployment
where
that
pod
actually
goes
to
which
node
that
pod
actually
goes
and
runs
the
application.
So
for
that
we
have
various
concepts
and
one
of
them
is
node
affinity,
so
node
affinity
is
basically
where
your
parts
can
actually
be
scheduled
based
on
the
labels
of
the
nodes.
Now
you
might
be
thinking
that
it
is
the
same
purpose
of
node
selector.
Yes,
it.
B
A
A
Now
we
have
two
things
which
is
in
the
node
affinity,
which
is
required
during
scheduling,
ignored
during
execution.
This
is
the
hard
way
of
doing
it.
Next,
we
have
is
preferred
during
scheduling
and
ignored
during
execution,
and
this
is
the
software
now.
A
A
But
if
this
can't
satisfy
some
of
the
other
things,
then
we
cannot
so
ignore
during
scheduling
is
actually
same,
but
I
think
in
future
there
will
be
more
options
with
respect
to
this
particular
word,
and
if
labels
are
changed
at
run
times
like
nothing
would
actually
happen.
A
So,
if
the
so,
if
you
change
the
node
labels,
that
are,
if
you,
if
you
change
the
node
labels
at
the
runtime
and
some
pod
is
already
running
and
it
doesn't
have
that
labels,
so
you
so
that
part
will
be
running
so
means
the
ignored
during
execution
means
the
labels
you
you
are
changing
on
the
node
during
the
execution.
Time
will
be
ignored
if
the
for
the
part
which
is
already
running
on
that
node.
Now
that
makes
it
clear
next
one
is
your
example,
so
you
have
a
pod.
A
You
have
a
metadata
for
that.
Now
in
the
spec
section
of
the
pod,
we
define
something
called
affinity
in
that
we
defined
node
affinity
in
node
affinity.
We
have
defined
required
during
scheduling
and
ignored
during
execution,
and
there
are
the
node
selector
terms.
You
can
have
multiple
load
selector
terms,
and
at
least
one
of
them
should
be
true,
so
we
are
now
matching
the
expressions
now
how
we
match
the
expression
we
say
key,
which
is
the
key
for
that
and
operator
is
in,
and
the
values
are
this.
A
This
means
a
pod
can
be
scheduled
with
this
particular
label
and
either
one
of
these
values
on
to
this
node,
a
pod
can
be
scheduled
with
humanities,
dot
io,
slash
e
to
e
is
at
label
value
any
one
of
these,
so
if
that
particular
par,
if
it
is
this
particular
pod,
so
this
particular
part
will
be
scheduled
on
the
node,
where
you
have
these
labels.
A
Now,
if
multiple
nodes
meet
the
above
criteria,
then
prefer
node
matching,
so
this
one
will
prefer
that.
So
if
multiple
nodes
are
meeting
the
criteria
for
the
bar
to
be
scheduled,
then
prefer
the
one
with
the
label
this
and
the
value
this
so
prefer
the
one
with
the
label,
which
is
in
the
in
the
preferred
section
and
the
value
with
this.
So
that's
how
the
node
affinity
works.
A
Now
people
often
do
get
confused
in
node
affinity
and
taints
and
toleration.
So
now,
according
to
the
official
definition,
no
definitely
is
the
property
of
the
pods.
This
one
node
affinity
is
the
property
of
the
pods
that
attracts
them
to
a
set
of
nodes,
because
you
are
defining
the
affinity
that
it
is.
You
know
attracting
towards
the
node,
whereas
paints
are
the
opposite.
They
allow
the
node
to
repel
the
set
of
ports.
Now
it
is
basically
restrictive.
Now
I
am
telling
the
node
you
know
not
to
take
up
these
set
of
pods.
A
Now
let
us
try
to
understand
with
the
with
the
example.
I
don't
know
how
much
relevant
it
would
be,
but
I
just
came
up
with
this.
So
let's
say
you
have
a
you:
have
a
party,
your
birthday
party
or
just
any
other
party,
or
maybe
a
cube
con
party
and
in
the
party
the
dress
code
mentioned,
is
red,
so
you
have
a
dress
code,
which
is
red.
A
Now
there
are
friends,
there
are
three
friends
blue,
green
and
red,
and
they
they
decide
to
go
to
the
party,
but
you
know
out
of
that
only
one
person
has
breastfed.
So
that
means
only
person
with
the
dress
red
can
be,
can
attend.
A
The
party,
so
you
are
understanding
right,
so
treat
this
as
a
node,
and
this
particular
node
can
only
take
something
with
label
with
the
paint
which
we
like,
which
I'll
explain
in
the
in
the
next
section
with
the
paint
has
a
taint
called
dress
red
and
so
all
the
pods
all
the
pots,
and
in
this
case
it
is
all
the
all.
The
people
which
do
not
have
the
toleration
will
be
rejected.
A
So
blue
comes
it's
rejected,
green
comes
it's
rejected,
but
or
any
pod
with
the
toleration
any
pod
with
the
toleration
dress,
red
will
be
admitted.
So
that's
how
you
can
relate-
and
I
mean
can
be
a
weird
example,
but
might
stick
to
your
heads
now,
let's
try
to
understand
in
in
proper
kubernetes,
so
on
a
node.
So
obviously
kubernetes
you
have
this.
This
is
a
kubernetes.
Let's
say
it's
a
control
plane,
and
these
are
your
worker
nodes.
A
Of
the
node
now
in
this
particular
node
in
this
particular
node,
we
have
a
taint
applied.
Okay,
we
have
a
taint
applied
now
that
taint
is
foo,
which
is
the
key,
so
it
is
in
the
form
of
key
value
and
effect
this
equal
key
value
and
effect.
So
in
this
particular
case
there
is
a
paint
which
is
set
on
the
node,
which
is
called
foo
equal
to
bar
with
the
effect
of
no
schedule.
A
A
A
A
So
this
particular
part
can
be
scheduled
can
be
scheduled
on
this
particular
node.
Now
we
are
restricting
the
pods
from
entering
the
nodes,
but
we
are
not
saying
that
any
of
the
pod
with
this
particular
configuration
has
to
or
will
definitely
come
to
this
node.
It
has
the
toleration
if
the
scheduler
picks
node
and
test
against
the
teens
and
toleration.
This
will
satisfy
and
will
be
scheduled,
but
there
can
be
a
scenario
where
you
have
where
you
have
a
pod
and
you
have
multiple
nodes
so
and
the
sorry
we
already
made
this.
A
So
you
have
a
you,
have
you
have
a
pod
over
here
and
you
have
multiple
nodes
now.
This
particular
part
is
having
a
toleration
against
this
node,
but
these
two
nodes
do
not
have
any
taints
itself,
so
the
part
can
be
scheduled
here
as
well.
So
if
we
want
to
schedule
specifically
on
a
particular
node,
then
we
define
node
affinity.
A
Then
we
define
node
affinity.
Now
we
want
it
to
be
scheduled
on
a
particular
node.
We
want
to
be
scheduled
to
a
particular
node.
Then
we
specify
node
affinity.
This
particular
scenario
is:
we
are
just
telling
the
node
that
you
will
only
accept
the
pods
which
have
the
toleration
to
this
particular
taint.
You
will
only
accept
the
pods
which
have
the
toleration
to
this
particular
taint.
If
not,
then
do
not
accept
if
any
part
of
it
toleration
comes
to.
A
You
then
accept,
but
that
part
can
also
go
to
some
other
nodes
without
any
toleration
which
is
also
fine.
So
but
we
are
restricting
the
parts
we
should
use
on
the
node
and
affinity.
We
are
telling
the
part
that
we
should
you
learn
a
specific
set
of
nodes
or
a
specific
group
of
nodes
that
we
have
defined
with
r
with
with
us.
A
So
with
that,
I
think
now
that
is
clear.
Few
other
things
on
the
operator,
so
there
are
two
operators
exists
and
equal
now
in
equal
by
default.
Obviously
it's
equal
and
when
you
specify
equal
or
non-specified,
you
have
to
provide
a
value,
so
there
should
be
a
value
which
is
equal
to
and
exists
is
if,
if
it
just
exists,
so
if
that,
if
the
name
just
exist
on
the
node,
then
also
you
tolerate
that.
Then
then
also
the
part
can
be
scheduled,
so
exist,
no
value
is
required.
A
Now
there
are
three
effects,
so
this
is
the
effect
and
it
is
no
schedule,
it
is
prefer
no
schedule
and
then
it
is
no
executed.
So
no
schedule
is,
please
do
not
schedule
the
pod.
Please
do
not
schedule
the
pod
that
do
not
have
the
toleration
for
the
state
do
not
schedule
the
part
that
don't
have
the
toleration
for
this
state
prefer
not
to
schedule.
A
A
That
means
in
no
schedule,
if
you,
if
you
have
a
so
this
is
node
one
and
it
has
two
ports
running
already.
Now
you
apply
a
taint
of
no
schedule
on
this
particular
node.
These
two
pods
will
still
be
running,
even
if
they
don't
have
the
toleration.
A
Now
you
don't
put
the
no
schedule
one,
but
you
put
the
no
execute
one
as
soon
as
you
put
the
toleration.
Sorry,
the
taint
on
the
node,
with
the
effect
of
no
execute
the
pods
which
are
already
running
and
not
having
the
tolerations
for
that
tenth
will
be
evicted,
so
they
will
be
evicted
from
the
node.
So
that
is
the
difference
between
no
schedule
no
execute.
So
you
have
so
right
now,
till
now.
What
we
have
learned
is
we
have
attained.
A
We
have
no,
definitely
where
we
can
define
like
we
can
you
know,
or
we
can
supply
to
information
to
the
pod
so
that
they
can
be
scheduled
on
specific
nodes.
Second,
is
we
have
taints
and
toleration
so
taints
are
applied
on
the
nodes.
Teams
are
sorry,
taints
are
applied
on
the
nodes
and
we
tell
them
the
like
any
pod.
Without
any
toleration
should
not
be
entering
the
node
and
pods
sorry,
toleration
is
applied
on
the
pods,
so
pods
we
specify
the
toleration.
A
Okay
you
this
particular
pod
is
having
the
toleration,
so
it
can
be
scheduled
on
the
nodes,
use
cases
very
important
use
cases
dedicated
nodes.
You
can
have
dedicated
nodes
for
specific
purposes
and
only
pods
which
are
required
or
the
applications
which
are
required
to
run
on
those
dedicated
nodes
should
be
on
those
dedicated
nodes,
so
we'll
be
having
dedicated
nodes,
we'll
be
having
taints
on
those
dedicated
nodes
and
then
the
pods,
which
we
want
to
be
scheduled.
On
that
dedicated
nodes,
we
will
apply
toleration
to
that
should
be
clear
special
hardware.
A
You
can
have
you
know
specialized
hardware
with
more
cpu
and
more
ram,
and
you
want
heavy
applications
to
be.
Should
you
learn
that
nodes
and
not?
Are
there
any
other
applications?
So
we
will
put
the
no
execute
or
no
schedule
label
sorry,
so
you
will
put
up
no
exit,
no
schedule
taint
on
that
particular
node,
and
only
the
pods
memory
hungry
or
cpu
hungry
pods.
We
will
give
the
toleration
in
the
spec
section.
A
And
next
one
is
paint
based
evictions,
so
this
I
already
explained
like
you
can
have
you
can?
Maybe
you
have
changed
or
maybe
some
policy
have
changed
where
you
are
required
to
apply
some
paint
on
the
node,
and
you
also
want
to
effect
any
other
part
on
that
particular
node,
which
is
not
following
the
toleration,
so
you
will
be
putting
no
executor
over
there
now.
You
must
have
wondered
like
whenever
you
set
up
like
I,
I
showed
you
the
setup
right
of
of
qadm
cube,
adm,
plus
container
d,
so
very
simple
setup.
A
I
I
took
like
four
instances
from
sibo
and
then
ran
each
of
the
commands
from
the
gist
that
I've
shown
previously
I'll.
I
can
again
share
the
link,
no
issues
with
that,
and
then
you
will
be
getting
a
four
node
cluster
where
one
is
control,
plane
and
three
are
the
workload
where
your
workload
actually
runs.
A
Now
you
must
have
wondered
like
why
my
pod
doesn't
get
scheduled
on
the
control
plane
node.
Why
does
it
not?
Why
do
the
pods
do
not
get
scheduled
on
the
control
plane?
Node?
There
are
some
other
things
which
are
also
there,
and
there
is
one
one
extra
thing
that
you
can
define
here,
which
is
called
toleration
seconds,
toleration,
duration
or
toleration.
Second,
something
like
that
I'll
confirm
just
after
we
close
this
presentation.
A
So
that
means,
if
you
specify
example,
no
execute
so
that
will
obviously
no
execute
will
evict
this
spot.
But
if
you
have
the
seconds
defined
over
here,
like
3600
seconds
or
some
seconds,
then
those
pod
will
be
still
running
for
this
particular
duration
and
then
they'll
be
evicted.
So
it
is
helpful
in
some
scenarios.
A
Okay,
so
I
was
talking
about
the
default
taints,
so
the
node.
So
this
is
this
small
piece
of
snippet
is
from
the
docs.
I
will
show
you
where
the
docks
are.
The
node
controller
automatically
retains
a
node
when
certain
conditions
are
true.
The
following
date:
states
are
built
in
so
kubernetes.I
are
not
not
ready,
so
node
is
not
ready.
This
corresponds
to
node
condition
ready
being
false,
so
this
is
automatically
added
by
the
node
controller,
and
then
you
have
your.
A
There
is
a
no
schedule
on
the
control
plane
as
well.
That
is
put
when
you
initialize
the
cluster.
I
will
show
that
as
well
when
we
move
to
the
demo
section
and
we
have
the
unreachable,
we
have
the
memory
pressure.
Node
has
a
memory
pressure.
Then
this
state
is
added.
A
node
has
a
disk
pressure.
This
state
is
added
known
as
the
pid
pressure.
Distance
is
added
networks,
unreachable
distance
added,
so
that
is
taken
care
by
the
node
controller.
There
are
different
set
of
controllers
that
that
are
there.
A
Node
controller
demonstrate
controller
deployment
controller.
So
all
these
controllers,
so
node
control,
is
the
one
which
is
responsible
for
all
these
adding
the
trains
to
the
nodes
I
mean.
Obviously
there
are
other
responsibilities,
but
this
is
one
of
them.
A
So
these
were
the
default
dates,
so
I
hope
the
confusion
between
node
affinity
paints
are
cleared
and
I
hope
the
concept
of
taints
and
toleration
is
clear,
like
what
is
attained.
Paint
is
applied
to
node.
What
is
the
toleration
applied
to
the
pod
when
a
tent
is
applied?
There
is
no
toleration.
The
body
will
not
be
due
when
a
tent
is
applied
and
there
is
a
toleration
which
matches
the
taint.
Then
the
pod
can
be
scheduled
on
that
particular
node.
A
There
is
no
guarantee
if
a
part,
if
you
have
a
node
with
taint
and
portrait
toleration,
then
it
will
definitely
go
to
that
node,
because
there
can
be
other
parts
which
do
not
have
the
any
any
teams,
and
it
can
go
to
that
as
well.
Depending
on
what
scheduler
chooses
so
yeah,
that's
pretty
much
it
from
the
theory
point
of
view.
We
now
move
to
the
demo
section
before
that.
I
will
quickly
show
you
the
obtains
and
alteration
docs.
So
these
are
the
docks.
A
And
please,
if
the
concept
is
clear
with
you,
then
just
say
in
the
chat
that
the
concept
is
clear
because
it
took
a
little
bit
of
time
to
arrange
it
in
this
manner.
So
I
would,
I
would
actually
feel
happy
if
you
say,
like
the
concept
of
dates
and
toleration
that
clear
to
you
now,
even
it
will
be
more
clear
when
you
see
the
demo.
So
it's
okay
and
I
see
a
lot
of
folks
in
the
chat
so
hi
saloni,
hi,
aj
and
hi.
A
Greece
hope
you
are
doing
good
and
please
keep
sharing
all
the
stuff
that
is
happening
interesting
now.
These
are
all
the
concepts
and
obviously
we'll
apply
the
teens
and
we'll
apply
the
toleration
house
and
see
how
it
works.
Actually,
and
these
are
the
tenant
ways,
eviction
that
I
was
telling.
I
just
want
to
show
you
yeah,
so
it
was
toleration
seconds
that
you
can.
A
You
know
define
so
kubernetes
automatically
adds
a
toleration
for
node,
not
ready
and
unreachable
with
300,
unless
you
or
a
controller
set
those
explicitly
and
also
if
you
apply
specifically
the
no
execute
or
taint,
you
can
toleration.
So
you
can,
you
know,
specify
those
toleration
seconds.
Rotation
seconds
is
a
good
thing
to
have
then
yeah.
These
are
node
affinity,
one
so
I'll
paste.
The
link
for
that
as
well.
Node
affinity.
B
A
So
you
can
see
this
is
the
same.
This
is
not
the
same
cluster
that
we
created
interesting.
A
B
B
A
A
So
we
have
like
this
is
the
one
that
we
created
actually
based
on
the
script.
I
can
even
show
you
the
script
once
again,
it's
okay,
so
we
have
a
control
plane.
Node.
We
have
three
worker
nodes.
Whether
parts
are
scheduled
there.
That
obviously,
can
be
some
of
the
schedule
pods,
which
are
okay,
I'll.
Remove
this
particular
thing:
qcdl
delete
or
iphone
iphone.
B
A
A
So
what
we
do
is
if
we
want
to
find
like
paint
from
all
the
nodes
of
the
simple
trick
that
I
use
is
skips.
It
will
get
nodes,
so
I
get
so
I
get
this
order.
A
I
get
this
order
now.
What
I'll
do
is
I'll?
Do
a
cube,
ctl
describe
node
and
grep
for
paint.
It
will
give
me
the
same
order,
so
this
will
be
for
the
control
plane.
This
will
be
for
the
worker
one.
This
will
be
for
the
worker
2,
and
this
will
be
for
the
worker
3,
and
what
we
can
do
is:
let's
have
a
pod.
I
already
have
a
pod
spec.
So
let's
see
the
port
spec,
we
have
a
pod
spec
which
do
not
have
any
toleration
which
do
not
have
any
toleration.
A
So
what
we'll
do
is
we'll
first
paint
the
third
one,
because
there
is
no
tainting
and
we'll
try
to
see
like
how
to
paint
the
node.
So
the
command
is
very
simple,
cube,
ctl
paint,
then
node,
then
the
node
name.
Then
what
paint
we
want
to
imply
apply?
Let's
say
science
search
magic
and
with
the
effect
off,
we
can
choose
the
same
effect.
That
is.
A
Command,
which
was
this
so
we
should
see
another
one
appearing
in
the
last
one,
so
this
is
for
the
control
plane
and
I
told
you
like
the
control
plane
already
comes
with
a
node.
So
this
is
the
default
paint
that
comes
widely
during
the
installation
of
the
cluster.
So
we
have
the
node
role
kubernetes.
I
o
master
no
schedule
so,
which
means
that
no
none
of
the
parts
will
be
shown
on
the
master
node,
and
it
should
actually
be
the
case
in
in
reality.
A
Also,
you
should
not
schedule
any
nodes
to
the
master
node
so,
which
is
a
good
thing
you
should
not,
and
next
is.
These
are
the
ones
that
we
have
manually
applied
now
there
are
paints
on
all
the
nodes,
and
if
we
have
a
pod,
it
should
not
be
scheduled.
So,
let's
see
so
cube,
ctl
apply,
hyphen,
f,
por,
dot,
yaml
odd
is
created,
get
thoughts,
support
spending.
A
What
is
spending
cube,
ctl
describe,
or
it
says
there
is
no
no
node
available,
failed
scheduling,
so
one
node
has
attained
foo
bar
that
part
didn't
tolerate.
One
node
hesitate
for
double
o
bar.
That
also
is
then
told
rate
one
node
has
had
a
taint
of
master.
That
is
also
didn't
tolerate
and
another
one
had
so
it's
magic.
That
also
does
not
tolerate
it.
So
we
have
four
nodes.
All
the
four
are,
you
know
tainted
what
to
do
now.
What
can
I
do
so?
It's
very
difficult
right.
A
So
what
we'll
do
is
we
will?
I
have
another
pod
spec.
So
let's
see
that
we'll
add
a
toleration,
so
pod
two
dot
camel.
A
So
this
is
the
one,
and
this
is
the
section
in
the
specs,
so
you
can
specify
the
tolerations
in
the
pod
spec
section.
A
So
you
have
your
key
foo
and
the
operator
is
equal.
The
value
is
far
effect
is
no
schedule,
so
it
should
be
tolerating
this
particular
node,
which
has
a
taint
of
foo
bar.
A
A
See
qct
get
ford's
hyphen
wide
absolutely
so
it
went
on
worker
one,
so
it
tolerated.
So
it
had
the
toleration
that
it
can
be
scheduled
on
a
node
which
has
a
taint
of
fou
equal
to
bar
another
interesting
thing.
So
we
can
see
that
we
have
a
few
pods
which
are
like
worker
one
and
on
worker
one.
So
what
we'll
do
is
we
will
see
another
scenario
of
the
eviction
scenario,
so
we
will
put
no
execute
how
to
do
that.
First,
we
let's
remove
the
tent,
so
cube.
Ctl.
A
B
A
A
I
hope
now
you
are
able
to
understand
the
concept.
You
know
how
you
can
apply
the
names,
how
you
can
remove
the
rains,
how
you
can
apply
the
tolerations
on
the
pod.
A
How
you
can
apply
the
tolerations
on
the
pod.
How
you
can
you
know,
apply
the
no
execute
one
and
see
the
eviction
so
how
the
eviction
happens.
So
I
think
all
these
scenarios
we
have
covered
and
that
that
was
the
main
goal
to
you
know
make
you
understand
how
the
pains
and
the
toleration
the
eviction
process
they
actually
work.
So
most
of
the
people
get
confused
in
this.
I
hope
this
particular
stream
helps
you
to
understand
the
taints
and
the
toleration
concept
in
detail
and
for
more
reference.
A
Obviously,
you
can
go
to
the
documentation,
but
I
I
have
seen
I
have
gone
through
the
documentation
and
I
have
seen
like
the
documentation
itself
talks
about
all
these
concepts,
so
the
preferred
no
schedule
and
the
no
schedule
and
the
no
execute,
and
then
you
have
these
are
the
effects.
And
then
you
have
your
what
you
call
the
operators
which
are
exist
and
the
equal.
So
that
can
be
that
that
is
there,
but
example
wise.
I
think
that
that
should
clarify
some
bits.
B
A
Yep,
so
that
was
pretty
much
it
that
I
had
for
today
and
thank
you
so
much
for
tuning
in
and
the
last
section
is
like
the
the
certification
voucher
thing.
So
I
think
two
people
who
are
active
just
just
want
to
ask
garish
like
did
he
get
the
coupon
previously
because
I
don't
want
to
give
away.
You
know
two
coupons
to
the
same
person,
because
actually
it
would
be.
You
know,
unfair
for
other
folks,
new
folks
who
have
been
joining
so
girish.
A
If
you
have
got
the
coupon
before
please
drop
in
the
drop,
a
message
in
the
chat
that
you
have
called
the
coupon
before
and
so
that
I
can,
you
know,
announce
them
announce
the
winner
in
the
meanwhile.
So,
like
I
told
you
before
cloud
native
tv
is,
you
know
there
are
different
shoes
that
runs
throughout
the
week
with
all
the
you
know
with
everything,
and
I
want
to
plug
like
this
show
as
well
say:
imparter.com
youtube.
A
If
you
want
like
in-depth
videos
of
cloud
native
technologies,
then
you
can
subscribe
to
my
channel,
which
is
ambarik.com
youtube.
I
don't
know
youtube
channel
where
I
keep
on
doing
live
streams
with
the
you
know.
Other
folks,
in
the
cloud
industry
on
different
topics,
also
follow
the
cloud
native
tv
because
we
have
shows
running
each
and
every
day,
so
it's
not
only
my
show,
which
is
bi-weekly.
A
Obviously
so
you
have
to
tune
in,
but
there
are
shows
which
are
running
every
day,
so
this
coming
friday,
which
is
tomorrow,
there's
a
show
spotlight,
live
with
grpc,
where
we'll
be
having
april
from
google
to
discuss
about
the
project.
So
I
think
that's
that's
pretty
much,
that's
what
that
would
be.
That
would
be
really
cool.
So
you
there
is
also
like
the
registration
for
kubecon
crowded
con
north
america.
2021
is
open
for
in-person
and
virtual,
so
explore
you
know
all
the
registration
options.
A
I'll
drop
the
link
in
the
chat
for
that
as
well
and
yeah.
Also
cloud
native
tv
is
actually
now
on
cncf
store.
So
I'm
really
really
happy
that
there
is
a
you
know,
a
decal
pack
for,
for
my
show
as
well,
so
make
sure
you,
you
know
check
that
out
and
you
get
the
cncf
search
magic
sticker.
So
you
can
see,
go
on
store.cncf.io
get
all
the
collectibles
for
all
the
shows
which
are
happening
on
cloud
native
tv,
so
make
sure
you
to
subscribe
that
button.
A
So
since
gerich
has
not
responded,
so
I'm
not
sure,
but
should
I
have
a
doubt
and
anyways
for
the
folks
who
have
joined
first.
So
I'm
giving
based
on
that-
and
I
saw
some
of
the
tweets
as
well
so
for
today
I'll
be
giving
out
the
cncf
certification,
50
discount
coupon
to
aj
and
saloni.
So
aj.
Please
do
reach
out
to
me
on
twitter
because
I
don't
know
like
you
know
how
to
contact
you.
So
this
is
my
twitter
handle,
so
you
can
see
on
the
screen.
A
Sayam
partner
and
saloni.
Please
reach
out
to
me
on
twitter
and
I'll
hand
over
to
you.
50
percent
is
gone
coupon
on
the
certifications
and
thank
you
for
tuning
in
see
you
next
time.
This
video
will
be
uploaded
on
youtube
as
well
after
10,
10
or
12
days,
or
something
like
that
till
the
time
it
stays
on
twitch
and
share
it
with
friends
so
that
you
can
have
you
know
all
the
knowledge
about
the
certification
and
the
concepts
I'll
try
to
simplify
them
and
I'll
try
to
get.
You
know.
A
We
also
have
more
guests
coming
up
on
the
next
shows
and
we'll
talk
about
some
of
the
other
modules
like
the
troubleshooting
one
and
the
volumes
one,
because
those
are
also,
I
think,
very
much
confusing
for
some
of
the
folks,
and
I
want
to
like
explain
that
explain
them
in
a
way
like
you,
you
understand
it
from
certification,
point
of
view
and
understand
it
from
the
from
your
the
regular
working
point
of
view
as
well.
So
with
that,
I
hope
you
enjoyed
today's
show
with
set
of
certifications.
A
We
talked
about
more
dfinity,
taints
and
alterations,
and
we
choose
vacuum
boys.
Thank
you
for
joining.
In
always
try
to
be
interactive,
follow
cloud90tv,
enjoy
the
other
shows
and
thank
you
so
much
bye.