►
From YouTube: Kubernetes sig-aws 20190111
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-
this
is
sick
AWS.
This
is
January
at
the
day.
Today
is
January
11th
2019,
Happy,
New,
Year
everybody.
We
all
have
a
great
year
this
year
and
we
have
a
couple
of
items
on
the
agenda.
Please,
if
you
do
want
to
cover
something,
please
do
feel
free
to
put
put
it
on
the
agenda.
Please
be
great
if
you
want
put
your
name
in
the
attending
list,
so
we
can
cart
it
back.
Who
you
are
in
case
you
don't
know
and
a
reminder.
A
A
Yes,
I
wasn't
actually.
Are
the
minister
see
what
this
link
is
to
so
is
we
I've
started
posting
the
videos
on
our
syllabus
channel
and
we
also
they
have
it.
We
have
a
link
in
the
in
the
minutes
to
our
CBS
update,
which
initia
and
myself
gave
at
coop
con
for
anyone
that
was
not
able
to
attend
I,
don't
there's
anything.
We
want
to
add
on
that
on
that
note
about
what
we
covered,
but
the
video
is
there
and
is
of
course,
as
always
great
watching,
particularly
double-speed.
B
And
the
other
thing
I
wanted
to
add
just
it
was
a
couple
of
ask
asks
from
the
presentation
I
think
a
couple
of
folks
said
that
they
want
to
get
involved
with
ckw
us
and
we
have
been
creating
history
of
all.
The
issues,
open
issues
related
to
say,
gay,
WS,
I
think
it
requires
proper
labeling
and
then
it
needs
to
be
labeled
as
siga
WS,
and
then
it
needs
to
be
categorized
as
a
easy,
medium
or
a
hard
issue.
So
people
can
get
involved.
B
A
Think
I
definitely
you're
right
to
call
out
the
the
the
people
want
to
contribute
and
it
is
hard
to
find
places
to
contribute
or
find
five
hard
find
issues
to
contribute,
on
particular
in
the
KK
repo
I
think
we
talked
about
the
idea
that
there
are
a
lot
of
projects
which
are
not
in
kubernetes
kubernetes
repo.
A
lot
of
they
do
a
special
push
to
another
committee
squibbon
as
we
feel,
but
are
great
places
to
start
contributing
for
people
and
are
perhaps
a
little
a
little
easier
and
higher
lower
effort.
A
Higher
return,
I
guess,
might
be
the
way
I
would
put
it
and
I
see
you
have
to
like
more
sub
projects
like
for
proposal
which
I
think
it,
but
that's
a
separate
leeway.
These
sub
projects
are
are
are
still
very
much
part
of
communities,
and
the
intention
is
is
to
make
the
the
core
of
kubernetes
smaller
the
criminals
kubernetes
repos
smaller,
so
that
we're
able
to
better
work
in
multiple
repo.
So
it
is
not
that
they
are
like
second-class
repos.
It
is
just
that
they
are
distributed
and
reflecting
our
increasing
community
size.
A
B
A
A
But
yes,
and
hopefully
we
will
have
lots
more
updates
in
the
coming
cube
guns,
so
we
can
work
on
that.
I
know
the
anyone.
That's
thinking
of
submitting
a
talk,
I
think
the
deadline
for
coop
con
EU
submissions
talk,
submissions
is
coming
up
in
about
a
week,
so
get
working
on
it.
If
you
want
to
submit
a
talk
to
Barcelona
and
I
think
the
there's
one
Asia
somewhere,
which
is
around
the
same
time.
So
those
two
are
the
deadlines
coming
up,
I
think
the
next
I
think.
A
B
C
An
issue
probably
can't
like
supplements
like
a
family
as
anything,
so
the
idea
is
like
because
it
always
has
other
storage
service
like
a
EFS
for
elastic
file
system,
as
well
as
which
is
a
new
launch,
cada
fsx
as
a
for
lustre.
It's
for
like
used,
usually
using
HPC
and
in
order
to
integrate
those
two
service
or
product
into
the
community
system,
like
as
a
Natura
attention
to
the
EBS,
which
already
been
already
implemented.
B
B
Yeah
and
I
think
the
idea
is
because
we
decided
that
all
in
volume
provisioning
will
be
eventually
removed
and
all
the
storage
logic
will
be
in
CSI.
Drivers
wanted
to
just
continue
the
roadmap
for
CSI
drivers.
We
did
EBS
next.
We
want
to
do
here
first,
and
there
are
also
some
customers
who
want
to
use
Amazon
luster,
which
is
fsx
for
HPC
apps,
and
so
the
two
sub
project
proposals
are
to
give
support
for
those
CSI
drivers
and
essentially
try
to
do
an
alpha
and
1.14.
A
That
sounds
great
I.
Think
four
people
are
not
aware.
The
you
know
these
subjects
that
are
then
sponsored
by
the
the
sig
and
we
basically,
if
anyone
has
any
objections
within
the
Singh
as
to
why
it
should
not
be
a
project
than
we
so
do
a
verbal
confirmation
and
then
I
think
we
have
a
further
process.
A
I
think
the
one
thing
I
would
bring
up
less
so
for
the
lustre,
but
particularly
for
the
NFS
one
is
maybe
I,
don't
know
whether
you've
talked
to
six
storage
about,
like
I,
think
a
lot
of
I
know:
DCP
has
an
NFS
backed,
hosted,
NFS
type,
product
and
I
know
that
NFS
is
also
a
thing
on.
You
know
bare
metal
and
so
I.
Don't
know
whether
whether
six
storage
thinks
there
should
be.
How
that
has
six
orders
thinks
the
NFS
drivers
should
be
implemented,
I
mean
to
an
extent
I.
A
Guess
that's
true
for
lustre
as
well,
but
I
feel
like
luster
is
much
more
much
less
come
free
common
but
like
to
what
extent
the
the
AWS
NFS
driver
is
going
to
be
similar
to
the
GCP
and
FS
driver
is
gonna,
be
similar
to
that
bare
metal
and
FS
driver
and
whether
it
makes
sense
to
have
how
the
colors
project
should
be
organized.
So
don't
know
whether
you've
talking
to
six
spoken
to
seek
storage
about
that.
Oh,
not.
C
Yet
so
at
least
there
are
similar
thinking
like
you
just
asked,
like
they're,
really
similar
they're,
all
backed
by
NFS,
one
difference,
I've
been
so
far
as
like
encryption
in
transit,
which
I
haven't
seen.
Anything
anywhere
else
is
providing
these
features,
so
might
be
one
of
the
differentiator
for
EFS
CSI
driver,
okay,.
A
And
that
requires
that
configuration
and
on
the
CSI
unless
I
sign,
I,
guess
it's
like
it's
all
mount
option
called
the
TLS
okay,
so
I
mean
I.
Think
yeah
I
think
that's
a
good
thing
from
my
point
of
view
at
least
and
I.
We
should
everyone
should
feel
free
to
chime
in.
But
from
my
point
of
view,
I
think
these
I'm
happy
that
these
would
be
in
sigit
of
us
I
think
we
should
just
check
with
sig
storage
about
whether
they
agree
that
you
know
every
different
group
would
have
a
separate
suicide
driver
type
thing.
A
C
B
So
one
thing
is
the
CSI
spec
wandered
otha
was
updated.
We
should
look
at
that
spec
and
I
think
the
idea
is
to
keep
the
spec
generic
and
then
use
the
underlying
storage.
Api
is
to
expose
features
such
as
we
probably
write.
The
driver
will
figure
out
feature
gaps
between
in
different
cloud
provider,
vendors
and
it's
always
good-
to
have
a
discussion.
I
do
think
that
Saad
had
an
opinion
on
how
the
CSI
driver
features
are
sort
of
listed
out
in
the
common
repository
and
linked.
B
But
then
we
can
discuss
that
offline
also
and
see
if
he
has
any
bearing
opinions
from
the
input
I
got
from
Saad
in
the
past.
Was
there
more
interested
in
figuring
out
a
common
way
to
migrate
any
in
volume
calls
to
the
CSI
driver
logic
because
that's
going
to
be
common
across
providers
and
it
requires
a
lot
of
work
but
other
than
that
I
think
like
with
EBS,
we'll
probably
figure
out
deltas
between
you
know:
Google,
block
storage
as
your
block,
storage
and
Amazon,
and
the
problems
with
the
API
of
our
service.
B
A
A
B
A
Yes,
that
has
its
own.
That
has
its
own
process,
so
I'm
sure
you
will
I'm
sure
you
will
follow
it
because
you
are
excellent
at
that.
So
thank
you.
We
have
reached
the
end
of
our
agenda.
I,
don't
know
if
anyone
else
has
anything
they
would
like
to
bring
up
or
discuss
or
and
has
anything
they
are
want
to
share
that
their
thing
you're
working
on
in
2019,
but
otherwise
everyone
gets
some
time
back
of
their
day.
So.
B
So
I
think
the
roadmap
that
we
showed
in
Yukon,
I
kind
of
think
that
if
we
sort
of
take
that
roadmap
and
put
it
as
a
survey
and
ask
you
know,
sig
AWS,
Google,
Group
and
slack
forum,
ask
people
to
like
rank
the
release.
Planet
would
be
a
good
use
of
time,
but
I
don't
know
what
people
think.
A
One
one
vote
for
yes
from
me
and
one
from
your
dog.
It's
an
sounds
like
sorry.
Well,
III
personally,
think
that's
a
great
idea
to
have
a
have
a
survey
because
I
mean
not.
Everyone
is
able
to
attend
the
meetings
and
I
think
I
also
love
to
see
a
like
a
sort
of
open-ended
like
any,
like
your
wish
list
type
thing
so
that
it's
not
just
what's
on
our
we're,
not
just
like
prioritizing.
What's
on
our
roadmap
they're
trying
to
capture
things,
we
have
missed
entirely,
but
yeah
I.