►
From YouTube: Kubernetes SIG CLI 20200722 - bug scrub
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
Good
morning,
good
evening,
good
afternoon,
depending
on
where
you
are
today
is
july,
22nd-
and
this
is
our
monthly
sexy-
live
buck
scrub.
Our
host
today
is
eddie,
welcome,
eddie
and
take
it
away
from
here.
A
I've
been
doing
that
one
for
for
so
long
that
I
kind
of
got
gotten
used
to
it
and
I
I
enjoyed
doing
it
at
the
beginning.
So
it's
our
trademark.
B
Cool
well
thanks
everyone
for
joining.
I
just
dropped
this
link
into
the
chat.
This
is
one
of
those
tools
that
we've
been
talking
about
called
triage
party.
We
went
through
this
cue
last
time
and
it
worked
pretty
well,
so
I
think
we're
gonna
give
it
a
shot
today,
but
we're
still
trying
this
out.
So
if
you
have
any
feedback,
let
us
know
and
we
can
tweak
it.
This
is
basically
pulling
all
the
github
issues
and
categorizing
them
into
different
sections.
B
This
section
right
here
is
the
unprioritized
issues
older
than
seven
days
and
when
I've
gone
and
I've
just
sorted
this
by
when
the
issue
was
last
responded
to,
and
so
once
an
issue
is
labeled
as
priority
or
triage.
It
should
get
out
of
this
queue.
So
I
figured
we'll
just
work
backwards
from
this
and
see
where
that
takes
us.
B
B
A
A
B
Okay,
do
you
want
to
type
that
up
real,
quick
and
close
it?
Oh
yeah
I'll!
Do
that
one,
okay,
that
one's
too
old
for
me
to
close.
C
Okay,
so
so
there
may
be
just
as
with
cryptocopy,
there
may
be
security
issues
as
well.
Is
that
correct.
A
I
don't
like
six
months
period
of
time
when
we
were
fixing
one
one
issue
and
that
uncovered
additional
ones,
the
majority
of
which
were
related
to
supporting
a
link
so
yeah
we
try
to
copy
files.
C
A
There
is
a
proposal
there
is
a
cap
describing
this
issue,
this
problem,
oh
I'm,
I'm
I'll
make
sure
to
to
link
to
that
particular
enhancements
describing
all
of
them.
If
I
remember
correctly,
it
had
all
the
links
to
all
of
the
cdes
that
we
fixed
back
then
so
yeah,
that's
a
that's
a
very
good
point.
C
B
A
I'm
I'm
not
100
sure
that
the
weight
command
does
support
multiple
resources,
but
it
could
be
something
that
we
might
and
having
a
more
generic
approach
to
waiting
for
a
particular
condition
is
where
we,
where
we
want
the
weight
command
to
fill
in
the
gap.
C
C
Yeah,
so
obviously
api
server,
only
you
can
only
have
you
can't
really
have
transactions,
you
can
only
really
send,
or
you
know,
apply
one
resource,
not
knowing
what
whether
or
not
the
other
ones
are
going
to
succeed.
I
don't
see
any
other
commands
where
we,
where
we're
working
with
that.
That's
not
true
of
many
other
resources.
A
B
E
You
don't
I
I
started
creating
one.
I
pulled
it
back.
Let's
see
which
number
is
this
I'm
following
along
on
my
other
screen,
five,
seven.
D
E
Yeah,
so
that
that
actually,
why
is
this
a
different
issue?
Oh
because
yeah,
so
we
get
we'll
get
fish
tab
completion
for
free
if,
if
we
can
move
to
the
go
based
completions
in
the
latest
version
of
cobra,
when
when
I
looked
at
doing
that,
I
did
have
a
pr
to
do
that.
But
then
somebody
else
I
think
it
was
maybe
mark
from
the
issue.
E
Tab
issue
is
pointed
out
that
there
were
some
issues
with
z,
shell
completion,
and
so
it's
there's
a
lot
of
moving
pieces
there
and
trying
to
get.
I
certainly
didn't
want
to
disrupt
seashell
completion,
because
I
know
a
lot
of
people
have
asked
for
things
to
work
in
that
for
a
long
time
and
finally,
we
got
it
into
a
good
spot,
so
I
don't
want
to
mess
up
bash
or
z
shell.
So
anyway
I
pulled
it
back
and
I
and
somebody
else
I
think
it
was
knight
42,
said.
D
F
Did
you
can
ask,
did
you
use
the
same?
Go
bash
completion,
libraries
that
customize
uses.
F
It
might
be
worth
just
doing
an
insanity
check,
making
sure
that
we
just
choose
one
instead
of
having
you
know,
trying
to
support
two
bugs
or
trying
to
support
like
two
different
libraries
with
different
sets
of
bugs
and
then
and
then,
if,
if
they're
different,
we
can
pick
try
and
evaluate
which
one's
better
and
find
the
link
for
that
now.
E
Does
customize
use
what
what
cobra
1.0
has
well
I'll
take
a
look
at
customize
it
and
and
see.
F
Uses
pose
neurocomplete,
send
you
a
link,
it
doesn't
use
the
cobra
ones.
We
looked
at
them,
but
we
chose
not
to
for
a
couple
reasons:
yeah.
Why
don't
you
follow
up
with
me
offline?
We
can
figure
out
what
the
preferred
approach
is.
E
The
question
on
the
other
one,
the
official
completion-
I
guess
the
other
issue
doesn't
specifically
address
fish
tab.
I
don't
know.
Okay.
E
Guess
I'm
I
would
be
concerned
somebody
would
who
apparently
people
really
want
fish
tab
completion
and
they
might
see
that
and
come
back
and
say
why'd.
You
close
that,
but
it's
up
to
you.
F
E
B
B
Okay,
I'll
leave
it
for
now.
I'm
gonna
prioritize
it.
So
it
gets
out
of
this
queue,
though
I
can't
spell
priorities
today.
E
E
F
B
A
Fails
that
looks
like
a
customized
block
and
since
we're
having
we're
using
very
outdated
version
of
customize,
it
probably
can
even
be
already
fixed
so
I'll
leave
there
a
comment
that
I'm
suggesting
to
use
a
newer
customized,
because
the
one
and
cute
cuddle
is
pretty
outdated.
B
A
A
D
E
A
Sean,
I
think
this
is
just
for
tracking
and
making
the
the
information
what
happens
with
convert
public,
it's
going
to
happen,
hopefully
in
120
that
we
will
convert
it
to
a
plug-in.
A
C
Yeah,
so
that,
just
as
just
to
give
a
little
bit
of
context
for
that,
it's
going
to
be
just
pulling
the
package
command
convert
code
and
putting
it
in
under
command
some,
you
know
foo
or
convert,
maybe
with
a
k.
C
All
of
that
code
has
to
be
out
of
coup
control
and
and
compiled
into
its
own
binary.
It's
actually
there's
not
a
whole
lot.
A
A
It
requires
the
internal
apis
that
will
will
never
be
extracted
from
the
main
kubernetes
repository
and
so
for
it
to
work
properly.
It
has
to
it.
It
will
be
always
strictly
connected
with
the
main
kubernetes
repo,
and
so
we
will
just
build
build
it
as
a
as
a
plugin,
so
people
interested
in
having
them
will
have
to
just
install
the
plugin,
we'll
we'll
try
to
make
sure
that
it
is
part
of
the
it
is.
It
is
published
in
crew
for
ease
of
use.
B
B
E
A
A
Which
will
have
this
semantics
so
maybe
worthy?
Also
a
change
in
the
in
the
code
as
well.
H
I
B
I
What's
your
github
username,
it's
your
best
j-I-b-u-s!
Actually,
I
don't
think
I
can
assign,
if
you're
not
in
the
org.
If
you
just
go
on
there
and.
I
C
Thank
you
for
volunteering
and,
if
you
need
to,
if
you
need
some
help
or
guidance,
go
ahead
and
reach
out
to
to
one
of
us
on
slack,
I'm
shawn
s3.
C
Thank
you,
slack
is
definitely
the
the
way
to
go.
Emails
are
more
difficult
to
to
make.
C
Yeah,
so
we're
we're
in
the
middle
of
and
very
close
to
updating,
customizing
coupe
control.
F
I
just
I
just
right
now:
I've
been
writing
an
entry
in
the
docs
back
as
a
pr,
as
I
saw
this
issue,
and
so
I'll
have
a
pr
out
in
a
second
and
then
we
can
just
post
that
to
the
issue.
C
So
so
this
particular
issue
is
connected
with
multiple
other
kobe
cuddle,
customized
version
issues.
I
believe
we
all
hopefully
will
all
get
them
pointed
to
just
one.
C
So
818
looks
like
it's
also
a
same
version
of
this,
so
is
so.
Are
we
going
to
stick
with
the
797
version
I'll
point
the
818
to.
F
797
that
sounds
good,
and
then
you
can
point
them
at
the
docks
at
the
back
in
a.
F
B
B
C
Yeah
those
those
two
may
just
be:
are
they
incompatible
so
prune
uses
a
label
in
order
to
specify
what
the
previously
applied
set
was,
and
maybe
some
gbk's
yeah
with
that
prune
white.
C
C
So
so
I'll
just
assign
this
to
me,
I've
been
digging
into
prune,
and
so
all,
if
you
could
just
assign
that
to
me
I'll
I'll.
B
F
A
I
wouldn't
go
as
far
as
built
outside
of
kubernetes,
but
I'm
hoping
that
120
will
be
when
we
will
be
entirely
in
staging
so
theoretically,
yes,
it
should
be
built
out
of
that.
The
the
pr
that
I
learned
some
time
ago
about
library
go
for
for
shared
libraries
when
this
as
soon
as
this
lands,
we
need
to
move
the
author
reconcile
function,
shared
functionality
and
then
we're
we're
ready
with
with
moving
quad
reconcile
as
well.
So,
like
I
said.
F
So
120
is
roughly
when
we
could,
when
the
code
could
be
built
outside
of
kubernetes
yeah,
but
we
still
need
to
figure
out
the
process
right.
Yeah.
A
Yeah
once
we
once
we
want
to
have
one
thing
at
a
time,
once
we
have
cucara
in
the
staging
repo,
we
can
start
knocking
on
the
doors
of
the
release
team
and
try
to
figure
out
how
to
build,
keep
cuddle
the
main
reaper
from
cape
canaverico,
and
only
then
we
will
cut
the
link
cool.
C
B
G
Too,
it's.
D
A
A
One
is
reporting
differently
and
the
other
one
is
loading
differently,
but
overall,
yes,
since
we
would
be
interested
introducing
additional
environment
variable
that
will
have
to
be
supported
over
there,
and
this
is
part
of
the
client
client
go.
It
will
be
a
crosstic
effort,
so
it
will
be
both
kubecon
6cli
and
sig
api
missionary,
because
that
would
be
a
change
in
for
them
as
well.
A
Yeah,
that's
a
fire,
that's
a
very
approach
because
it's
it's
a
bigger
topic.
B
A
It
right
no,
no,
we
only,
we
only
remove
the
functionality
of
creating
the
generators
other
than
yeah
anything
other
than
pods,
so
cucumber
will
only
create
pod
and
which
is
perfect
for
debugging
and
diagnostics.
A
F
I
think
folks
are
just
looking
for
a
command
that
allows
them
to
you
know
debug,
better
or
I've
heard
for
run
like
it
was
about
teaching
people
kubernetes,
and
they
like
just
wanted
a
simple
way
of
teaching
people
how
kubernetes
works
and
so
like
it
might
be
worth
considering
just
saying:
okay,
let's
build
a
separate
command
where,
like
for
debugging
or
teaching
people
to
use
competitors
or
that
sort
of
thing
you
can
kind
of
go
nuts
with
features,
and
we
don't
offer
a
version,
skew
policy
for
it
or
any
of
that
sort
of
thing.
F
So
as
a
way
of
kind
of
pushing
back
and
saying
like
no
we're
not
going
to
expand
the
functionality
of
run
because
of
you
know
those
reasons
of
the
amount
of
burden
it
puts
on
us
for
maintaining,
but
that
here's
a
way
that
you
can
still
get
what
you
want.
C
C
C
Yeah,
I'm
just
curious,
I'm
just
curious
what
what
the
to
make
sure
that
we,
the
that's
actually
what
we
decided
was
that
we're
not
gonna
add
to
the
run
commands
and
if
that's
the
case,
then
maybe
we
want
to
like
keep
that
as
a
policy
for
any
other
potential
issues
that
come
up
like
this.
A
F
A
We
will
be
again
at
the
same
point
where
we,
where
we
were
a
couple
months
back.
We
still
I
mean
I
just
looked
at
the
cube.
Color
run
help.
A
It
is
two
pages
long
and
one
page
is
the
amount
in
one
page
and
I
have
pretty
small
font.
So
that's
not
80
by
20.
That's
a
lot.
A
lot
more
thermal
that
I
have
in
one
entire
page
is
just
options
that
you
can
pass
to
keep
gotta
run
and
the
more
options
there
are,
the
more
confusing
the
commands
are
for
users
to
use,
and
this
is
only
run
itself
flags
and,
if
you
add
the
the
cube
cuddle
flags
that
can
expand
quickly
to
unmanageable
math.
B
The
only
thing
I
was
going
to
say
was
this
seems
like
a
super
reasonable
request,
especially
with
the
real
world
example.
I
I'm
not
pushing
for
it
either
way
right
but
like
if
this
saves
people's
life,
not
not
if
this
saves
people
time
right
like
this
is
extremely
valid
use
case
for
anyone
using
istio.
That
wants
to
do
this,
but
I
totally
get
the
other
end
of
the
spectrum
too.
E
I
would
say
too,
though,
that
I
mean
it's
a
valid
use
case,
but
it
is
also
an
issue
specific
use
case
really
because
it's
just
that
istio
looks
for
that
annotation
and
will
inject
a
sidecar.
If
you
don't
have
that
annotation
right
away
right.
F
F
Entire
patch
functionality
of
overlays
into
control-
and
it
seems
like
just
over
kill
or.
I
B
Yeah,
that's
fair:
okay,
phil
who's.
Responding
to
this
one,
I'm
closing.
A
F
B
A
Yeah,
I'm
inclined
to
say
that
the
request
is
too
generic.
A
But
in
all
honesty
we
are
trying
to
add
the
sound
of
some
of
the
run
command
functionality
back
to
create
commands,
but
these
are
per
request
per
particular
request.
I
don't
want
to
have
a
oh
at
everything
that
was
in
run.
I
want
to
have
a
discussion
per
request,
whether
we
care
about
this
kind
of
functionality,
whether
it
makes
sense
whether
there
are
alternatives
that
we
can
address
them.
B
Okay,
do
you
want
me
to
add
something
to
the
future
topics
for
the
meeting.
C
Okay,
moving
on
should
we
just
document
what
we
said
about
run
in
the
60
live
meeting,
we'll
have
it
in
the
notes
and
in
the
video
and
we'll
we
can
reference
that
whenever
we
turn
down
any
other
changes
to
the
run,
requests.
F
F
Yeah
yeah,
I
I
don't
know
I
mean
I
mean
that
clearly
the
annotations
is
better
than
this
override
nonsense,
but
I
I
think,
like
today,
it's
annotations
and
tomorrow
it's
you
know.
Whatever
labels.
A
F
You
know
labels
labels
are
already
there
resources
yeah,
there's,
there's
labels
already
there,
but
the
annotation
is
the
one
thing
that
isn't
supported
the
labels.
Are
I
don't
know
if
someone
filed
a
pr
I'd
be
inclined
to
accept
it,
but
I
wouldn't
prioritize
it
like
it's.
F
C
B
A
F
A
It's
a
mess,
I
mean
I'm
super
literally,
every
single
pr,
both
in
kubernetes
and
openshift
today
for
me
fails
all
the
resources
are
being
exhausted.
For
me,
I'm
getting
constant
flakes
across
the
board
and
I'm
having
meetings,
since
this
is
like
sixth
or
seventh
hour
of
meetings
for
me
today,
so
yeah
bad
day
very
bad
day,.
H
I
C
Sorry,
real
quick,
yamas
there's
a
a
good
video
that
mache
created
at
the
that
you
can
find
on
slack
for
the
basics
of
coop
cuddle
development,
which
will
significantly
help
you
out
in
your
journey
to
to
write
that
kind
stuff
that
run
stuff.
H
Okay,
all
right
where,
where
about
in
the
slack
channel,
would
I
find
that
in
in
the
six
cli
it's
pinned.
C
H
A
I
can't
remember,
but
in
the
worst
case,
if
you
ping
me
on
slack
I'll
point
you
to
the
right
recording
and
then
we
click
on.
D
A
Message
if
it's
not
independent,
if,
if
it's
not
independent,
all
right
yeah
there
is,
it
is
pinned
check.
Our
check
check
the
code
base
tour
from.
B
It
is
the
only
pin
all
right
yeah,
it's
the
only
pin
all
right.
We
got
eight
minutes
left
8
37
I've
never
heard
of
kind
list
before
as
a
resource.
It's
a.
A
It's
a
internal
thing
that
is
being
extensively
used,
but
it
just
like
brian
explained
each
resource
will
have
a
typed
list
until
you
have
you'll
see
a
pod
list.
Cron
job
list
deployment
list
whatever,
and
the
list
is
a
meta
type
that
is
being
used
only
in
the
code.
B
F
F
F
B
A
If
he
tried
to
maybe
his
issue
was
that
after
he
exact
into
a
pod
and
then
he
looked
back,
he
was
not
able,
but
just
that
just
a
matter
of
setting
the
right
locale.
B
A
Honestly,
I
don't
see
any
other
option,
then,
if,
if
his
company
is
using
men
in
the
middle
proxy,
then
the
only
reasonable
way
is
to
have
the
the
proxy
ca
and
the
ca
certificate
installed.
That's
what
usually
happens
and
I'm
not
seeing
us
adding
some
extra
or
commands
to
bypass
that
kind
of
a
functionality.
A
Also,
it's
a
more
more
of
a
question
for
a
takeoff
than
us.
B
How
much
time
three
minutes
any
of
any
of
these
on
the
list
that
anyone
wanted
to
bring
up
make
sure
we
get
to
it.
C
A
I
want
to
have
a.
I
want
to
have
a
a
user,
be
explicit
about
the
naming,
I'm
worried
if,
if
we
start
naming
them
automatically,
we
might
bump
into
issues
of
oh,
this
name
was
already
used
and
cube.
Cuddle
run
should
be
smart
enough,
not
to
use
the
same
name,
etc,
etc.
No.
F
Maybe
could
we
just
have
like
a
canned
response
for
every
issue
that
has
control
run,
requesting
the
user?
Explain
why
they're
using
two
control
run,
why
they're
not
using
apply
and
like?
Are
they
using
it
purely
for
debugging
or
for
teaching
or
for
development
or
what?
Because
I'd
really
like
to
know,
if
folks
are
using
this
to
run
their
workloads
in
production
or
not.
B
Real
quick:
let's
look
at
oh
sorry,
who's
going
to
respond
to
that
one
I'll
I'll
close
that
one
okay,
I
wanted
to
bring
this
one
up.
8.94
support
private
git
repos
for
cube,
ctl
apply.
F
No,
you
should
use
like
this
can
be
solved
by
like
kept
just
fetching
the
repo
and
applying
locally.
F
If
we
want
to
get
in
the
business
of
like
control,
applying
to
get
repos
and
making
that
experience
really
good,
then
we
need
to
like
actually
get
in
that
business
and
then
like
call
out
like,
is
that
packaging
or
is
that
not
packaging
or
that
sort
of
thing,
because
it
seems
like
we've?
In
the
past,
we've
been
pretty
hand-wavy
about
what
we
support
and
it's
mostly
been
okay,
we'll
apply.
F
We
support
it
through
customize
and
we
apply
it
through
to
a
url.
But
if
we're
going
to
start
applying
get
directories
from
dash
ft,
then
I'd
like
to
like
really
flesh
out
what
we
want.
The
full
get
experience
to
be
like.
C
F
Other
kit
or
the
other
non-git
version
control
systems.
F
F
And
that
sort
of
thing
are
kind
of
where
my
questions
are,
and
so
maybe
this
is,
if,
if
we
don't,
if
we
don't
agree
that
it
is
out
of
scope
or
we're
not
sure,
then
maybe
we
should
have
a
follow-up
discussion
on
that.
But
it
just
seems
like
a
longer
discussion
than
we're
going
to
get
in
this
bug.
Triage.
A
I
mean
a
simple,
a
simple
answer
to
that
is:
create
a
plugin
show
us
that
the
plugin
is
successful
and
it's
being
broadly
used
in
the
community.
Then
we
can
think
of
adding
that
functionality
to
the
core.
That's
probably
the
best
option
for
us
and
that's
one
of
the
reasons
that
why
we
went
with
the
cube
cutter
plugins
to
allow
people
to
experiment
quickly,
gather
feedback,
improve
and
return
to
us
with.
A
With
with
their
success
that
they
achieved
through
a
plug-in,
and
then
we
can
reassess
whether
this
kind
of
functionality
will.
F
Yeah
I
mean
the
plug-in
is
going
to
be
difficult
to
implement
right
because
they're
really
asking
for
it
to
be
in
control,
apply,
and
so
it's
going
to
I'm
not
exactly
sure
how
they'd
write
the
plugin
like
they
essentially
have
to
invoke
the
control,
apply
libraries
and
do
some
of
the
same
work
that
sean
has
done
with
apply
ncla
utils,
where
you
kind
of
have
to
like
put
code
into
the
hooks
we've
exposed.
A
F
We
should
we
should
have
like
a
you
know,
celebration
on
the
10th
bug
scrub
or
like
the
anniversary
of
like
the
first
one
or
something
I
don't
know
just
to
sell.
F
Issues
yeah,
I
mean,
or
something
right
like
to
celebrate.
The
product
like
we've
introduced,
eddie,
introduced
this
process,
and
I
think
we
should
celebrate
like
its
success
when
we
hit
some
sort
of
arbitrary
milestone.
A
How
far
we
are
out
of
curiosity,
are
we
close
to
10
a
year?
I
think
we
started
at
the
beginning
of
this
year.