►
From YouTube: Cloud Foundry for Kubernetes SIG [January 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).
B
Yes,
yeah
here
we
go
so
yeah
welcome
everybody
officially
for
the
1st
of
2020
boundary
on
kubernetes
called
Happy
New
Year
everybody,
as
mentioned
earlier
I,
think
we
still
have
a
draw
between
like
the
dual
approach
topic
and
the
kubernetes
or
requirement
to
kubernetes
components
topic
anybody
wants
to
raise
an
opinion
on
which
one
to
to
tack
on,
preferably
the
people
that
haven't
voted.
Yet,
yes,
should.
B
D
Actually
Alex
just
joined,
so
maybe
we
could
have
some
discussion
of
some
of
the
ideas
in
his
document.
I
know
we've
kind
of
talked
about
integration
issues
for
the
past
couple
of
times
and
maybe
is
just
some
follow
up
so
I
know
you're
working
on
kind
of
a
more
comprehensive
and
concrete
proposal
for
the
integration
work
that
rel
and
is
has
been
researching
and
is
planning
to
you
start
in
an
or
in
earnest
soon,
yeah.
E
D
E
Okay,
yeah
so
I
think
three
months
ago,
suppose
they
say
CF
for
Kate's
day
on
Sousa
and
discuss
it
to
be
moving
to
more
combative,
called
foreign
jazz.
It's
one
thing
that's
been
up
in
my
has
it
we
need
to
have
that's
been
up
in
like
in
the
conversation
we
don't
have.
Good
restrictions
like
borscht
gives
us
and
people
don't
know
good
practice.
E
I
know
how
to
divorce
in
sees
borscht,
probably
but
not
is
gratis,
and
my
idea
was
to
get
my
knowledge
of
respect
versatile
experiences
when
people
when
the
concierge
are
call
for
a
cation
term
and
tyranny
waters,
a
good
things.
What
I
know
from
community
try
to
incite
also
documents
that
I
could
find
house
a
different
people
are
also
similar
comments.
E
What
his
last
things
and
idea
is
that
we
need
to
show
that
God
foundry
is
becoming
more
kubernetes,
II
welcome,
eyes,
idiomatic,
not
called
native
native,
but
why
do
I
think
that
it
looks
more
like
sound
says
that
experts
wrote
a
note
something
like
I
know.
Some
random
people
said
just
need
to
get
their
money
right
now
from
the
company's
road
as
I
just
I
know.
Just
great
Dockery
much
as
I
said,
so
that's
why
I
chose
this
document
and
it
goes
from
from
like
lowest
level,
how
to
write
code.
E
E
E
I
mean
I
want
people
to
give
a
bit
more
feedback
I
and
what
is
I
know
what
can
be
proved.
How
can
we
get
this
thing
in
in
the
process?
My
one
more
ideas
that
the
document
is
a
guidelines
itself,
don't
require
any
tool
right
now.
So
if
you
decide
we
can
have
some
validation
tool,
but
it's
just
not
required.
You
can
achieve
without
any
and
ideas
that
it's
not
attached
to
any
tool
to
deploy
things
such
as
ham
or
anything
else.
E
E
There
might
be
some
improvements
from
the
language
as
well,
that,
like
Sporty's,
has
to
be
done,
might
be
there
in
my
head.
It
was
that
I
chopped
off
this
document
will
be
like
requirement
for
the
component
to
become
in
co-founder
II
organization.
I
could
add
to
say
comidas
things
that
cloud
foundry
people
built.
It
won't
be.
Let
say
you
know
promoted
to
the
Michel
qualified
organization
from
incubator
until
they
satisfy
some
like
mast
stains.
E
You
can
keep
it
an
incubator
if
you
want,
but
if
you
want
to
have
it
in
call
find
domain,
it
should
satisfied.
So
that
means
that
it's
production
ready
and
it's
the
same
as
as
a
component.
So
it
will.
Everything
will
be
the
same
one
more
things
that
I
think
in
future
should
have
that.
We
should
have
at
some
point
where
we'll
choose
the
template.
We
should
have
the
same
properties
for
each
component.
So
let's
say
if
I
style.
E
If
I
want
to
say
request,
I
I
can
set
requests
for
each
component
is
the
same.
I
know:
value
sample
from
her
more
same
team
played
from
I,
know
car
for
some
team
played
from
and
as
simple
I
can
language.
What
is
basically
the
same
team
plate
I
might
change
the
higher
level
or
case
it's.
This
it's
for
copy
is
for
irony
is
for
something
else,
but
general
things
like
I,
say:
interest
number
of
witnesses,
o
DM
type
in
boss.
E
F
B
Now,
I'm
not
sure
how
it
was
actually
distributed.
That
I
think
I
stumbled
across
it
in,
like
the
kind
of
main
document
that
every
created
two
to
kind
of
collect
references
to
to
other
documents,
but
I'm
not
sure
that
it
was
actually
sent
out
of
the
cloud
foundry
mailing
list
to
or
do
you
want
to
like
keep
it
in
a
smaller
group
first
and
then
so.
E
I
come
outside
to
the
big
Milan
list.
I
was
like
okay.
I
want
to
finish
this
thing,
pathetic,
just
drop
this
link
and
I
can
I'll
share
too
besides
here
for
case
channel
as
well
separately.
I
think
that's
a
unless
so,
unless
I
will
be
something
quite
big
that
people
want
to
contribute,
I'll,
send
it
to
the
yeah,
French
Channel
and
then
my
whole
food
visit.
E
A
Think
it
would
be
okay
Alex
if
you
were
to
post
it
to
CF
dev
and
explain
like
it's
very
open
for
a
comment
and
the
current
state
of
it
and
I
think
that
would
be
perfectly
fine
and
really
the
people
who
are
paying
it.
Who
would
want
to
comment
I
think,
will
comment
and
people
who
are
just
curious,
I.
A
Don't
know
you
could
add
a
section
at
the
top
stating
the
state
of
it.
I
guess
I
guess
also
I
was
wanting
to
suggest
Alex.
It
might
be
interesting
to
have
for
free
to
have
some
sort
of
table
or
something
to
say
you
know
say
for
Kathy.
What
have
they
adopted
are
not
adopted,
UAA
adopted
it
not
adopted,
and
then
that
may
be
also
a
source
of
feedback
for
you
about
any
of
these
guidelines.
E
D
E
Don't
think
so
I
might
but
I,
don't
think
anything
like
people
engaged
I'm
to
be
honest,
like
from
the
player
adding
inside
its
heart
from
dr.
Joe's
point
at
like
saying:
okay,
this
is
required
for
the
product
because
it's
it's
nice
to
have,
but
it's
not
like.
Okay,
this
is
the
most
important
feature.
You
just
lots
of
face
wall
nice-to-haves.
It
has
to
be
run
eventually,
but
if
it's
not
official,
it's
hard
to
say
like
okay
people,
let's
do
these
things,
because
why
it's
not
top
priority
I
was.
C
Wondering
are
there
already
some
tools
like
a
linter
that
does
some
of
these
checks
like
it
could
like
it's
pretty
mechanic
to
check
if
there
are
pub
disruption,
budgets
for
all
pods
or
like
if
I
don't
know,
everything
has
a
readiness
probe.
Are
there
already
tools,
because,
if
there's
a
standard
tool
and
has
a
set
of
requirements,
that
might
be
easier
to
convince
others
that
this
is
probably
a
good
guideline,
so.
E
G
G
I'm,
joking
intentionally,
I
can't
get
away
from
the
thought
that
none
of
these
things
were
necessary
when
you
think
CS
and
I,
don't
know
which
one
of
our
things
that
we
do
other
than
maybe
my
sequel
isn't
a
stateless
fact
like
what
white
white
just
for
ceaselessly.
If
there
was
a
like
in
a
really
CID
or
call
it
whatever
right.
G
It
really
does
today
it
really
doesn't
be
politics,
but
it
I
think
every
knee
should
be
doing
Potter
such
matters.
It
really
should
set
things
up
so
that
your
app
will
not
have
that
downtime
as
long
as
it
follows
12
facts
or
apples
it
given
that
I
mean
that's
what
I
think
the
value
of
CF
is
supposed
to
be.
Instead,
if
you
do
in
this
whole
document,
you
just
do
a
CF
push
and
all
these
defaults
are
kind
of
correctly
set
and
it
just
works,
and
you
don't
care
about
that
stuff
and
I.
G
H
Think
there's
something
here
like
like
different
levels
of
like
we
do
I
mean
I,
pushing
her
I
really
would
just
do
the
deployment,
but
you
still
have
the
problem
of
configuration
management.
How
do
you
share
configuration
values
between
applications
and
that's
what
we
saw
on
the
templating
demos
before
like?
How
do
you
reuse
configuration
data,
and
then
you
have
like
guidelines
on
how
applications
should
behave,
that
they
should
read
a
configuration
file
from
somewhere
or
their
data.
Con
directory
should
be
configurable.
H
They
should
be
containerize
able,
so
they
should
fit
into
containers
at
all,
and
that's
also
like,
on
the
application
level,
the
set
of
guidelines
which
are
useful
and
we
might
need
to
have
something
about
packaging
about.
How
are
they
supposed
to
look
end
up
our
containers?
Are
we
going
to
install
all
the
components
into
the
same
folder
or
something?
So
it's
it's
really
very
much
like
the
normal
applications
which
you
have
on
the
notes
which
follow
like
filesystem
guideline
or
something
I,
think
we
need
guidelines
for
several
levels
and.
H
E
So
I
want
to
say
that
I
mean
right
now,
Cloud
Foundry
does
from
one
point
more
then.
What
is
this
document
like
packages
covered
and
it
filled
the
cart
in
any
way?
I
don't
think
will
require
people
dildo
cream,
I,
just
hint
if
required
bill,
don't
talk
images
we
won't
like
requires
and
to
provide
labels
if
they
provide
strategies,
so
some
best
practices
like
definitely
after
my
table
some,
let's
say
there
is
a
as
I
said
several
sections.
E
So
let's
say
post
specification,
a
start
specification
article
subject:
ok,
this
is,
can
be
covered
by
your
component,
like
irony,
plus
plus
or
whatever
I
didn't
you
Wireless.
You
might
finally
remove
features,
but
I
don't
like
goodbyes
at
this,
a
your
support
will
be
covered.
I,
don't
think
that
the
code
guidelines
will
be
covered,
and
this
sound
said
we
should
do
and
assure
that
parka
jeans
will
be
covered
in
the
same
way
as
we
can
cover
it.
Right
now
might
be
at
some
point.
E
If
customers
will
ask
us,
we
can
do
like
okay,
we
have
these
labels
with
jaws
and
everything,
but
it's
more
important
for
developers
who
want
to
support
it's.
Like
hockey,
I
gather
requires
that
Sawa
deployed
my
application
and
I,
don't
know
which
version
do
they
use
and
they
don't
know
which
version
to
tell
me
the
ocean.
It's
not
that
much
of
a
case
in
say
CF
for
short
I
would
say
so
that
there
will
be
some
differences.
I
agree
that
something
can't
be
done
by
butter
tool.
E
D
I
mean
I
was
thinking
that
one
getting
some
deeper
engagement
from
the
component
teams
could
be
useful
just
in
terms
of
iterative
feedback
on
the
document
like
I,
don't
think
it's
in
a
form
yet
where
we
could
say
like.
Please
do
all
of
these
things
exactly
you
know
this
can
be
a
collaborative
discussion
between
the
teams
and
then
I
think
maybe
to
Jules.
This
point.
D
That's
a
an
interesting
aspect,
just
thinking
about
like
how
many
of
these
practices
should
pertain
to
CF
apps
as
well,
in
terms
of
how
ireenie
is
making
those
specifications,
so
that
could
even
be
another
like
meta
evaluation
table
in
this
document.
It's
like!
Well,
actually,
you
know
what,
if
these
practices
make
sense
for
apps
or
would
be
things
that
CF
apps
could
provide
as
a
higher
level
of
abstraction
to
component
development
right.
G
I
know
I'm
kind
of
beating
a
same
drum
on
this,
but
I
feel
like
if
CF
is
going
to
be
a
tool
for
people
to
push
twelve
types
of
apps
to
keep.
In
essence,
we
we
should.
This
is
a
big
opportunity,
we're
now
pushing
concepts
Cuban
at
ease.
We
should
be
looking
at
what
lessons
we
can
apply
CCF
and
if
it's,
if,
if
we
are
using,
that's
one,
that's
a
that's
a
it's
just
a
real
bad
smell
and
it's
like
something's.
That
means
we're
missing
something
right
like
like
what
Alec
says
is
right.
G
Like
some
of
these
things
may
not
be
correct
for
CF
push,
but
we
should
know
because
we
need
to
tell
us
we
need
to
tell
people
you
use
CF
push
if
they
fix
it.
You
can't
do
in
the
CF
push
like
they're
upgrade
between
versions
or
whatever.
That's
something
we
need
to
toss
in
for
the
CF
push
people
as
much
it's
something
that
we
need
to
cross
out.
I
I
feel
like
we're,
conflating
a
little
bit
here.
There's
there's
a
proposal
for
good
practices
how
to
run.
You
know
something
more
generic
on
kubernetes
right
and
then
there
is.
What
do
we
do
within
our
own
system?
Components.
I,
don't
think
there
is
disagreement
that
we
shouldn't
be
able
to
visit
any
but
I
think
there's
also
separating
or
genetic
like
it.
You
know,
Irina
factory
is
the
implementation
of
this
specification.
Now
this
specification
may
go
Leo,
that's
wider
than
that,
but
he
didn't
say
could
be
a
subset
of
that's.
G
A
really
good
way
of
putting
it
and
they
think
this
is
like
the
generic
everything
it
really
should
do,
is
a
meaning
in
sketchy
to
as
much
fat
as
possible
in
cooling
right.
So
what
I'm
talking
about
is
that
question
it
should
we
have
a
tool
to
do
it,
I
think
that
tool
is
CS
or
at
least
like
we
should
try
and
which
we
should
in
some
way?
Isn't
it
isn't?
J
Also,
my
feeling
is
like
I'm
bashed
added
significant
value
to
people
operating
the
platform
of
CF
in
several
ways
right,
one
of
them
was
it
enforced,
a
pretty
constraints
set
of
things
you
would
know
where
log
files
are
on
a
VM
which
scripts
I
executed
at
what
point
in
time
were
to
look
at
where
your
persistent
disk
got
mounted
and
and
alright?
Oh
of
course,
you
cannot
say
like
well
I,
do
your
thing:
it's
a
12
factor,
app
right.
G
People
do
want
to
be
able
to
pull
the
escape
action,
go
down
to
Cuba
Nettie's,
but
I
still
see,
there's
a
ton
of
value
to
that
opinionated,
high
level
thing
and
I
hope
there
is
otherwise
I,
don't
know
what
cloud
found
peaceful
right
like
I,
think
that
is
the
value
that
we're
talking
about
and
he's
having
some
opinions
and
guardrails
and
defaults.
On
top
of
that
things,
I
think.
A
A
G
Me
be
very
clear:
I
think
this
document
is
great
and
I
not
in
any
way
against
it
so
and
I
think
we
should
have
this
document.
I
think
the
document
should
be
on
a
repo
frankly,
I
think
it
could
just
immediately
put
on
a
repo
and
just
like
go
request.
This
we
do
things.
I
only
document
is
great
and
good,
and
all
that
kind
of
pushing
out
is
I.
Think
rather
than
kind
of
trying
to
manually,
do
all
the
specs.
We
should
be
thinking
about.
G
If
is,
is
it
possible
for
us
all
to
just
do
something
like
12
factor
apps,
because
that's
what
kind
of
trying
to
build
is
a
thing
that
lets
people
have
all
of
this?
That's
for
free.
So
we
need
the
document,
make
sure
we're
doing
this
right
and
make
sure
we
understand
this
stuff
and
for
the
cases
I
don't
do
it.
And
then
we
started
a
different
conversation.
I
think
about
whether
there
should
be
a
link
to
or
a
tool
that
does
it
and
and
all
I'm
saying,
if
I
kind
of
think
that
tool
is
building.
E
So
what
I
want
to
say?
That's
like
I
think
that
should
be
I'll
a
it's
like,
but
I
don't
think
it's
right
now
is
the
time
to
build
a
to
build.
The
table
is
also
validation.
If
it
jokes
I
like
like
how
far
do
yourself
is
the
borscht
immediately,
your
quiet,
like
I,
mean
yeah.
We
know
some
some
lessons.
You
definitely
help
that,
but
what
I'm
saying
that
we
don't
have
I,
don't
at
least
I,
don't
know
if
you
have
enough
lesson
from
could
by
the
slant
that
you
can
say.
Okay,
this
is
all
great.
E
Let's
feels
a
tool
because
we
know
exactly
what
you
want
to
build.
You
know
exactly:
what's
good
people
want
to
have
we
kind
of
facilities
the
same
as
golf
auntie,
but
the
DA
sisterly
for
this
for
the
tool
I
was
after
here
a
little
bit
more
from
Cabarrus
Community
before
we
start
building
for
the
is
this
to
like
going.
F
J
C
Do
agree
with
Jules,
though,
that,
like
like
a
lot
of
the
stuff
that
like
builds
up
Cloud
Foundry,
is
actually
like.
It
should
be
pushed
as
an
CFM
I
think
we
we
don't
have
solve
the
bootstrapping
part
here.
So
we
can't
immediately
start
with
that,
because,
like
I
mean
we
are
right
now
building
a
tool
that
applies
these
foresee
of
apps
right,
that's
ireenie,
and
we
learn
by
doing
that
and
like
all
this
lessons,
we
learn
there
should
immediately
apply
to
what
we
have
here.
I'd
like
take
away
the
my
sequel,
the
blobstore
and
I.
C
G
Isn't
the
point
of
the
abstraction
that
if
we
build
to
the
high
level
thing,
we
can
take
care
of
figuring
out
those
lessons
and
changing
those
lessons?
That's
that's.
Why
there's
a
value
in
that
higher
level
abstraction?
Is
we
don't
know
what
the
answers
today?
Neither's
are
the
people
who
will
be
using
the
thing
we're
building,
but
they
and
us
will
not
have
to
discover
every
one
of
those
lessons
themselves
and
keep
up
to
date.
B
D
B
To
the
rest
of
the
round,
should
we
keep
it
short
this
time
and
resume
next
time,
probably
with
like
the
people
who
haven't
had
a
chance
to
take
a
look
at
the
document
or
being
able
to
to
provide
feedback,
I'm.
F
Okay
with
being
short
today,
but
I
do
want.
I
do
want
to
take
this
document
in
context
with
the
discussion
about
the
gradual
withering
away
of
the
Bosch,
the
the
other
topic
that
we
were
talking
about,
or
the
other
frontrunner
the
dual
approach
in
see.
If
there's
any
conflict
from
what
we
talked
about
today,
with
with
our
like
the
plans
for
the
next
few
months
with
quarks
that
make
sense,
yeah.
B
Awesome
and
then
I
think
we're
also
looking
forward
to
seeing
the
document
from
from
psy
to
to
then
also
provide
provide
feedback
on
that,
because
I
think
like
along
the
lines
of
what
you
said,
Troy
that
might
kind
of
also
fit
in
in
that
kind
of
bigger
discussion
on
how
things
evolve
over
time.
Yep.
F
The
other
thing
just
quickly
before
we
go
Vlad
we're
just
talking,
we
think
cube
CF
is
ready
to
go
to
the
foundation
so
Chris.
We
will
talk
to
you
about
where
that
lives
and
probably
I'll
reach
out
to
Eric
well
to
see
about
the
where
it
fits
in
the
in
the
structure
and
sounds
good,
but
but
the
the
repo
I
think
is
ready.
We
just
got
to
get
a
final
thumbs
up
from
Jeff
hops
and
then
and
then
be
on
its
way.