►
From YouTube: Cloud Foundry Community Advisory Board Call [April 2020]
A
Okay,
welcome
everyone
to
this
community
advisory
board
meeting
for
April
15
20,
2000
P.
You
are
all
safe
and
well
you
and
yours.
We're
gonna
kick
off
with
our
regular
Cloud
Foundry
foundation
highlights
and
updates
from
I
believe
Swarna
I
see
we
have
chip
as
well.
Welcome
our
new
executive
director,
hey
how
y'all
doing
good.
C
Yeah,
let's
see,
would
you
would
you
add
in
here
yet
so
it's
in
the
in
the
dock
right,
we,
we
had
a
change
at
the
Board
of
Directors
level
and
just
I
I'm
always
reminded
that
some
context
about
what
the
foundation's
board
does
is
important,
they're
responsible
for
helping
to
manage
the
the
business
of
the
corporation,
that
is,
the
Cloud
Foundry
foundation,
so
they
approve
annual
budget.
They
you
know
work.
C
We
worked
very
closely
with
all
the
directors
and
the
board
as
a
whole
to
establish
what
the
priorities
for
how
we're
gonna
the
staff
will
spend
its
time
supporting
the
community.
They
helped
set
those
priorities
for
us,
the
you
know,
I've
said
this
in
other
context,
but
I
just
want
to
maybe
reiterate
what
what
we're
going
to
be
focused
on
in
support
of
everything
that
you
all
do,
there's
really
two
two
key
things.
C
So
the
first
one
is
that
we're
gonna
be
very
focused
on
trying
to
find
ways
to
help
the
community
grow
and
continue
to
build
on
its
a
fairly
healthy
community
right
we've
got
decent
diversity,
but
we
can
do
more.
We
can
do
better
right.
So
you
know
Sora
and
Chris
as
an
example,
it
started
to
reach
out
to
different
project
leads
to
PMC
leads
to
say
no.
How
can
we
think
about
the
project's
being
more
welcoming
for
casual
contribution?
C
I
think,
that's
a
that's
a
key
ingredient
that
we
haven't
been
doing,
particularly
well
as
a
collective,
so
there's
there's
areas
to
improve.
We
want
to
be
there
to
support.
You
know
everybody
in
make
this
room
changes
there
in
the
second
area
of
focus
for
us
is
to
is
to
really
simplify
any
of
the
kind
of
the
marketing
of
your
outreach
that
we
do
to
focus
on
a
very
straightforward
story:
right.
C
C
You
know
irregardless
of
what
coop
distribution
or
you
know,
cloud
provider
offering
you're
using
there's,
there's
a
pretty
significant
gap
between
enterprise,
developer
and
communities.
So
that's
that's.
What
we're
gonna
do
around
outreach
activities,
so
we're
kind
of
we're
simplifying
what
we
do
to
support.
All
of
you.
We're
we're
gonna
be
very,
very
focused
on
those
two
activities
and
I
think
that
that's
incredibly
appropriate,
given
the
the
state
of
the
project
overall
right
commercialization,
is
fairly
successful.
C
C
C
So
that's
what
we're
gonna
try
to
create
virtually
we're
gonna
work
very
closely
with
the
Linux
Foundation
events.
Team
they've
done
a
lot
of
work
on
different
platforms
and
tools
to
use
for
this
and
we're
gonna
do
our
best
to
try
to
create
something.
That's
not
just
people
staring
at
a
zoom
screen
all
day
because
I
think
that's
our
lives
anyway.
Right
so
hey!
You
know
how
do
we,
how
do
we
make
something?
That's
gonna,
hopefully
provide
not
just
a
chance
for
great
talks
to
be
highlighted
and
then
reused.
C
But,
ideally
you
know,
the
value
of
any
event
is
in
you
know.
The
hallway
track
were
another
way
to
look
at.
It
is
the
serendipitous
moment
of
collaboration
that
you
wouldn't
expect
otherwise,
so
we're
gonna
experiment,
we're
gonna,
try
some
new
things,
so
we'll
have
more
information
about
that
kind
of
shortly
in
terms
of
the
European
event.
C
Who
knows
at
this
point
we're
gonna
focus
on
getting
North
America
right,
we'll
see
what
happens
you
know
with
with
the
the
state
of
the
world
and
travel
when
everybody's
feelings
of
safety
around
travel
and
then
we'll
see
what
happens
so
I,
don't
think
I
have
anything
else.
Swarna
did
I
miss
anything
critical,
no.
C
D
It's
technically
this
Friday,
but
given
the
whole
new,
my
change
that
is
kind
of
still
in
the
works.
I,
don't
want
to
speak
for
the
entire
team,
but
I
think
we
will
push
that
out
a
little
more
because
there's
no
point
in
closing
the
culper
papers
before
we
announce
the
format
change
so
that
might
stay
open
for
a
little
while,
but
we'll
keep
the
community
poster
are.
C
B
D
A
Yeah
I
saw
the
change
that
those
three
projects
highlighted
quite
well.
It
looked
great
I
think
we
need
some
cross
references
between
for
Cades
and
cube
CF,
so
people
know
which
is
which,
when
they
land
on
one
page
of
the
other
yeah
see
I
sort
of
a
see,
also
sort
of
thing.
I'm
working
with
psy
on
that
and
I'll
be
working
with
the
docs
team
on
something
in
the
doc.
Stop
Cloud
Foundry
org
to
point
people
in
the
right
direction.
If
that's,
if
that's
how
they're
discovering
it.
C
I
did
mention
Paul
I,
think,
let's
I
skipped
over
that
when
I
explained
what
the
board
is,
but
yeah
yeah,
so
Paul
Feig's
own
from
VMware
elected
to
chair
the
board
and
again
that's
about
the
business
management
of
the
corporation
John
Rose
who's,
the
Dell
Dell
technology.
Cto
has
been
doing
that
since
2015,
and
so
it
seemed
like
a
good
good
opportunity
for
him
to
to
free
up
free
up
some
cycles,
he's
off
doing
other
things
right
now.
C
C
I
would
the
way
I
would
say
this
is
that
you
know
Google's.
Recent
focus
on
the
enterprise
has
led
them
to
see
that
Cloud
Foundry
is
very
important
in
the
large
enterprise
to
quite
a
lot
of
these,
these
big
companies
and
so
demonstrating
at
least
financial
support,
and
it
seems
material
to
their
customer
acquisition
and
retention
strategy.
Beyond
that,
you
know
not
sure.
Okay.
A
C
You
know,
III
think
the
answer
to
this
is
Troy,
the
the
the
continued
push
towards
rapidly
getting
a
really
robust
set
of
options.
For,
for
you
know,
a
great
debt
experience
in
topic.
Communities
is
something
that
Google
is
paying
a
lot
of
attention
to.
A
lot
of
companies
are
paying
a
lot
of
attention
to,
and
so
the
more
we
we
push
on
that
and
the
more
we
focus
on
ensuring
that
the
you
know
the
projects
are
prepared
for
new
contributors,
the
more
likely
it
is
that
that
diversity
will
continue
to
grow
cool.
A
E
Thanks
Trey
I'll
run
through
these
real
fast
because
we're
pretty
far
in
some
highlights
the
release.
Integration
team
released
version,
0.1
of
cf4,
kate's
and
they've
also
been
working
on
refining
the
change
criteria
for
CF
deployment
version,
13
I
know
qcf
has
been
integrating
some
of
the
more
kubernetes
centric
deployment
options
for
Iranian
UAA
into
their
set
of
resources
for
deployment
instead
of
relying
on
the
Marshall
uses.
A
Then
I'll
just
mention
quickly
proxy.
Some
remarks
from
the
quarks
team.
They've
got
release
Florida
3.1
out
and
there's
been
a
lot
of
flux
in
the
CF
operator
to
accommodate
the
changes
in
cube,
CF
to
start
consuming
helm
charts
rather
than
Basha
releases
or
as
in
addition
to
Bosch
releases.
So
there
are
break
some
breaking
changes
between
the
quarks
operator
and
and
cube
CF
state
they're
they're.
Now
getting
back
in
sync
for
that
for
the
current
releases.
F
I
can
very
briefly
took
you
through
some
of
the
features
I
condemning
them
as
well,
if
you
wish,
but
I'm
gonna
in
industry
200,
which
is
rather
the
big
thing
for
us
most
of
it
was
another
hood,
but
some
of
the
things
that
are
visual
to
use
is
is
the
upgrade
to
angular
8,
where
we
basically
the
big
thing.
There
is
differential
loading
so
which
should
improve
Stratus
in
old,
browsers
other
things.
We've
done
clarifying
applications.
We
can
deploy
those
via
docker
image
now,
along
with
public,
get
the
gait
lab
or
file
archive.
F
Those
are
the
older
ones,
but
docker
image
is
the
new
one,
and
users
can
view
our
foundry
events
at
the
cloud.
Foundry
organ
space
level.
If
you
don't
you
a
as
well
now
we
have
a
quick
way
to
get
Ron
us
up
and
running
and
where
you
can
specify
some
credentials
for
a
single
user,
and
that
is
your
single
user.
Is
your
admin
for
that
that
stratus
lifetime?
That's
good
for
just
testing,
oh
yeah?
If
people
just
want
to
quickly
demo
out
what
or
see
what
it's
about,
we've
also
improved
error
reporting.
F
G
F
Jealous
dark
mode
and
in
3.1,
which
hasn't
been
released
yet,
but
we've
done
an
hour
see
today,
so
hopefully
that'll
be
out
within
the
next
week,
and
in
there
we've
basically
made
a
lot
of
improvements
to
scaling.
We've
had
some
feedback
from
various
users,
specifically
Comcast.
They
were
talking
a
lot
about
how
they
had
a
lot
of
entities.
F
A
lot
of
users
of
our
logs
so
now
in
we've
improved
the
way,
the
lists
that
we
have
to
present
those
we
handle
lots
of
rocks
identities
and
one
of
the
big
things
also
fir
the
cloud
gov
team
they're
interested
in
adding
users.
We
already
have
the
ability
to
invite
users
to
organizations
via
email
and
that
they
also
wanted
a
way
for
all
managers
to
assign
roles
to
people
who
were
outside
of
their
organization.
F
Another
community
feedback
community
one
was
a
we've
disabled
logging
of
jet
stream.
Api
requests
optionally.
That
could
be
a
bit
spammy
in
the
jet
in
our
back-end
log.
So
we
can
now
disable
those
we've
updated
the
way
that
the
Cloud
Foundry
deploy
works,
sort
of
sorry
deploying
applications.
So
that
now
supports
all
the
latest
svey
three
features
such
as
multiple
bill
packs
and
a
few
small
nice
ones.
We've
support
now
the
of
Gravatar
for
user
profile
icons.
F
A
F
F
A
G
G
So
this
is
actually
live
now
hasn't
officially
been
announced,
but
we're
introducing
it
so
that
you
all
can
start
kind
of
taking
a
look
and
poking
and
prodding
at
things.
So
I
will
go
through
this
relatively
quickly
and
show
you
kind
of
some
of
the
I
think
interesting
parts.
But
our
goal
here
is
really
to
collect
and
curate
a
set
of
tutorials
that
are
kind
of
easily
consumable.
You
know
short
in
nature
for
various
relevant
audiences.
G
You
know
it
doesn't
really
matter
what
the
what
the
topics
are,
but
I
think
we
do
a
great
job
of
documenting
the
platform.
We've
got
some
very
good,
long-form
I
think
training
out
there
across
different
companies,
but
I
think
in
the
community.
We
could
do
better
at
introducing
people
that
are
kind
of
core
concepts
and
doing
some
of
those
things
quickly,
and
that's
that's
really
what
our
aim
is
here.
So
you
can
start
poking
around
at
this.
G
It's
out
at
tutorials,
Cloud,
Foundry,
org
we'd
been
building
some
of
the
backend
infrastructure
to
support
this
and
I'll
show
you
what
some
of
that
looks
like
here
in
a
second
as
well
as
some
of
the
initial
content,
but
our
goal
here
is
really
for
people
to
get
involved.
So
if
you
have
ideas,
if
you
have
thoughts,
if
you
want
to,
you
know
make
a
quick
tutorial.
15-Minute
thing,
a
ten-minute
thing,
even
you
know-
maybe
up
to
about
a
thirty
minute
thing
on
some
particular
topic
that
you
think
would
be
relevant.
G
Please
jump
in
slack
in
and
touch.
Let
me
know
what
that
is,
we're
taking
on
the
onus
of
maintaining
and
making
sure
that
all
of
those
stuff
is
is
kept
up
to
date
and
all
that
so
I'll
leave
time
for
questions,
but
just
to
kind
of
give
you
an
idea
of
what's
in
here
now
and
what's
going
to
be
in
here
for
launch
in
the
next
few
weeks.
G
Currently,
there
is
not
a
section
on
what
is
called
foundry
I'm
working
on
that
behind
the
scenes,
but
that
will
be
here
for
the
launch,
and
so
we
really
want
to
give
people
a
good
understanding,
a
really
quick
review
of
what
this
thing
is
and
why
it
matters,
because
they
think
we've
seen
over
the
course
of
the
entire
project
that
people
just
getting
started
with
cloud.
Foundry
is
one
of
the
biggest
impediments.
They
just
don't
understand
how
to
start
with
it,
because
there's
so
many
different
parts
and
pieces
we
are
addressing
this
whole.
G
You
know
question
of
cloud
foundry
and
kubernetes
here.
This
is
still
actively
being
worked,
but
there
is
a
draft.
That's
out
there
that
you're
welcome
to
take
a
look
at
for
any
of
any
of
you
that
have
seen
the
Tri
cloud
foundry
stuff
that
we
put
out
previously
so
try
cloud.
Foundry
com.
We've
actually
moved
that
in
here
in
a
tutorial
format,
and
it
walks
you
through
kind
of
getting
a
cloud
foundry
instance
or
getting
an
account
of
an
existing
cloud.
G
Foundry
instance-
and
you
know,
the
basics
are
deploying
and
a
half,
and
you
know,
logging
in
and
targeting
that
whole
thing.
Provisioning
databases
scaling
killing
all
that
fun
stuff,
that
is
in
here,
but
we
still
felt
that
that
was
a
little
bit
of
a
too
high
of
an
impediment
because
you
got
to
go
pick
a
provider
and
then
you
got
to
figure
out
how
to
actually
get
an
account.
G
But
we've
implemented
this
on
category
if
you
haven't
used
it
before,
it
is
basically
an
integrated
learning
environment
where
we
actually
have
a
real
terminal
window
running
over
here
and
it's
typically
hooked
up
to
live
systems,
and
so,
when
you
do
cloudy
coda
training
like
if
you
were
doing,
let's
say
some
form
of
kubernetes
training
behind
the
scenes.
They'll
typically
spin
up
a
mini
cumin
sense
for
you
and
hook
it
up
to
your
browser.
For
us
that
model
doesn't
work
great
with
Cloud
Foundry,
because
the
installs
take
a
while.
G
So
what
we
ended
up
doing
was
actually
provisioning
a
cube,
CF
cluster
on
GCP
and
basically
hooking
that
up
behind
the
scenes,
and
so
it's
the
same
tutorial.
But
when
I
actually
start
this
tutorial,
I
actually
have
Cloud
Foundry
instance:
I
actually
have
an
organ
space,
I
have
a
username
I'm
already
authenticated
and
everything
is
basically
hooked
up
and
ready
to
go.
There
are
still
some
kind
of
I,
don't
know
rough
parts
of
katha
coda,
I,
don't
know
if
you
know
the
history,
but
they've
been
acquired
by
O'reilly
and
things
have
been
getting
better.
G
It's
a
really
good
platform,
but
you
know
some
of
these
things
are
unfortunately
things
we
have
to
live
with,
but
the
idea
here
is
anybody
can
actually
go
through
the
entire
tutorial
of
actually
using
Cloud
Foundry
and
pushing
applications
against
the
real
running
instance.
Again,
it's
running
on
cube
CF
right
now.
The
cube
CF
is
relatively
small.
G
So
we've
put
some
things
in
place
to
constantly
repave
and
update
URLs
and
replace
things,
but
there's
actually
no
way
for
you
to
go
in
here
and
get
the
username
or
to
get
the
password.
Sorry,
not
the
username,
to
do
anything
kind
of
major
with
this
with
this
anyway,
but
again
it
takes
them
through
the
whole
process
of
deploying
an
application,
the
binding
services
of
scaling,
the
application
killing
the
application
you
know
and
that
that
whole
kind
of
try
cloud
foundry
thing
with
basically
no
barrier
of
entry.
G
You
just
need
a
browser
that
catagory
works,
so
that's
primarily
what
I
wanted
to
show
you.
Please
do
jump
in
and
start
looking
around
and
if
you
have
ideas
on
content
you
want
to
add.
You
know,
please
jump
in
slack,
there's
a
slack
channel
and
and
reach
out
to
me,
and
let
me
know,
we've
got
kind
of
all
the
infrastructure
stuff
behind
the
scenes.
So
you
don't
need
to
worry
about
any
of
that.
You
can
basically
just
write
some
markdown
and
we
should
be
good
to
go
so
I
will
pause
there.
G
C
B
G
Think
a
lot
of
what
you'll
find
here.
That's
in
there
now
is
really
aimed
at
the
getting
started
type
stuff,
so
it
might
not
be
relevant
for
them,
but
we
wanted
to
really
kind
of
tackle
the
barrier
of
entry
issue
that
I
think
we
hear
about
on
Twitter
a
lot.
So,
oh
and
incidentally,
the
intention
is
also
to
offer
this
whole
try.
G
Cloud
Foundry
experience
on
Stratos,
because
I
actually
do
work
on
the
cloud
backup
team
part-time
as
well,
and
we
have
a
lot
of
users
that
just
do
everything
through
the
UI
and
we
want
to
support
that
as
well,
so
cool.
So
it's
coming
also
feel
free
to.
If
there
are
people
that
you
think
would
be
valuable
and
feedback,
please
definitely
share
the
information.
A
C
Alan,
the
other
thing
I
just
reiterate,
and
it's
Steve
already
said,
but
I'm
gonna
make
a
really
specific
reiteration
here.
This
is
an
awesome
opportunity
for
projects
to
think
about
not
just
like
the
formal
documentation
side,
but
if
you've
got
a
really
cool
new
feature,
a
quick
tutorial
might
be
a
great
idea.
It's
a
different
format.
Right,
it's
lighter
weight,
so
you
know,
there's
there's
been
a
limited
number
of
people
that
have
contributed,
but
it's
on
github
right,
so
PR
is
welcome.
Please.
C
H
G
Yeah
that'd
be
great
there.
There
is
a
mention
of
C
uppercase
and
keep
C
F
in
there.
But
again
you
know
we're
open
to
whatever
you
know.
If
you
have
thoughts,
if
you
have
things
you
want
to
add,
if
you
want
to
add
a
separate
section
on
C
F
for
kids,
that's
perfectly
fine
too,
for
everybody!
That's
what
we're
here
for
yeah.
A
A
G
J
Yes,
thanks
Trey,
first
off
for
those
of
you
that
don't
know
me:
I'm
Kashia,
the
product
management
manager
at
VMware
on
the
build
path
site.
We
wanted
to
just
take
some
time
to
announce
the
potato,
build
packs
project
launch
to
you.
Folks,
I
don't
have
too
much
like
official
content
prepared,
maybe
just
walk
you
through
the
brand-new
website
that
the
cff
put
together
and
then
answer
some
questions.
J
So
first
off
Kato
build
packs,
we're
just
launching
this
product
as
a
collection
of
our
implementations
of
cloud
native,
build
packs.
A
huge
motivation
behind
this
launch
is
sort
of
tying
to
a
lot
of
messaging.
That
chip
said
a
little
earlier
around
expanding
a
little
bit
more
broadly
beyond
just
the
Cloud
Foundry,
a
community
as
we
expanded
into
kubernetes
and
all
and
the
overall
messaging
I
think
we
want
to
get
forward
with
this
launch
is
just
that.
Build
packs
are
not
just
for
Cloud
Foundry,
but
for
everyone
beyond
and
using
any
cloud
native
platform.
J
J
Created
so
I
put
the
FAQ
together
yesterday
and
the
CFF
really
polished
up
the
site
and
I'm
really
liking
how
it
looks
now
so
as
soon
as
we
launch
we're
gonna
be
supporting
java.net
core,
go
nodejs
nginx
and
PHP
language
families
in
the
FAQ
we're
planning
on
like
adding
in
roadmap
things
like
that
over
the
next
couple
weeks.
As
soon
as
we
launch
yeah
that's
effectively
all
I
had.
Maybe
we
could
pause
here
and
just
answer
some
questions
around
this.
A
J
J
The
picado
build
packs
project
is
just
focused
more
so
on
implementing
build
packs
that
conform
to
that
specification.
We're
a
little
lucky
here,
because
we
have
Stephen
who's,
also
like
a
core
maintainer
of
both
the
CNCs,
build
packs
project
cloud
native,
build
packs
project
and
also
the
potato
side.
So
a
huge
part
of
I
think
the
website
content
FAQ
things
like
that
or
more
so
message
to
around
sort
of
differentiating
the
two,
because
that's
a
big
question:
we've
had
okay,
that.
A
I
Well,
the
build
packs
IO
project.
If
you
have
the
PAC
CLI
locally
and
run
pack
suggest
builders,
it
gives
you
a
list
of
different
kind
of
open-source
build
packs
that
are
out
there
from
contributors
to
the
project's
lists,
the
CI
build
packs,
which
will
say
potato
dough
packs
and
it
also
lists
for
Okaloosa,
edible
packs
for
cognitive
impacts.
So
the
the
project
may
do
some
curation
and
and
more
visibility
around
build
packs
that
are
out
there.
But
it's
kind
of
a
goal
of
that
project.
I
Not
to
you
know,
say
these
build
packs
are
better
than
is
right,
it's
about
just
about
the
specification
and
tooling
and
making
sure
that's
really
easy
for
platforms
any
platform
to
support
in
bill
impacts.
It's
also
worth
I.
Think
noting
that
with
potato,
we
really
want
to
double
down
on
that
kind
of
vendor
neutrality,
and
you
know
kind
of
there's
a
bull,
fair
governance
and
all
of
those
things.
You
know
that
we
really
want
to
turn
the
potato
project
into
a
you
know
something
with
a
much
larger
community
than
what
Cloud
Foundry
build.
I
A
A
D
I
Can
take
this
one,
so
the
K
PAC
is
being
integrated
into
CF
for
Kate's
and
so
it'll
be
the
way
that
CF
for
Kate's
does
build.
Pack
builds
in
the
future,
something
else
we're
doing
to
make
sure
that
exists,
existing
deployments
and
people
who
can
upgrade.
You
know
to
run
CF
on
top
of
kubernetes.
Yet
something
else
we're
going
to
make
sure
that
they're
very
well
supported
is
we're
producing
this.
I
This
will
still
probably
be
Cloud
Foundry
branded
instead
of
potato
branded,
but
we're
we're
producing
sort
of
shim
versions
of
the
new
build
packs
that
will
continue
to
run
our
foundations
to
make
sure
people
know
keep
receiving
bill.
Peck
updates
and
we
don't
end
up
maintaining
two
generations
of
build
packs.
So,
while
the
potato
build
packs
were
like
really
modular
and
kind
of
fit,
the
new
API
like,
for
instance,
the
node
build
pack,
is
like
no
didn't
yarn,
yarn,
install
and
NPM,
and
all
these
little
parts
will
we'll
be
releasing
a
Cloud.
I
Foundry
compatible
build
pack
that
kind
of
wraps
all
those
together
along
with
the
v3
tooling,
and
runs
it
on
top
of
the
b2
tooling,
on
Cloud
Foundry.
It's
a
surprise.
We
could
make
that
work,
but
the
it
won't
have
some
of
the
performance
benefits
as
if
you're
running,
on
top
of
a
proper
cloud
medical
tax
platform
like
Kay
pack
or
it
packs
you
lie
or
whatnot,
but
it
should
bring
a
lot
of
the
new
functionality
and
features
and
sort
of
transparency
of
the
new
build
pack
model
back
to
Cloud
Foundry.
A
I
Faster
they're,
like
there's
some
some
app,
especially
on
rebuilds,
take
a
second
or
two
seconds,
even
if
the
build
pack
has
to
start
a
container
and
run
due
to
the
really
aggressive
layer
we
use
again.
Those
those
performance
benefits
won't
show
up
when
you're
running
the
chemin
versions
on
Cloud
Foundry,
but
it
will
show
up
when
you're
running,
with
kpac
integrated
the
CF
for
Kate's
or
on
any
other
platform
that
supports
cloud
minute,
build
packs,
yeah.
A
H
Yes,
so
right
now
we
have
a
one
big
builder
good,
that
contains
all
of
this
bill
packs.
The
plan
is
to
work
with
the
Cappy
team
and
the
Decatur
bill
paxton
to
have
more
granular
set
of
bill,
packs,
configure
or
declared
indicia
for
Kade's
resources.
So
you
will
individually
see
each
of
this
bill
packs.
D
B
I
That's
this
is
complicated
the
what
I
was
referencing
before
is
just
the
rebuild
time,
which
doesn't
the
container
runtime
doesn't
affect
just
the
process
of
generating
a
new
image.
If
you're
deploying
you
know,
applications
the
container
runtime
contain
if
you're
running
just
container
D
versus
you
know
running
into
dr.
Damon,
the
doctor
Damon
is
bad
at
pulling
a
you
know
like
it'll
repulse
entire.
I
Deploy
should
be
very
fast
on
a
platform
with
container
D,
because
only
the
change
layers
will
get
transferred
that
you
know
node
VM.
In
the
case
of
a
stack
update,
only
the
change
layers
for
all
the
you
know,
containers
on
the
you
know,
node
be
it
will
get
transferred
there
and
everything
can
I
flip
around.
But
if
you're
running
a
doctor
damn-
and
there
are
definitely
cases
where
things
are
a
lot,
more
data
has
to
be
pulled
the
and
we
don't
foresee
docker
making
any
changes
to
that.