►
From YouTube: Kubernetes SIG Scheduling Meeting 2018-06-28
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
guys
and
welcome
to
city
scheduling,
meeting
I'm
happy
to
see
Klaus
here
as
well.
So,
as
you
guys
know,
111
kubernetes
111
is
out.
We
have
been
able
to
get
most
of
our
features
with
111,
particularly
priority
and
preemption
is
now
out
with
111
and
is
enabled
by
default.
Some
of
you
folks
are
aware
that
one
of
the
features
that
we
really
wanted
to
ship
with
priority
and
preemption
was
warning
priority
in
resource
code,
and
that
feature
is
built,
but
due
to
some
concerns
at
the
very
last
minute
of
the
for
the
code.
A
Freeze
it
its
feature
gated.
So
because
of
that,
we
cannot
really
use
that
feature
to
limit
people
from
creating
pods
at
the
highest
priority
levels.
Basically,
user
and
user
in
a
cluster
could
possibly
go
and
create
a
bunch
of
pods
in
a
cluster
with
a
system.
Now
it's
critical
and
if
that
happens,
and
if
the
cluster
is
on
the
resource
pressure,
those
kind
of
nodes
can
preempt
any
other
node
in
a
cluster,
including
some
of
the
nodes
that
run
as
like
some
of
the
critical
know.
A
It's
like
you,
DNS,
that
run,
which
is
slightly
lower
priority,
which
is
called
system
cluster
protocol.
So
that's
that's
a
big
concern.
As
a
result,
we
are
trying
to
mitigate
the
problem
by
limiting
those
or
high
very
high
priority
classes.
Basically,
those
two
priority
classes
to
some
configurable
set
of
namespaces
only
and
by
default
it's
only
it's
gonna
be
only
in
cube
system,
so
users
cannot
create
pods
with
those
priorities
in
other
namespaces,
and
our
current
code
of
mechanism
has
a
way
of
limiting
users
from
creating
parts
inside
a
namespaces.
A
So
it's
going
to
be
very
easy
for
an
admin
to
set
coda
or
no
quota,
basically
for
most
the
users
of
the
cluster
and
preventing
them
from
creating
any
pods
in
cube
systems.
In
fact,
it's
it's
not
recommended
at
all
to
create
any
part
in
cube
system
namespace
any
rate,
but
in
order
to
prevent
abuse,
admins
can
enforce
it
as
well.
So
we.
A
That
we
can,
you
can
ship
this
change
of
it
111one
and
basically
our
next
darts
release
and
I'm,
using
a
ravi,
a
novice
to
basically
build
a
feature
and
review
it.
I
have
built
the
first
early
version
of
it,
which
is
basically
a
limiting
pass
to
only
cube
system.
Namespace
I
have
to
work
on
the
tests
to
make
sure
that
our
tests
pass
because,
right
now
our
end-to-end
tests
tend
to
create
critical
pods
in
all
sort
of
namespaces.
So
with
that,
hopefully
we
can
match
with
that
change.
A
B
A
Actually,
a
good
question
I
was
I
was
thinking
about
it
last
night
as
well.
I
felt
like
we
don't
really
need
to
keep
it
that
way
and
although
it's
gonna
be
a
change
of
behavior,
but
since
we
are
removing
a
limitation,
you
know,
after
of
course,
this
resource
quarter
goes
to
beta.
Since
we
are,
if
we,
if
we
decide
to
remove
this
limitation,
it's
not
gonna,
be
a
breaking
change
in
terms
of
like
backward
compatibility.
A
A
Change
or
fix
yeah,
that's
to
be
decided.
I
would
like
to
basically
hear
the
ideas
from
the
API
folks
as
well,
including
Jordan,
Kate
and
Jarek,
and
some
other
folks
to
see
what
we
should
be
doing
at
that
point.
But
I
don't
think
it's
necessary
to
keep
it
easy
anyway.
It's
good
because
it
kind
of
like
makes
things
a
little
easier
for
admins.
A
B
Yeah
sure
so
we
also
have
the
same
concerns
like,
and
we
also
feel
that
it
would
be
easier
for
cluster
admins.
If
we
have
this
feature
in
place,
instead
of
using
whiskers
quota
or
policy
based,
nothing
I
mean
at
some
point.
Often
we
may
have
to
switch,
but
I
think
at
this
point
of
time.
This
this
is
better
is
what
we
think
has
been.
A
At
some
point
actually,
some
point
in
the
past
I
had
already
added
this
kink
in
in
in
our
admission
controller,
but
we
decided
to
remove
it
in
during
the
code
review,
but
anyway
it
doesn't
matter.
We
were
adding
it
back,
it's
it's.
Hopefully
he
can
hopefully
help
right
like
going
with
it.
Making
the
default
configuration
a
little
bit
easier
to
use
for
for
most
people
yeah.
So
are
there
item
any
other
question
by
the
way,
so
another
item
on
the
agenda
that
I
added
was
items
for
112.
A
Basically,
we
have
a
bunch
of
items
in
our
spreadsheet
this
virtually
the
spreadsheet
is
linked
to
the
same
document
that
we
have
for
that
basically
shows
our
agenda
for
our
weekly
meetings
in
the
same
spreadsheet,
I
have
listed
a
bunch
of
features
for
112.
If
you
have
any
other
features
that
you
would
like
to
add,
please
go
and
comment
on
a
document.
As
I
said,
the
document
is
linked
to
the
dock,
to
the
G
doc.
Will
dock
that
is
available
in
the
invite
meeting
advice?
A
So
if
you
have
any
other
features
that
you
would
like
to
add,
please
go
ahead
and
comment
on
that
spreadsheet.
We
have
a
bunch
of
items.
Last
week
meeting
we
talked
about
some
of
those
and
since
Klaus
is
here.
I
would
like
to
hear
an
update
about
the
gang
scheduling
if
you
Klaus
any
updates
for
us.
Yes,.
C
Yes,
for
the
counseling
we
a
sink
away.
How
is
that
that
we
are
going
to
use
counts,
delving
out
of
car
and
by
this,
the
RT
and
I?
Think
as
the
collaborator
will
be
the
base
to
peel
that
feature,
and
so
I
upgrade
a
true
class
of
positives
and
document,
something
about
API
and
something
about
how
about
the
cue
controller
as
we
are
going
to
out
of
out
of
copper.
So
some
implementation,
part
about
the
scatter,
also
changed
I,
will
share
the
link
later
after
the
meeting
to
the
you
CEO.
C
So
everyone
can
give
some
comments.
Albany's,
maybe
is
some
some
case
you
want
to
cover
in
the
counseling
and
for
the
pine
I
think
I'd
like
to
gather
alpha
in
the
1-1
dog
chow
yeah.
Yes,
but
you
know,
forecast
calendars.
They
were
O'connor
kids
for
them.
How
about
resource
utilization
when
they
reserve
some
resources
to
make
constantly
requirement
yeah
the
for
such
can
Oh
food
corner
case
on
the
performance
improvement,
maybe
maybe
as
a
follow-up
I,
think
that
will
be
nice
to
have
but
item.
So
maybe
this
not
cannot
catch
up
with
even
one
released.
C
So
in
the
in
the
one
thought
well
I'm
going
to
provide
the
RFID
traffic
comes
guarantee
for
the
other
feature,
for
example
preemption
backfill
on
some
other
on
one
feature:
that's
where
we
necessarily
improvements
to
improve
the
resource
utilization,
yeah,
okay,
so
I'm
sure
that
Inc
and
chooses
to
the
Google
Group
we
honor
to
the
issue.
So
everyone
can
have
some
comments
and
share.
That's
right
here,
I'd
like
to
get
it.
A
D
A
C
If
there
is
some
other
people
can't
from
this,
one,
I
can
reveal
another
proof
that
can
be
the
approver
for
this
Hydra
I
think
most
most
efficient
here
then
in
the
1.0,
and
we
already
face
the
mother
is
in
here
and
I.
Think
we
may
do.
Some
ties
do
some
more
some
case
for
that
small
task
more
unit.
Has
our
integration
has
for
this
one,
that's
true
enough.
I
already.
C
A
Go
so
it
will
be
great
if
you
can
label
that
issue
it
Help
Wanted,
so
they
find
it
more
easily.
Please
go
ahead
and
learn
if
people
in
this
meeting
are
interested
in
taking
that
issue,
you
can
and
say
something
now.
Okay,
sure,
thank
you.
So
Harry
is
here
Harry.
Do
you
have
any
updates
for
us
for
equivalents,
cash
or
image,
low
quality,
priority
function.
A
D
The
for
the
image
locality
priority
and
the
design
has
been.
You
know
we
have
richest
women
that
we
can
consider
the
notes,
distribution
when
calculating
the
image
of
activity
score
and
see
were
willing
to
do
the
implementation,
so
I
would
expect
a
standard
per
request
makes
it
next
Oh
next
time.
Next
week,
yeah.