►
From YouTube: 20200114 Kubernetes SIG Usability
Description
Regularly scheduled SIG meeting:
- user research proposal
- standardizing iconography
- update on secure by default work
A
Okay,
hi
everybody
and
welcome
to
our
regularly
scheduled
cig
usability.
First
one
for
2020.
Today
we
have
Gabby
who's
going
to
do
an
overview
of
some
of
the
work.
She's
done
for
some
of
the
usability
studies
that
we
plan
to
do
hopefully
kicking
those
off
within
the
next
quarter
and
then,
after
her,
if
Pamela
sorts
out
some
internet
issues
that
she's
having
Pamela
will
do
a
presentation
on
some
iconography
work.
She's
been
doing
so
Gabby
go
for
it,
cool.
B
B
So
if
y'all
were
here
last
time,
you
can
like
saw
these
kind
of
like
high
level
profiling
questions,
I
sent
it
out
to
the
Google
group
and
some
people
sent
X
and
great
feedback.
So
thank
you
for
that.
I
think
we
had
some
additional
questions
around.
Where
do
these
people
have
their
environment
located
like?
Is
it
on-premise
or
is
it
in
a
public
cloud
somewhere
or
somewhere
in
between,
but
I
guess
the
bulk
of
the
survey
are
these
jobs
questions
and
what
I've
done
since
then,
as
I've
started,
transferring
this
over
into
a
survey
monkey?
B
This
is
still.
This
link
is
still
in
the
Google,
the
original
Google
Docs.
So
if
anybody
goes
in
and
just
kind
of
like
clicks,
this
link
right
here,
you
should
get
the
preview
of
the
survey
you're
in
every
monkey,
so
you
a
little
bit
a
like
higher
fidelity
per
se.
So
these
are
for
the
most
part
of
the
same
questions,
but
I
just
wanted
to
go
ahead
and
start
switching
it
over.
B
So
I
guess
like
what
we're
trying
to
find
out
from
this.
Hopefully
it
maybe
it
doesn't
feel
as
lightweight
now,
but
it
the
intention
was
for
it
to
be
lightweight,
is
just
to
kind
of
start
getting
collecting
use
cases.
What
are
you
trying
to
achieve
with
kubernetes
and
so
I?
Don't
usually
at
this
stage
of
collecting
jobs?
And
you
know
it,
people
do
it
via
interview
style.
The
idea
of
putting
it
into
a
survey
form
was
to
also
give
us
the
chance
to
start
doing
some
baselining.
B
Just
gender,
like
you,
know
a
lightweight
and
PS
a
question,
and
then
pretty
important
here
would
be.
Would
it
be
okay
for
someone
from
the
open-source
community
to
follow
up
with
you
about
your
response?
So
if
they
gave
us
if
we
liked
their
responses
and
wanted
to
kind
of
like
do
a
little
bit
of
a
deep
dive,
maybe
like
a
15
minute
call
or
or
30
minute,
deep
dive?
B
A
Cool
yeah
I
think
this
looks
great
I.
Obviously
like
I've
chatted
with
you
before
about
this,
but
I
think
is
a
really
lightweight
way
to
get
started.
This
would
be
super
interesting.
It
could
possibly
get
us
access
to
more
people.
Who'd
be
interested
in
talking
more
to
us
about
their
experience
and
it
kind
of
gives
us
a
place
to
start
as
far
as
user
research
goes,
and
you
know
as
far
as
kicking
this
off
I
think
once
everyone's
had
a
chance
to
look
at
it
offer
any
feedback
anyways.
A
We
want
to
improve
it,
just
keeping
in
mind
that
we
are
trying
to
keep
this
as
lightweight
as
possible,
just
so
that
people
complete
it.
We
don't
want
to
kind
of
send.
Like
a
I
mean
you
can
imagine
that
if
someone
was
really
passionate
about
either
the
positivity
or
negativity
of
their
experience,
they
could
spend
a
lot
of
time
on
these
essay
questions
actually
Gabby
as
a
question
in
Survey
Monkey.
What
is
the
character
limit
on
those
paragraphs?
A
C
And
the
give
me
the
only
other
thing
that
I
was
going
to
suggest
was
it
we
put
the
lightest
weight
to
answer
questions
up
at
the
top,
so
I
got
a
scale
of
1
to
10
0
to
10.
How
likely
are
you
to
recommend
community
or
friend
or
colleague,
is
a
super
lightweight
thing
to
answer
so
that
we're
we're
going
progressively
more
detailed
as
we
go
along
gotcha.
B
A
When
you're
trying
to
achieve
these
different
use
cases-
and
so
I
thought
you
were,
you
were
awesome
to
share
that,
because
a
lot
of
that
feedback
I
could
imagine
us
getting
in
this
form,
so
yeah
yeah.
It
would
be
good
to
kind
of
know
where
people
are
getting
frustrated
and
I.
Just
think
that
this
kind
of
format
is
a
really
nice
lightweight
way
to
kind
of
get
access
to
people
who
might
have
some
better.
You
know
more
in-depth
feedback
for
one-on-one
interview
sessions,
yeah.
B
A
Yeah
so,
as
Gaby
mentioned,
she
dropped
the
links
in
the
agenda,
I
think
and
everyone
who
is
part
of
the
mailing
lists.
It
does
have
excess
and
can
the
comment
and
leave
feedback,
and
we
would
like
to
try-
and
you
know,
agree
that
this
is
a
good
first
research
effort
and
ship
this,
so
that
we
can
start
kind
of
building
rolodex
of
people
who
are
interested
in
giving
us
more
research
data,
so
cool
thanks.
So
much
for
all
the
work
you've
done
on
that
Gaby.
It's
looking
really
good,
no
yeah
happy
to
hey.
E
E
This
thing
was
that
we
were
looking
for
icons
to
make
it
consistent
across
our
products,
because
we
are
kind
of
investing
into
kubernetes
and
we
were
like
okay,
what's
out
there
and
open
source
will
be
that
we
can
use
in
our
products,
and
we
then
really
find
anything
and
when
we
started
this
discussion,
one
of
the
first
few
things
we
discussed
was
like
hey.
How
do
we
like
to
know
will
the
repository
of
icons
that
could
be
consistent?
All
you
know
in
the
community,
and
we
could
all
like
share
it.
E
E
E
So
I
followed
what
Gabby
had
done
initially
in
terms
of,
and
she
was
exploring
for.
Mr.
Li
kind
of
all
of
the
same
format
sometimes
want
to
take
you
through
this
document
and
shared
it
with
everybody
as
officiating,
right
varmints,
because
this
needs
to
be
improved
a
lot.
But
the
idea
is
the
goal
as
it
is
this
to
unify
the
experience
of
using
two
headings,
icons
across
the
community
and
have
a
way
of
sharing
icon.
Typically,
once
you
have
access
to
the
icon,
you
can
use.
E
You
know
in
a
fellow,
very
impatient
in
size
that
you
want
to
the
reason
we
want
to
do
this
and
how
come
be
expecting
out
of
this
is
to
have
a
detailed
iPhone
repository
for
kubernetes,
iPhones
or
also
technology
icons.
You
know
for
us
to
use
of
anybody
infants
in
terms
of
capability
community
please
and
have
some
consistency
across
and
another
positive
out
of
this
would
be
because
you
know
a
lot
of
terminal
uses
open
source
and
there's
a
lot
of
integration
with
different
tools
of
anyone
associated
in
different.
E
You
know
products
there's
we
all
speak
the
same
language.
So
when
we're
talking
about
daenerys
clusters
and
iPhone,
okay,
you
know
kind
of
integrating
with
human
peers.
You
know
we're
talking
about
the
same
language
if
this
expert
is
adopted
by
everybody
across
it.
There
is
another
similar
effort
going
on
out
here.
I
can
open
this
tab.
E
One
of
the
things
is
that,
of
course,
this
is
not
something
that's
gone
through
review
and
it's
not
something
you
know
be
as
a
team
or
as
a
group
has
looked
at
and
also
it'd,
be
nice
to
kind
of
have
a
proper
standard
guidelines
around
how
we
are
building
icons
as
we
go
forward,
because
it
is
something
that
are
going
to
be
used
in
context
us.
So
we
can,
as
a
team,
you
know,
go
through
these
icons
and
see
what
actually
work
and
what
goals
work
mechanically.
E
There
is
an
effort
already
out
there
and
there's
a
deeper
presentation
as
well
in
terms
of
how
these
icons
and
we
used
so
the
links
then-
and
we
can
discuss
more
about
it
now.
I'm
gonna
go
a
little
bit
into
details
about
what
we,
as
the
VMware
team,
have
been
doing.
We
have
a
clarity
website
which
is
the
design
system.
We
it
use
in-house
and
there
are
a
lot
of
icons
available
on
this
website.
E
So
if
you
go
to
the
ideal
design-
and
you
want,
if
you
search
for
namespaces,
you
can
actually
access
a
namespace
iPhone
right
from
here
and
you
can
download
the
SVG
icon
for
that
names
because
icon.
So
this
is
a
really
sort,
that's
already
available
and
it's
open
source.
It's
a
design
system
we
use,
but
these
are
icons
that
we
are
using
in-house
PDA
advocate
there.
We
have
different
products
that
support
kubernetes
and
all
of
them
are
using
these
icons,
because
you
know
you
want
to
consistently
pin
house
but
I'm.
E
Also
what
I've
done
is
so
you
this
is,
of
course
it's
if
you,
if
I
just
look
at
this
a
lot
of
icons,
you
know-
and
they
might
not
all
be
relevant
for
us
right
now
as
we
go
forward.
Of
course,
we
can
include
a
lot
of
icons
into
our
repository
and
we
can
probably
categorize
them
in
different
sections,
but
going
forward
at
least
I
was
thinking.
We
can
be
a
little
bit
more
focused
and
identify
objects
that
we
really
are
using
on
a
day
to
day
basis
and
are
very
common
across
all
our
products.
E
So
I
do
have
a
big
mass
file
that
I
created,
which
is
open
as
well,
and
you
all
can
access
it.
What
I've
done
is
I've
made
two
documents
right
now
light
and
dark
and
I've
identified
the
top
view
that
we've
been
using
in
house
right
now.
As
you
know
like
across
our
products,
there
are
quite
a
few
that
you
know
are
still
a
bit
like
you,
services
are
missing,
deployments
is
missing.
Those
are
some
common
ones,
bbc's.
E
Those
are
things
that
are
in
a
Python
and
we
would
want
to
work
on,
but
currently
in
a
product
that
we
are
usually
going
to
be
launching.
These
are
the
icons
happy
fills
in
house
lilia
in
a
visual
designer
who
stand
all
these
illustrations.
So
this
is
definitely
something
that's
already
available
and
we
should
take
a
time
to
you
know,
review
it
and
see
what
we
think
about
it.
E
In
terms
of
you
know
this
official
design
and
just
the
design
elements
of
it
is
there
something
that
you
want
to
go
forward
with,
and
you
have
time
I
would
encourage
they're
going
to
look
at
it.
There's
a
comment
section
on
top
three
three
to
add
comments
as
to
what
we
think
is
good
and
also
feel
free
to
share.
If
you
have
something-
and
you
think
would
be-
you
know
better
line
with
us,
proposing
out
there
to
the
perfectly
now
going
back.
E
So
that
was
what
we've
kind
of
been
working
on,
but
I
don't
think
you
know.
Iphone
should
be
one
person's
job,
so
I
did
make
like
a
documentation
on
how
one
could
contribute
iPhones
I
think
we
need
to
have
strict
guidelines
across
around
contributing
iPhones.
So
say
somebody
has
a
need
for
a
new
iPhone.
They
can
go
and
propose
you.
E
Were
simply
propose
a
new
icon,
but
this
should
follow
these
guidelines
or
have
some
kind.
We
should
have
like
a
certain
criteria
that
needs
to
be
met
for
an
iPhone
to
go
into
the
iPhone
packs
to
kubernetes
so
filthy,
to
read
this
and
we
can
expand
on
this.
You
know
after
everybody's
reputed
and
has
added
their
conference,
but
for
now
is
thinking
that
we
could,
you
know,
definitely
add
what
the
default
size
is.
It
could
be
36,
36
and
16
by
16,
because
a
lot
of
icons
are
very
difficult
to
scale
down.
E
E
Svg
formats
are
the
best
in
terms
of
sharing
icons,
because
you
can,
you
know,
change,
color
and
the
easily
is
able
to
change
or
modify
them.
Skill
ability
I've
seen
this
as
a
big
problem,
because
at
VMware
the
product
I
work
on
this
fear
is
a
very
complicated,
complex,
UI
and
a
lot
of
times.
The
iPhones
have
to
be
really
hard
to
because
they
need
to
be
it.
We
need
to
be
able
to
like
scale
them
down
easily.
So
then
you
scale
down
an
icon.
If
you
know
the
pixels
and
to
be
effective.
E
So
that's
something.
Definitely
we
should
look
into.
We
have
an
accessibility,
hadn't
seen
I'm
gonna
be
working
with
them
in
terms
of
supporting
what
an
iPhone
should
be
when
we
are
looking
at
accessibility.
I
do
have
some
points,
but
I
definitely
always
were
rounded
by
them
before
I
put
them
here
and,
lastly,
design
review
and
finalizing
the
iPhones
I
do
agree
that
people
should,
you
know,
definitely
contribute
towards
this.
E
So
these
are
the
icons
equality
worked
on,
which
is
already
in
the
figma
file
that
you
will
look
at,
but
we
can
also
now
go
ahead
and
add
request
or
require
iPhones.
So,
as
groups
like
when
you
are
looking
at
this
document,
I
would
encourage
everybody
to
add.
You
know
I
first,
like
just
objects
that
you
are
currently
using
a
lot
and
would
need
icons
for
and
then
we
can
identify
it.
You
know
everybody
can
probably
just
want
to
be
towards
this
iPhone
fact
at
the
before
word:
yeah.
That's
it
from
me
right
now.
A
A
If
you
read
the
description,
it
also
says
that
those
icons
are
really
intended
for
presentations
and
I'm,
not
sure
if
anyone
actually
used
it
so
I
guess
the
question
is
Valerie:
do
we
want
to
own
it
or
do
like
you
know,
I,
don't
know
if
we
know
who's
worked
on
them
in
the
past
or
where
you
know
where
they
came
from
I
guess
we
could
do
it.
We
could
look
at
the
history.
F
E
A
I,
you
know
what
I
kind
of
think
we
should
do
so.
A
great
presentation,
I,
yeah
I,
feel
like
some
of
these
might
be
useful.
I
feel
like
maybe
the
next
step
is
once
we
as
a
group
are
like
yeah.
We
like
these
icons
or
we
just
want
more
information
about
how
other
groups
are
thinking
about
icons
and,
like
would
be
to
go
to
like
say,
gaps
where
a
lot
of
the
people
who
are
developing
kubernetes
based
applications
meet
and
try
presenting
this
there
and
see
kind
of
what
feedback
we
get
from
those
those
people.
A
A
A
G
A
Cool
thanks
for
joining
okay.
Well,
if
anyone
has
anything,
you
would
like
to
talk
about
related
to
usability
now's
a
great
time.
Also,
our
agenda
is
open,
so
feel
free
to
add
topics
or
follow
on
meetings.
Another
thing
that
I'd
really
encourage
is,
if
you
see
a
cool
project,
that
you
think
this
group
could
benefit
from
a
presentation
about,
feel
free
to
suggest
it,
and
we
can
reach
out
to
the
maintainer
and
ask
them
if
they'd
like
to
present
to
us
I
think
for
the
next
week,
we're
probably
going
we're
going
to
continue
working
on.
A
F
I
was
gonna,
give
an
update.
There
is
a
lot
of
motion,
but
not
progress.
I've
been
talking
with
some
of
the
security
people
and
the
network
people,
but
it's
challenging
to
change
anything.
So
after
I
put
up
the
initial
cap,
I
got
a
lot
of
feedback
on
some
of
the
logistics
and
reasons
why
we
don't
necessarily
want
to
implement
default
security.
So
I
am
still
talking
to
people
and
kind
of
mulling
over
how
to
proceed.
A
F
A
There
I
think
that
tooling
I
think
so
from
what
I
heard,
like
the
reason
that
pod
security
policies
haven't
kind
of
made
it
out
of
beta
was
because
everyone's
been
like.
Oh,
it's
we're
just
gonna,
invest
in
it,
but
instead
and
I
know
that
oppa
had
some
interesting
plugins
that
some
people
and
the
multi-tenancy
group
were
really
excited
about
with
like
core
DNS
+
OPA
plug-in
model.
G
F
A
C
H
H
A
E
Sasha,
what
you
can
do
is
that
there's
so
many
people,
maybe
we
can
arrange
for
one
that
you
could
actually
talk
to
all
of
them
this
week
and
I
could
arrange
it
because
we
have
the
new
designers
on
the
team
as
well
and
they
really
wanted
to
meet
you.
Oh
yeah,
that
sounds
good
yeah.
So
just
we
now
send
out
an
invite
and
then,
if
you've
done
it,
anybody,
okay.