►
From YouTube: cf-for-k8s Monthly SIG (July 2020)
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
B
C
B
C
B
B
B
A
C
A
B
A
C
C
D
C
B
A
C
C
Yeah
yeah,
so
Flavio
Castel
ease
distinguished
engineer
at
Sousa,
who
is
responsible
for
the
architecture
of
Sousa
Cavs
platform,
so
deeply
into
kubernetes,
and
we
talked
last
year
about
how
we
have
two
different
authentication
models
for
the
kubernetes
api
and
Cloud
Foundry
API.
And
what
could
we
do
to
use
UA
a
to
create
organ
space
like
structures
and
similar
are
back
roles,
roles
that
are
similar
to?
D
Yes,
yes,
he's
looking
at
adding
these
concepts
of
orgs
and
spaces
to
wrap
namespaces
around
so
you'll
have
CR
DS
for
organizations
and
spaces,
and
then
people
can
tour
around
with
that
and
then
you'd
have
an
operator
that
automatically
sets
up
namespaces
with
the
appropriate
CR
DS
and
everything,
sorry
with
the
appropriate
roles
and
bindings
to
match
the
origin
spaces.
Yes,
oh
yeah
yeah.
He
has
a
lot
of
detail
around
that
and
so.
C
Anyways
yeah
we're
happy
to
share
that,
because
if
other
people
are
doing
work
in
that
area,
I
think
it
would
be
good
to
work
together
on
it.
Rather
than
have
a
couple
different
implementations,
all
right,
we
talked
a
little
bit
about
how
Rancher
had
sort
of
done
their
own
thing.
There
that's
not
really
connected
to
the
kubernetes
community.
So
if
we
could
do
the
thing
that
is,
you
know,
it
could
be
broadly
accepted
as
a
as
the
right
way
to
do
role
based
access
control
on
kubernetes.
That
would
be
great.
E
A
E
F
B
A
Okay,
then
the
question
would
be
any
more
Atok
topics.
We
could
talk
about,
I
mean
Marco,
just
just
pinged
me
and
like
I,
don't
I
don't
have
the
food
context,
but
he
was
basically
asking
a
question
of
like
what's
the
status
regarding
route
services,
I'm,
not
sure
if
that
was
actually
meant
to
be
a
question
for
for
psy
or
more
everybody
else.
Nobody.
B
F
A
F
A
F
C
If
we
have
a
bit
of
time,
I
think
it'd
be
good
to
talk
about
I,
really
X
and
getting
that
upstream,
so
that
it
can
be
used.
I,
don't
think
we
have
a
dedicated
team
to
ireenie
X
right
now,
so
it
would
not
be
a
new
team.
It
would
just
be
a
repo
and
responsibility
for
it.
Vlad
that
would
that
fall
on
the
cube,
CF
team.
D
C
C
D
D
E
E
Then
the
status
of
them
I
know
when
I
talked
with
Jillian
here
about
I
mean
II
Percy
like
very
briefly.
He
was
saying
that
there's
actually
some
code
injected
into
irony
itself
that
they
did,
that
might
help
which,
which
may
be
complimentary
or
or
who
knows,
with
with
what
the
Hirini
Percy
work
did,
but
they're
they're
also
on
pause
for
the
moment
as
they
there.
Many
of
the
team
members
who
are
working
on
volume
services
are
trying
to
help
get
CF
for
Kate's
to
GA
era.
One
daughter,
as
a
case
may
be.
C
D
That
one
is
sort
of
a
catch-all
for
all
storage
classes
that
run.
So
if
you
have
search
classes
configured
to
on
your
kubernetes,
you
can
expose
them
as
Percy
services
in
Cloud
Foundry.
So
you
just
get
everything
that
cube
supports
you
get
as
a
persistent
service
for
your
ireenie
apps
so,
and
that
seems
to
work
well.
D
A
Then
I
guess
it
depends
on
the
on
the
actual
kubernetes
underlay
implementation.
If
there
is
then
like
I,
don't
know
the
official
term,
but
this
like
a
single
container
can
read
right
from
it
versus
like
multiple
containers
can
write
into
it
simultaneously
and
then
kind
of
sync
back
and
forth.
All
of
that
I
guess
would
be,
would
be
handled
by
whatever
properties,
the
underlying
kubernetes
and
is
provides
right.
I
think.
D
D
B
D
E
Yeah,
we
haven't
had
it
before,
but
it
was
a
use
case.
They
were
interested
in
exploring
for
certain
types
of
apps
like
sometimes
you
need
more
storage
attached
than
is
normally
available
right
for
a
certain
kind
of
app
or
you
need
certain
speed
because
you're
handling,
like
geospatial
data,
or
something
like
that
or
certain
apps.
That
expect
to
write
locally,
but
don't
want
that
overwritten
by
some
other
thing.
E
D
C
D
C
It
I
get
it,
but
but
the
other
use.
The
other
thing
that
comes
from
that
use
case
is
content
management
systems
where
you're
uploading
a
file
right.
A
lot
of
these
frameworks
just
use
the
file
system,
because
it's
expecting
to
be
running
on
a
bare
metal
server
and
they
never
really
updated
it
to
use
the
database
properly
so
shared
volumes,
whether
a
great
way
to
just
run,
not
not
cloud
native
things
well
enough
in
that's
that's
what
I
use
good
for
with
sample
and.
B
D
C
I'm
Percy
NFS
earth,
sorry
and
the
NFS
in
SEF
in
the
NFS
broker.
Did
this
as
well,
and
this
is
what
you
would
use
it
for.
You
would
use.
It
drew
an
untrue
poet
like
Django
or
something
when
you
you're
blogging,
and
you
upload
an
image
that
image
is
shared
through
all
instances
of
the
app
and
yes
yeah,
and
it's
right
that
the
storage
provider
might
not
support
multiple
rights.
C
B
Ok
yeah,
it
might
not
be
excluded
from
the
possibilities
from
an
kubernetes
api
standpoint,
but
you
can't
even
get
like,
I
think
on
AWS,
you
don't
even
get
multiple
write
disks
that
you
can
attach
to
two
hosts
to
two
worker
nodes
so
that
no
matter
where
they
run
they
get
it.
Maybe
I'm
wrong
with
that,
but
and.
D
Yeah
there
is
so
when
the
the
service
gets
created,
we
get
a
persistent
volume
and
then,
whenever
a
binding
happens
we
just
we
just
mount.
We
have
the
volume
mounts
be
appended
to
to
a
pod.
So
if,
if
the
search
class
support
supports
multiple
read/write,
they
should
see
the
same
thing.
So
it's
not
using
a
persistent
volume
claim
template.
D
C
E
C
I've,
never
really
had
great
luck
with
Cloud
Foundry
Epic's
submitted
to
cube
card
they've
all
been
rejected,
but
mind
you.
Almost
everything
is
predicted
to
console
I,
don't
take
I,
don't
take
it
personally,
but
this
time
I
just
went
in,
and
so
we
tried
to
sort
of
talk
generally
about
platform
as
a
service
and
not
Cloud.
Foundry,
specifically
and
or
try
to
you
know
talk
about
application
delivery.
Instead
of
and
as
soon
as
you
put
the
word
cloud
foundry
in
there,
it
seemed
to
be
like
the
kiss
of
death
for
acceptance.
C
This
time,
I
just
went
all
in
and
made
a
sort
of
self-deprecating
abstract
about
Cloud
Foundry,
the
good
parts
where
we
will
fess
up
to
the
previously
non
cloud
native
nature
of
parts
of
Cloud
Foundry,
and
talk
about
the
talk
about
cloud,
foundry,
warts
and
all
because
you
know
they
would
I
think
that
might
be
more
of
a
draw
for
people
who
who
are,
for
whatever
reason,
prejudiced
against
pass
or
Cloud
Foundry.
So
I'll
share
that
abstract.
If
I
can
find
it.
E
Yeah
I
mean
the
their
topics
are
sort
of
like
does
it
include
these
technologies?
That
happened
to
be
in
part,
a
part
of
CN
CF
and
so
yeah
that
there
are
a
lot
of
topic
talks
that
are
probably
submitted
and
I'm
a
high
percentage
of
them
don't
get
accepted.
But
I
did
you
know
I,
it's
disappointing.
If
you
can
say
like
actually,
Cloud
Foundry
is
using
like
six
or
more.
A
E
C
Did
actually
have
a
chat
with
the
Cloud
Foundry
people
who
I
think
Caitlin
and
chip
who
and
who
have
said
that
there
is
an
effort
going
by
the
Linux
Foundation
to
the
force
to
force
the
umbrella
communities
to
play
nicely
with
each
other
and
to
include
each
other
stuff.
So
there
is
a
I
am
told
a
thawing
of
the
maybe
silo
Inc,
a
thawing
of
the
silos
I'm
mixing
my
metaphors
here.