►
From YouTube: CF-for-K8s [March 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
A
Unfortunately,
this
time
we
kind
of
have
the
leftover
topics
that
we
couldn't
touch
upon
for,
like
the
last
instances
of
this
meeting,
and
as
indicated
in
in
the
chat
having
jewels
on
the
cob
would
have
been
good,
also
to
see
some
signs
of
life
from
Great
Britain,
but
yeah-
that's
so
he
probably,
or
maybe
he
still
joining
other
than
that
I
guess.
One
one
topic
for
this
round
would
be:
let's
say,
assuming
that
we
kind
of
don't
have
too
many
kind
of
standards
topics.
A
Is
there
anything
that
we
should
do
to
like
the
frequency
of
the
meeting,
or
should
we
kind
of
move
to
a
more
regular
agenda
with
like
teams
working
on
various
topics?
Just
providing
updates
I
think
I
would
be
probably
a
discussion
beyond
the
topic
that
I
think
has
won
the
poll
with
like
three
votes
out
of
a
total
of
four
votes
provided,
which
is
what
are
we
doing?
Next?
A
B
A
See
all
right,
I
mean
he
was
arguing,
saying
it's
no
longer
and
I
really
1.0,
demo
and
I
would
agree.
Probably
it's
a
1
point
something
they
mark
meanwhile,
but
they
are
getting
an
update
where
they
are
headed.
It's
probably
a
good
thing
to
have,
but
especially
for
this
topic,
we
wouldn't
need
Jules
in
the
column
right
yeah.
Otherwise,
how
do
you
do
that.
A
So
so
rudely
employes
was
something
that
we
kind
of
voted
for,
because
that's
something
that
people
use
on
our
and
already
on
and
obviously
like
the
whole.
The
whole
discussion
ties
into
like
feature:
comparisons,
less
feature
parity
where
I
thinks
I
mentioned
that
like
this
is
also
something
thats,
that's
upcoming,
to
identify
at
least
where
the
gaps
are
yeah.
C
C
B
As
for
changing
the
the
format,
I
think
we
just
need
to
be
a
little
bit
more
active
about
suggesting
new
topics,
because
now
we've
we've
we've
whittled
it
down
to
the
two
that
we
we
either
don't
get
to,
or
we
don't
close.
You
know,
we've
talked
about
option
one
before
what
are
we
not
doing
next
now
and
I
would
love
to
change
the
wording
of
that.
What
should
we
be
doing
its
citizens
and
so
I
to
that?
B
To
that
end,
I
did
post
this
blog
post,
which
got
a
lot
of
traction
thanks
to
the
foundation
which
I
sort
of
unilaterally
said
what
we're
doing
as
a
community,
because
I
wanted,
of
course,
to
present
a
very
united
front
and
we
have
F
and
brocades
moving
in
the
same
direction
and
broadly
that's
true.
It
wasn't
always
true
like
we
had.
You
know
a
couple
of
sick
meetings
ago.
It
was
actually
kind
of
contentious.
B
So,
first
of
all,
has
anyone
read
that
and
objected
to
anything
in
there,
because
I
I,
just
wrote
it
I
didn't
sort
of
consult
with
too
many
people.
I
ran
part
of
it
by
sy.
To
say:
is
this?
Okay
with
you
what
I'm
saying
about
SIA
for
K
eights,
but
I,
just
kind
of
barged
ahead,
and
did
that
any
any
feedback
from
that
and
or
any
anything
we
need
to
talk
about
from
the
has
there
been
more
inquiries
because
of
that
post
in
the
press,
press
release
a.
B
Not
required
reading
or
anything
I,
just
I
just
want
to
check
cross-check
what
I've
written
with
you
guys,
which
is
basically
you
know,
Cube
CF
is
awesome,
but
if
you
so,
this
is
my
outstanding
action
item
from
the
last
cig
meeting,
which
is
disambiguate
CF,
4k,
eights
and
cube
CF
I
had
an
initial
conversation
with
the
docs
team,
but
I
haven't
followed
up
on
that.
So
the
plan
was
to
do
a
blog
post
first
to
just
sort
of
say
this.
B
This
is
the
keep
CF
project
because
it
was
going
into
incubation
terrible
time
to
use
that
word
in
a
blog
post
and
here's
if
you're
wondering
here's
CF
4
KS,
which
is
the
kubernetes
idiomatic
components
which
are
being
integrated
together
in
this
repository,
and
this
is
what
the
two
of
them
do
so
so
we'll
I'll
pick
up
the
doc
thing
again
and
and
I've
made
a
contact
with
someone
on
that
team.
That
was
okay
with
me,
exploring
that
further,
but
I
haven't
done
that
yet
just
just.
C
B
E
Awesome,
so
we
are
planning
to
lease
0.1
release
of
C
it
for
Kate's
we're
hoping
to
do
this
this
week.
There's
some
small
document
documentation
updates
we
want
to
make
before
we.
We
actually
cut
that
release,
so
that
should
be
out
and
at
this
week
or
early
like
Monday
or
Tuesday,
and
get
this
here,
push
with
Bill
packs,
and
it
contains
all
the
highlights
and
on
issues
in
the
release.
Note
so
you'll
get
to
know
what
you
can
or
cannot
do.
E
So
that's
that's
coming
up
leave
what's
next
for
us
is.
We
are
now
focusing
on
the
contribution
workflow.
So
how
do
we
consume
releases
from
contributing
projects
as
we
do
with
CFD
today,
alright,
nice
bits
body.
We
want
to
try
to
automate
that
as
much
as
possible
and
create
that
sort
of
contract
between
us
and
the
contributing
teams.
So
that's
that's
in
Prague
progress
and
we
plan
to
submit
the
proposal
to
you,
see
updating
the
dev
mailing
list
to
get
feedback
from
the
community
right
now.
E
It's
going
to
circulation
within
the
team
at
the
moment,
so
pretty
excited
about
that
yeah
and
the
other
were
other
part,
is
we're.
Also,
looking
at
the
compatibility
matrix
of
what
Kate's
versions,
as
you
all
know,
K
cube
annuities
community
version
supports
up
to
three
versions
and
they
have
a
pretty
what
we
call
the
cadence
for
releasing
every
quarterly.
So
it's
pretty
the
pace
is
pretty
high,
so
and
every
minor
releases
minor
major
release.
So
every
every
quarter
of
the
release
they
have
some
breaking
changes
in
the
API.
So
how
do
we?
E
E
E
B
E
D
B
B
A
Okay,
nobody
else
has
an
additional
topic,
then
probably
wanted
to
pick
up
on
something
that
was
at
least
briefly
mentioned
in
some
of
the
calls.
But
then
I
think
I
keep
hearing
the
topic
every
now
and
then,
which
is
like
migration,
so
kind
of
moving
stuff
from
one
cloud
foundry
to
another
one
and
then
like.
Obviously,
there
could
be
variations
in
terms
of
what
that
other
Cloud
Foundry
actually
is
so
obviously
like
moving
from
a
posh
jcf
to
ku
180
space.
A
One
is
this
one
use
case,
but
I
guess
on
our
end,
we
even
have
use
cases
where
we
want
to
move
workloads
from
one
wash
face
tf2
to
another
one
so
wanted
to,
let's
say
see
if
there's
like
common
interest
in
in
the
topic
and
then
obviously
like
from
from
ours
perspective.
You
have
a
couple
of
angles
to
to
look
at
that.
Like
what
kind
of
migration
do
you
provides
the
to
you
like
even
consider
backing
service
content
in
that
migration,
or
is
that
something
that
you
keep
out
of
scope?
A
Do
you
quote
unquote,
just
like
migrate
over
like
org
structure,
socio,
forks
and
spaces
and
user
assignments,
and
do
you
then,
because,
like
people
will
anyhow
need
to
change
their
endpoints
kind
of
ask
them
to
reach
their
applications,
or
is
that
something
that
you
would
migrate
over
so
I
think
those
those
are
topics
that
are
are
of
interest
to
to
us?
Not
that
we've
really
spent
implementation
effort
on
it.
But
it
comes
up
every
now
and
then
to.
A
Well,
ultimately,
yes,
I
mean
backup
and
restore,
in
my
mind,
would
mean
like
backing
up
an
entire
Cloud
Foundry
system
and
kind
of
restoring
it
in
place.
So
to
speak.
So
I
think
when
I
when
I
say
migration,
as
I
said,
I
would
at
least
expect
the
the
endpoint
of
that
Cloud
Foundry
system
changes
and
then
like,
depending
on
how
sophisticated
you
you
want
to
be.
A
You
might
have
different
levels
of
migration
and
that
might
speak
and
some
some
support
to
move
over
things
like
user
assignments,
but
it
might
also
be
requirements
around
like
what
would
we
need
to
do
in
order
to
let's
say,
move
a
customer
or
tenant
that
actually
doesn't
want
to
move
right?
So
I
think
that's
like
the
ultimate
scenario
where,
like
the
need
to
move
more,
comes
from
us
as
a
platform
provider.
A
So,
for
example,
Cloud
Foundry
deployments
growing
too
big
might
be
a
use
case,
but
then
even
things
that
that's
I
mentioned
where,
like
for
exam,
there's
a
question
of
when
it
is
version
updates
and
then
do
you
wanna
like
in
place,
update
your
kubernetes
cluster.
Or
do
you
also
need
to
have
like
some
migration
tooling
to
actually
seamlessly
move
over
workloads
from
from
one
deployment
to
another
one?
So
it's
actually
a
very
broad
range
and
like
I,
don't
think
that
we've
settled
on
one
concept
or
one
end
of
the
spectrum
already,
but
just
so.
F
F
The
Cloud
Foundry
plugin
for
backup
and
restore
at
the
Cloud
Foundry
command
level,
which
is
designed
and
and
has
successfully
been
used
in
the
last
case,
you're
talking
about
where
a
customer
is
either
moving.
Hardware
they're
moving
the
same
similar
system
to
the
two
new
hardware
or
a
new
kubernetes
installation,
but
in
effect
it's
it's,
the
same
user
set
org
set
and
that's
that
tool
which
does
actually
have
some
options
it
the
data
services
you
have
to
handle
yourself,
although
there's
a
easily
prescribed
way,
you
can
do
that
depending
on
the
service.
B
And
Jeff
some
updates
there,
so
I've
actually
back-channel
with
Vlad
who's
in
another
call
we're
in
the
process
of
moving
that
plugin
into
the
foundation.
Ibm
has
expressed
interest
in
collaborating
on
it,
so
it's
an
API
based
backup
and
restore
and
we're
going
to
be
adding
some
things
to
it,
which
are
missing
right
now.
B
I
pace,
re
I
can't
paste
in
there
in
the
zoom
meeting,
but
it's
in
this
yet
4k
eights
channel
I
just
pasted
the
link
there,
so
we
planning
to
add
services
migration
or
serve
as
binding
migration,
and
you
a
a
deets
as
well
so
using
the
API
rather
than
getting
into
the
database
export
I'm,
not
exactly
sure
how
all
the
magics
gonna
work
and
Vlad
has
to
get
that
the
details
of
that,
but
they
have
something
in
the
works
and
are
gonna,
be
looking
for
collaboration
on
that
plugin.
Once
it's
once
it's
upstream.
F
C
Yeah
I'd
say
like
VMware:
we
don't
have
active
investment
and
it's
just
yet,
as
we
were
mostly
focused
on
investing
and
making
a
solid
place
to
land,
but
it's
an
area
of
interest
for
us
and
our
in
talking
with
some
of
our
customers.
I
think
they're
they're
thinking
that
they're
much
more
interested
in
how
could
they
do
this
in
a
deliberate,
slow
fashion?
C
Bring
it
they
there's,
not
I.
Think
the
idea
of
a
big
bang
migration
is
very
scary
and
hard
to
get
right.
That
there
was.
There
was
one
customer
who
was
saying
what
we
have
so
many
surrounding
things
on
top
of
Cloud
Foundry,
but
for
for
a
vendor
or
contributor
to
two
CF
to
imagine
you
could
build
like
a
perfect
migrator
tool.
C
You
know
there
might
be
pieces
that
might
be
helpful
for
that,
but
but
we
couldn't
really
manage
a
whole
big
bang
for
them
because
of
just
what
they
built
up
around
it
and
and
I.
Think
that
makes
a
lot
of
sense
when
you
think
about
the
capabilities
or
going
to
be
a
little
bit
different,
you
kind
of
want
to
be
able
to
say.
B
I
think
that's:
we've.
We've
heard
that
as
well,
and
it
depends
on
the
customer
entirely.
Some
people
want
to
do
an
in-place
upgrade
with
no
additional
hardware,
which
is
an
extremely
hard
thing
to
to
manage.
Other
people
are
like
no
I
would
never
try
that
I'm.
You
know
set
up
any
completely
duplicate
a
residual
that
residual,
a
parallel
CF
and
then
move
things
over
in
my
own
time,
so
yeah
I,
I
get
that
and
I
think
that's
the
idea
with
the
V
API
based
plugin,
that
it
just
provides
some
functionality
to
pull
down.
D
C
Yeah
and
I
think
that's
more
I
kind
of
from
the
from
the
outside-in
came
declaratively
like
these
are
kind
of
the
orgs
and
users
and
we'd
like
to
step
it
out
to
to
a
number
of
foundations,
because
our
installations
of
Cloud
Foundry,
because
they're
already
you
know
with
the
hardware
lifecycle
every
few
years
having
to
build
new
foundations
and
whatnot
and
then
trying
to
replicate
more
or
less
there
or
user
structure
and
telling
people
okay,
these
really
your
new
endpoints.
These
are
new
domains
and
please
manage
your
migration
over.
A
D
Yeah
I
don't
know
if
we
have
good
out
of
the
box
generic
solutions
for
those.
Yet
you
know
it
might
be
worth
us
trying
to
be
a
little
more
specific
around
the
kinds
of
migrations
that
we
might
be
trying
to
support.
You
know,
because
I
can
see
a
difference
between
migrating
1cf
instance
and
those
backing
services
from
like
a
network
in
one
geographic
location,
to
a
totally
other
geographic
location
versus
doing
one.
That's
more
local,
because
you're
trying
to
do
like
a
switch
from
a
Bosch
based
distro
to
a
gates
based
one.
You.
B
What
was
the
problem?
The
broker
didn't
know
about
the
fact
that
it
was
also
moving
I
can't
remember
no
cuz.
We
got
it
out
of
the
CCTV.
We
ended
up
going
in
and
doing
surgery
and
the
CCD
be
damn
it
to
make
it
all
fit,
but
it
would
have
been
really
nice
if
the
plugin
could
have
handled
that
somehow,
and
there
was
something
that
would
have
been
nice
in
the
API
I
think
to
make
the
migration
happen
and
I'd
have
that's
glad
about
that
as
well.
All
thinking.
A
B
Instance,
with
same
IDs
like
we
would
have
to
recreate
instance,
essentially,
rather
than
get
a
new
binding,
that's
why
we
couldn't
do
it
with
the
API
anyway,
we
we
had
the
requirement
in
there
somewhere.
So
once
this
goes
up
streamed
up,
the
plugin
goes
upstream.
We
could
it
make
more
sense
to
have
the
corresponding
feature
request
for
the
API
submitted
as
well.
C
It
really
needs,
like
some
concentrated
effort
to
like
kind
of
think
about
all
of
these
scenarios,
trying
to
be
transparent,
about
like,
what's
being
worked
on
at
all,
if
nothing,
and
how
to
advocate
for
attention
to
the
different
scenarios
and
and
curious
burned.
If
you,
if
you
have
folks
who
who
are
concentrating
in
this
area
as.
A
I
said
not
not
yet
fully,
but
we
see
that
topic,
as
is
definitely
something
that
that
will
come
up
I'm
kind
of
tempted.
Even
though
kind
of
looking
at
my
schedule.
I
I
won't
be
able
to
really
come
up
with
with
something
short
term
but
I'm
tempted
to
to
kind
of
put
something
together
in
terms
of
these
scenarios
and
thoughts
and
ideas,
and
probably
also
like
the
links
to
the
ruling
that
exists
today
and
then
probably
circulated
in
this
round
to
to
get
some
people
again.
Many
thoughts,
but
no
promises
on.
A
A
D
E
One
one
option
we
could
do
is
we.
We
Wallen
told
in
the
sense
that
we
have
a
set
of
topics
that
we
want
to
discuss
and
then
write
the
finer
individual
who
may
be
leaving
that
project
or
knows
what
about
it
and
then
give
them
at
least
a
week
or
two
advance
that
we
want
to
talk
about
this.
So
that
way,
the
agenda
at
leas
is
planned
out
for
two
weeks
three
weeks
out,
instead
of
asking
people
I
want
to
talk
about
it.
E
As
this
group,
we
can
seed
it
like.
We
can
just
do
a
dumping
sort
of
topics.
We
want
to
discuss
that
that
could
help
each
other
projects
or
other
projects
on
top
of
their
minds
and
then
and
then
we
find
the
right
person
who
could
help
us
deep
dive
into
that,
or
we
just
could
just
be
an
open
discussion
like
I
think
we
should
cede
some
topics
and
then-
and
then
we
just
say
here,
this
Tuesday
we're
gonna
talk
about
this
and
then
next
Tuesday
we're
gonna
talk
about
this.
A
Yeah
make
sense
so
I'll
take
another
action
and
come
up
with
such
a
collection
document
will
probably
send
it
to
to
the
select
channel
plus,
probably
by
a
mail
to
to
this
round
of
people
here
and
then
ask
everybody
to
come
up
with
their
topic
suggestions
and
then
plan
a
little
bit
upfront
on.
What's
going
to
be
presented,
I'll
make
up
my
mind
on
like
the
mode
on
on
how
we
do
that
yeah,
probably
one
one
week
in
advance
kind
of
closing
the
poll
already
and
then
letting
the
name.
D
A
D
You
know
everyone's
welcome
to
join
those
two,
and
then
we
also
have
the
cap
call
on
a
monthly
cadence
for
some
of
those
other
things.
So
I
think
we
should
maybe
plan
to
have
the
one
in
two
weeks,
but
maybe
that
could
be
a
just
like
meta
discussion.
Topic
is:
what
do
we
want
to
do
in
the
future?
With
this
meeting,
do
we
want
to
shorten
it,
make
it
less
frequent?
We
try
that
out,
make.