►
From YouTube: CNCF CI WG Meeting - 2018-07-24
Description
Join us for Kubernetes Forums Seoul, Sydney, Bengaluru and Delhi - learn more at kubecon.io
Don't miss KubeCon + CloudNativeCon 2020 events in Amsterdam March 30 - April 2, Shanghai July 28-30 and Boston November 17-20! Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects
B
A
A
A
C
D
Frederick
will
be
giving
a
presentation
on
the
kubernetes
ansible
provisioner
and
wanted
to
allow
plenty
of
time
for
Frederick
and
from
packet
and
Dustin
from
Oracle
to
give
their
updates,
and
then
we
would
jump
into
cross
cloud
after
that,
and
so
that
it
could
extend
into
a
big
Q&A
session
and
I
wanted
to
make
sure
we
had
enough
time
for
an
hour.
Speakers
as
well
I
mean.
C
D
B
B
Coincidentally,
there
was
just
a
announcement
today
as
part
of
Google
next
of
a
new
Google
Cloud.
No,
a
new
go
cloud
interface
that
will
I
believe
try
to
unify
cloud
provisioning
from
within,
go
and
just
started
to
look
at
that
and
I.
Think
I
have
someone
from
our
from
the
packet
community
interested
in
that
so
I
hope
to
report
back
on
that
next
week,
or
actually,
probably
next
month,
I
have
some
PTO
Kamiya.
D
D
D
The
Oracle
OCI
cloud
has
been
in
progress
on
the
CI
status
dashboard
on
CNCs
CI,
and
it
looks
like,
as
of
yesterday,
they
were
able
to
get
the
full
run
of
the
provision.
Script
completed
end
of
last
week
and
looking
for
the
next
step,
and
so
the
next
steps
is,
we
will
take
a
look
at
the
new
pull
request
and
compare
it
to
a
master
branch.
Do
some
testing
on
our
CI
development
branch
and
then
go
from
there.
D
D
E
E
One
of
them
is
I've,
been
working
with
the
network
service
mesh
group
in
order
to
in,
in
order
to
try
to
build
up
some
of
the
infrastructure
to
run
and
test
against
a
kubernetes
cluster
and
I've
also
been
working
with
the
open
daylight
community
for
some
similar
purposes,
where
we're
building
out
kubernetes
support
with
I
would
interoperate
with
daylight
and
so
effectively
in
open
in
the
open
daylight
community.
We
then
created
a
ansible
playbook,
and
what
it's
designed
to
do
is
it's
designed
to
deploy.
E
Because
one
option
is:
if
there's
duplicate
functionality,
then
we
could
migrate
off
of
that
onto
something
that
your
team
is
working
on
and
provides
or
if
there's
no
overlap
in
the
functionality,
would
it
be
useful
to
to
collaborate
or
work
or
find
a
way
to
to
provide
this
functionality
so
that
if
someone
comes
up
with
a
similar
use
case,
then
they
can
then
they
can
make
use
of
it
rather
than
world
around.
So
so
those
are
the
two
questions
that
I
that
I
really
have.
E
A
Sure,
before
we
respond
to
this
I
wanted
to
know,
is
there
a
link
you
can
together
or
tell
me
where
to
go
for
looking
at
that
playbook
sure.
C
Will
add
this
to
the
agenda
as
a
note
under
the
go
cloud?
I
just
did
a
quick
look.
It's
just
another
middleware
library,
that's
entry!
All
of
the
providers
are
entry,
so
strike
one
for
accessing
common
features
across
the
clouds,
not
even
deploying
them.
So
I,
don't
know
what
the
mileage
is
going
to
be
here,
but
that's
the
high-level
overview
I
would
think.
E
A
And
I
think
it
may
we
may
want
to
have
a
follow-up
on
this
for
sure
I'm,
looking
through
the
the
playbook
right
now
and
I
definitely
think
from
the
Linux
Foundation
IT
side,
where
they
have
a
lot
of
different
play
books.
This
would
be
a
good
thing
to
contribute
and
I
know
we
had
talked
about
that
seem
a
little
bit
about
that
separate
from
this
call.
I'm
not
sure
what
all
they
have.
I
know
that
some
of
their
installs
are
a
lot
more
complicated
and
deal
with
a
lot
of
other
things.
E
E
Gave
me
commit
access
to
the
LF
IT
project
in
order
to
start
pushing
these
type
of
things
up,
but
yeah
I
wanted
to
check
this
with
this
particular
group.
First,
to
see,
first
make
sure
we
don't
duplicate
effort,
because
I
can
easily
point
them
to
say.
Let's
use
this
for
this
particular
notebook,
but
yeah
I
think
the
lfi
t
is
a
great
place
for
this
to
land,
because
there
certainly
are
multiple
other
groups
who
would
be
good
to
to
work
with.
Do
you
use
this.
A
We
go
about
building
the
clusters
a
little
bit
different
and
it's
using
two
real
quick
would
be
terraform
and
then
cloud
in
it
and
for
bootstrapping
we
lay
down
everything:
I
don't
want
to
go
through
the
whole
skill
right
now.
We
actually
have
some
slides
and
demos
if
you're
interested
in
that
we
can
have
an
offline
call.
A
We
do
have
some
similar
things.
It
seems
like
the
tool,
though,
what
you're
doing
could
serve
other
purposes
than
what's
happening
there.
So
I
don't
want
to
say
right
off
the
bat
that
it's
duplicating
work,
there's
a
lot
of
folks
that
are
using
ansible
for
managing
various
parts
of
their
infrastructure.
So
I
think
it's
for
sure
useful
to
have
it.
We
don't
happen
to
use
ansible
for
the
dashboard
and.
A
As
far
as
like
collaboration
on
it,
I
think
the
first
part
is
probably
they
lfi
t,
and
I
don't
know
where
it
would
land
as
far
as
this
project,
but
there's
a
lot
of
different
projects,
I
think
within
CNCs,
so
not
just
the
one
lsit
but
within
san
CF.
That
could
use
something,
possibly
that
does
ansible
and
they're
already
interested
in
using
other
playbooks
to
manage
the
infrastructure,
whether
it's
C
ICD,
whatever
they're
I,
don't
have
a
specific
ones
that
I
could
point
out.
E
E
A
Could
we
have
the
link
for
this?
We
can
share
some
information
on
how
the
cross
cloud
siak
project
does
deployments
and
I'm
provisioning
everything
for
kubernetes,
and
that
way
you
could
take
a
look
at
that
and
think
about
comparison
again.
I,
don't
really
think
it's
going
to
be
a
replacement
leasing,
complimentary
for
different
purposes.
E
Yeah
and
for
a
network
service
smash
like
if
I
can
see
what
that
is,
and
that's
that'll
give
me
a
good
overview
is
to
like
which
direction
I
should
head
off
into
in
order
to
to.
In
order
to
make
this
happen,
it's
not
referred
to.
I
prefer
to
work
in
with
what's
communities
doing
rather
than
like
I
can
I
can
roll
my
own
wrote
without
too
many
issues,
but
if
the
community
already
Sardi
adopting
something
for
this
role,
then
there's
no
reason
to
deviate.
A
A
So
I
think
you
went
over
a
couple
of
related
ones.
The
Oracle
staff
Oracle
being
is
in
progress
and
I,
don't
know
if
we
mentioned
last
time,
but
the
Ammar
vsphere
anyway.
So
let
me
go
back.
Where
were
we
I
see
your
window
now
so
the
VMware
integration?
That's
done.
We've
had
a
lot
of
poor
requests
and
updates
trying
to
fine-tune
some
of
the
differences
there.
A
Those
were
talked
about
earlier
and
keeping
up
with
updates
on
all
the
different
projects,
including
some
changes
that
require
internal
changes,
to
make
it
a
little
bit
more
general-purpose
to
handle
updates
between
versions
of
kubernetes
or
whatever
else,
Denver
just
fixed
and
I'm,
on
an
IBM
cloud
with
addy
provisioning,
where
they've
had
some
upstream
changes
that
required
a
changes
on
our
end
handling,
how
we
do
terraform
templates
and
how
the
resources
were
managed.
So
that
fix
that
issue
since.
C
A
C
F
F
A
To
expose
more
of
this
so
happy
for
you
to
raise
an
issue
and
yeah:
that's
all
something
of
it,
especially
if
you
have
specific
details
on
it,
so
we're
trying
to
differentiate
those
and
then
and
make
the
underlying
issue
more
visible,
so
that
we
don't
have
that
top
saying.
That's
not
the
real
problem.
Gotcha.
A
Can
go
on
we've
been
attending
a
lot
of
the
different
groups,
trying
to
figure
out
how
we
can
collaborate
related
to
what
Fredrik
was
talking
about
as
far
as
reusing
tools
and
trying
to
work
directly
with
the
different
teams,
so
cluster
API
breakout
and
the
cluster
lifecycle
group,
the
NSM
with
you
Frederick
and
looking
at
how
we
can
extend
or
reuse
different
components.
A
So
doing
a
lot
of
that
and
Watson
has
been
working
a
lot
on
my
mapping
and
figuring
out
what
all
the
different
groups
are
needing,
so
we'll
be
providing
more
details
on
stuff
like
that
in
our
kind
of
roadmap
and
planning,
and
what
we're
seeing
between
the
different
teams
will
be
upcoming,
so
slide
14.
Here's
some
initial
thoughts
on
what
we're
saying.
A
Before
we
get
into
maybe
more
more
items
that
could
be
project
specific,
so
we're
looking
at
splitting
the
screens
out
and
having
the
project
a
project
overview
screen
and
the
dashboard
we've
talked
about
that
for
a
while.
That
still
seems
like
a
valuable
thing
so
that
we
have
a
difference
between
the
kubernetes
deployment
and
how
that's
provisioned
and
how
the
projects
and
then
test
and
sauna
boy
be
working
to
update
and
replace
what
we
had
originally
set
up
with
cube
test
and
then
I'm,
adding
cube,
ATM
and
potentially
ignition
support.
A
Andrew
had
brought
that
up
as
far
as
what's
supported
and
caresse.
So
that's
something
that
we'll
be
examining
further,
whether
it's
going
to
be
running
side
by
side
or
if
we
can
replace
or
what
we
want
to
do
there
harbour
is
something
we're
looking
at
to
make
us
not
as
dependent
on
yet
lab.
So
we
have
different
components
and
at
a
minimum,
if
we
have
a
layer,
so
we
could
say
we
can
use
images
and
artifacts
that
are
somewhere
outside
of
get
lab.
Then
that
would
be
nice.
A
A
A
Automating,
the
project
release
updates
a
lot
of
that
tied
in
with
the
fact
that
we're
running
at
3m.
So
if
automation
happens,
how
soon
do
we
find
problems
and
going
for
the
environment?
So
there's
some
issues
there,
but
I
think
that's
desired,
so
they
they
come
up
a
little
bit
sooner.
That
could
be
tied
in
with
and
we
do
support
uncommit
runs
and
we
may
decide
to
do
some
things
with
flags
from
different
projects.
A
That's
been
desired
to
turn
on
when
to
do
full
runs
of
the
CI
test,
so
anything
along
the
automating,
those
new
updates
from
the
absurd
projects
and
then
the
API
I
think
there's
still
a
big
desire
that
we've
been
hearing
to
have
access
to
all
the
data,
so
historical
builds
where
artifacts
are
come
from.
So
did
we
pull
these
down
from
upstream?
A
This
ties
into
something
folks
have
talked
about
quite
a
bit,
so
if
we
have
a
failed
deployment
or
build,
maybe
it
the
end-to-end
tests
are
not
they're
failing,
so
we
want
to
actually
show
on
the
dashboard
and
in
the
API.
Here
was
the
last
release
that
that
built
or
deployed
successfully,
and
they
in
dentists
were
successful
for
so
providing
that
sort
of
details,
I
think,
is
important.
That
will
help
with
false
positives,
so
we're
not
showing
red
on
the
dashboard.
A
If,
if
we
have
this,
we
can
say
here
was
the
last
one
that
worked
and
the
current
one
failed,
but
you
can
see
the
last
one
they
could
use
now.
I
talked
about
the
new
screens
on
the
slide
16,
some
of
the
groups
that
were
attending
and
events
that
were
going
to
be
a
part
of
if
anyone's
interested.
Then
please
join
if
you're
in
Austin
a
fun
thing
that
started
or
there's
a
lot
of
good
conversation
that
open-source
axis
and
I
think
that's.
It.
A
C
C
Well,
thank
you
thanks
for
that
Taylor
and
appreciate
that
the
slides
and
I'll
try
to
be
better
about
not
interjecting
in
the
middle
there,
I
guess
it's
just
I'm
used
to
that
all
all
filed
file
those
issues.
Yes,
thanks
I
reached
out
to
listen.
You
know
a
while
back
with
some
questions
for
the
team
at
bulk
regarding
the
cross
dashboard,
and
she
suggests
that
this
would
be
a
good
venue
for
it,
so
other
people
could
benefit
from
the
conversation.
C
Essentially
VMware
is
getting
more
injury
were
involved
in
kubernetes
into
investing
as
well.
You
know,
that's
the
test
end
for
project
proud
and
test
great
and
whatnot,
and
one
of
the
things
that
you
know
I
I
raised
a
topic.
I
raced
with
my
colleagues
is
hey.
You
know,
Volk
had
to
deal
with
getting
involved
in
kubernetes
and
endure
conformance
testing,
not
in
the
exact
same
way,
but
it
conformers
testing.
C
What
were
the
goals
of
the
dashboard
and
I
think
we
reached
out
to
me
on
slack
and
asked
me
to
clarify
a
use
cases,
and
so
what
I
meant
by
use
cases
was
or
as
the
day
come
to
you
and
say
this
is
exactly
what
we
want
or
they
come
to
you
and
say
we
need
to
provide
us.
You
need
to
provide
a
solution
that
there
are
these
three
use
cases
we
want
to
solve,
and
this
was
your
solution
for
that
it.
C
Additionally,
if
you
could
have
done
it
all
over
again,
how
would
you
approach
it?
You
know
what
feedback
did
the
CNCs
provide
in
that
process?
And,
finally,
you
know
what
are
the
plans
that
you
could
possibly
expand
the
dashboard
to
cover
and
in
testing
and
I
say
that
having
just
exited
a
conversation
instead
testing
where
you
know
they
into
in
testing
at
least
a
subset
of
that
our
conformance
tests
and
I,
would
you
know
I
think
you
would
say
this
as
well
that
the
dashboard
is
in
a
lot
of
ways?
It's
conformance
testing
I.
C
Think
you've
called
it
that
so
is
there
an
opportunity
for
the
dashboard
to
contribute
back
to
the
test
grid
and,
if
so,
I
mean
have
you
considered
that
I
just
I'm
trying
to
want
learn
from
your
process,
learn
from
any
mistakes
you
made
or
what
you
do
different
and
also
not
try
to
duplicate
any
future
work
that
you
could
share
in
VMware
zone.
Efforts
to
you
know
expand
into
the
the
kubernetes
testing,
so
hopefully
that
was
all
clear
as
mud.
A
Thanks
for
that,
intro
it,
you
provided
a
little
bit
more
info
for
myself,
as
also
thanks.
I
think
we
kind
of
go
through
this
and
we've
laid
out
most
of
kind
of
responses,
but
I
think
there's
probably
some
conversations
or
in
this
based
on
what
you're
just
saying-
and
it
looks
like
we
have
quite
a
few
folks
on
the
call
that
could
respond
to
maybe
some
additional
pieces.
C
Yep
about
the
goals
and
use
cases,
I
mean
that
was
more
for
hey
I'm,
managing
a
similar
project
at
the
moment,
I'm
just
being
selfish,
you're,
very
smart
people
who
did
this
and
figured
it
out
and
I
want
you
to
do
my
I
want
to
learn.
You
know
what
things
that
you
encountered
and
you
know
how
you
responded
to
them,
I'm
being
selfish
and
hopefully,
that
myself
and
again
others
getting
involved
in
kubernetes
testing
can
learn
from
you.
Your
experience.
A
A
F
F
C
In
let
me
go,
let
me
quickly
say
like
it's:
it's
been
difficult
to
get
as
much
conversation
out
of
testing
with
some
respects
to
because
there
haven't
been
as
a
lot
of
people
as
many
people
that
have
implemented
things
that
work
with
prow
externally,
so
because
ya
kind
of
did
a
similar
thing
with
multiple
platforms.
I'm.
Looking
for
up
examples
of
how
you
went
about
organizing
to
do
a
similar.
F
F
Just
quickly
speak
to
the
choices
that
we
made
and
trying
to
look
at
what
was
in
the
community
cig
testing
didn't.
It
was
only
one
cloud
at
the
time
and
we
were
looking
to
find
something
more
generic.
There
were
not
a
lot
of
tools
out
there
that
did
multiple
providers.
Well,
there
was
everybody
was
there
was
that
there
was
a
very
busy
field,
everybody's
trying
to
do
the
same
thing,
and
so
we
did
make
some
some
early
choices
to
try
to
generalize
things
to
make
sure
it
wasn't
specific
to
a
provider.
F
One
of
those
things
was
trying
to
find
an
API
to
all
of
the
clouds.
We
did
go
with
terraform
on
that
and
also
trying
to
find
an
OS
Cygnus
t'k
approach
that
didn't
require
that
it
was
well-suited
to
CI.
So
we,
instead
of
trying
to
SSH
or
use
any
any
after
the
boxes,
up
provisioning
tools.
We
decided
to
go
with
cloud
in
it
and
then
using
the
very
simple
put
some
files
here
and
when
you
know,
system,
D
and
stuff
starts
up
begin.
That
was
some
of
the
more
advanced
stuff.
F
Those
design
decisions
have
have
stuck
pretty
well.
One
of
the
things
that
we
also
looked
for
with
some
type
of
CI
platform
that
was
put
together
enough
for
we
didn't
have
to
do
all
the
glue
at
once.
So
we
made
some
early
decisions
to
go
ahead
and
use
yet
lab
for
that.
I
really
liked
the
approach
of
being
able
to
use
something
open-source
and
drop
in
a
single
file
to
get
us
started
and
and
I
think
that
pretty
much
covers
the
design
decisions.
F
Then,
and
as
we
worked
more
and
more
with
tests,
infra
trying
to
find
ways
to
reuse
that
that
approach
and
it's
there's
you've
been
involved
in
the
conversations
on
in
several
places
where
it
seems
particularly
for
CI
and
within
tests
infra,
that
the
flow
is
focusing
on
it
was
kubernetes
anywhere
for
a
while
and
now
that
we're
seeing
API
cluster
API
is
beginning
to
come
to
fruition.
It
looks
like
cluster
API
run
by
cube
tests
run
by
Edie.
C
F
C
F
So
no
okay,
well
it's
it's
I,
I!
Think
I'll!
Let
vocht
speak
to
that.
The
the
specifics
of
it
but
I
I
I,
don't
think
it's
a
it'll,
be
an
undertaking!
Mind
you
but
I,
don't
I!
Think
the
value
that
we
get
out
of
it
would
be
I'd,
be
tremendous
that
benefit
the
whole
community
to
clear
all
the
providers.
We
already
have
running
sorry
that
you
had
to
do
the
heart
and
the
heavy
lifting
for
the
first
foray
in
the
cluster
API.
A
F
A
A
A
It
was
always
something
moist
hindsight
you
would
have
done
differently
and
made
it
more
useful,
let's
hop
to
slide
20
real
quick,
so
this
is
just
a
quick
overview,
the
goals
so
tied
in
with
why
we
were
here
and
at
a
higher
level
what
HH
was
just
talking
about
and
the
CI
platform,
so
that's
tied
in
with
the
building
building
that
initial
platform
out
and
what
it
could
do,
and
the
different
pieces
within
that
for
provisioning
kubernetes
using
terraform
and
cloud
in
it
to
be
able
to
handle
a
larger
set
that
at
the
time
cube,
ATM
was
not
really
in
a
place
where
it
was
going
to
solve
the
needs
for
a
che
clusters
and
and
handling
bringing
up
all
of
these
nodes
with
with
various
needs.
A
So
those
were
kind
of
the
reasons
why
that
was
chose
at
first
and
that's
done
and
then
a
Status
repository
for
storing
all
that
information
which
would
be
used
by
the
dashboard.
So
how
to
display
this,
so
that
was
one
of
the
biggest
main
goals
was
whatever
CI
system
underneath
we
need
to
be
able
to
have
a
high
level
dashboard.
So
that's
what
we
have
now
it
had
happened
to
have
many
statuses
that
maybe
we
can
get
to
in
the
past.
Well
what
we
would
have
done
differently.
A
A
None
we're
doing
all
of
so
sure
that
one
was
a
solid
use
case
to
get
going
at
the
time
and
and
then
from
the
site
of
like
an
end-user
there's
a
lot
of
folks
that
were
afraid
of
vendor
lock-in
and
okay.
Kubernetes
can
solve
this,
but
how?
How
does
it?
How
does
it
actually
work?
So
this
is
kind
of
a
the
idea
of
more
than
a
demo.
Something
that's
live
and
running
and
doing
testing
from
an
end-user
perspective.
A
That
goal
is
something
that's
there
that
use
case.
I
should
say
it's
a
harder
one
to
reach
that's
kind
of
a
reference
architecture,
type
thing,
and
it's
better
to
have
scenarios.
That's
something
that
that
we've
kept
in
mind,
though,
is
we're
building
that
out,
and
then
they
build
all
the
status
et,
build
everything
else.
So
a
use
case.
How
do
we
look
from
that
high-level
status.
F
C
Yeah
I
feel
glad
that
you
went
through
all
this
effort
to
lay
all
this
out
for
those
questions.
At
the
same
time
you
know
I,
it
makes
me
feel
worse
that
you,
just
your
team,
isn't
somehow
involved
in
the
leadership
of
the
cluster
API,
because
everything
you
described
so
far
is
just
like
the
perfect
plan
for
the
Questor
api
and
its
goal
or
its
goals
in
my
mind,
should
be,
and
then
you
already
have
a
solution.
It's
anyway,
yeah.
A
Well,
we're
actively
working
with
them
and
HHS
working
also
on
a
on
a
project.
That's
related
to
it's
kind
of
it's
it's
a
tool
that
helps
the
I
I,
don't
know
if
you've
looked
at
the
API
snoo
project,
but
it's
all
of
these
are
kind
of
related
to.
How
do
we
help
these
groups
so
in
a
lot
of
ways
this,
in
addition
to
providing
some
of
the
goals
that
we
had
with
the
dashboard?
A
It's
it's
trying
to
give
miss,
fill
some
of
those
missing
gaps
between
all
the
projects
where
things
overlap,
but
they
don't
quite
meet
and
then
we
are
participating
in
a
lot
of
the
the
group
calls
and
everything
and
saying
how
do
we
survive
feedback?
Some
of
these
things
were
way
ahead,
so
cube,
ATM
wasn't
ready
to
be
used
so
now
there's
it's
kind
of
at
a
stage
where
we
can
start
collaborating
test
grid
and
whip
up.
The
API
coverage
from
API
state
may
not
have
been
the
right
time
early.
A
It's
now
at
the
right
time,
where
they're
trying
to
meet
a
goal
with
conformance
the
conformance
group.
Now
they
have
more
providers
that
are
interested.
So
it's
kind
of
coming
together,
but
I
appreciate
your
comments
on
that.
So,
let's,
let's
move
on
to
what
you're
saying
might
be
exciting
here.
So
what
would
we
do
differently
so
broke
some
of
these
out
and
Denver
I.
Don't
know
if
you
had
good
audio
if
you
have
some
lots
or
anyone
else
that
wants
to
speak
up,
feel
free,
so
modifying
how
we're
building
and
using
the
artifacts.
A
The
one
of
the
things
that
was
desired
and
we
didn't
really
get
to
get
to
until
say
own
app
was
using
the
external
artifacts
and
really
thinking
about
those
and
reusing
and
saving
them.
That's
something
that
you
would
want
to
do
once
it
validated
if
a
project
already
has
artifacts
and
they're
producing
them
in
a
way
that
they're
easily
accessible
and
we
can
validate.
A
Maybe
the
FCI
tests
that
we
don't
need
to
run
them
then
using
some
of
those
there's,
there's
a
bit
of
complexity
around
determining,
and
is
this
something
for
each
project,
if
there's
not
a
format,
but
that's
something
that
we're
moving
towards
and
I
think
that
would
be
there'd,
be
some
more
that
we'd
put
in
place
and
that
would
have
more
collaboration
with
the
community
early
on
and
reusing
the
verified
artifacts.
So,
besides
that
the
showing
them,
maybe
the
API,
so
I'll
move
on
how
to
on
the
provisioning
side
of
queue
brunetti.
A
So
this
ties
in
we
talked
about
cube
ATM
a
bit
so
terraform
with
packer
to
create
pre-baked
images.
So
this
would
be
beneficial
in
a
lot
of
ways.
It
would
speed
up
the
deployments
of
kubernetes
if
we've
already
validated
run
conformance
tests
and
everything,
and
we
have
images
for
all
the
cloud
providers.
We
can
spend
those
up
when
we're
running
additional
tests
for
say
the
apps
or
whatever
parts
that
we
need.
So
this
is
about
using
those
validated
or
hide
artifacts.
Those
could
also
be
made
available
to
the
community
and
we
say:
hey.
A
C
This
is
the
part
that
interested
me
most,
because
this
is
the
piece
of
the
project
in
which
I'm
currently
working
are
the
terraform
stuff
on
which
I'm
currently
working
I'm.
Just
to
the
point
of
laying
down
kubernetes
and
to
see
you
say
that
you
would
use
cube
ATM
at
this
point,
it
is
very
interesting
to
me
it
doesn't.
It
doesn't
totally
a
divorce
you
from
something
like
clogging
it
or
ignition,
because
there's
usually
that
to
configure
the
actual
guest
OS
outside
of
kubernetes.
A
I
think
this
is
still
in
the
investigating
stage
for
our
what
I
should
say
what
the
scene
CSCI
dashboard
is
doing
like.
Is
it
ready?
Do
we
have
the
different
pieces?
Maybe
it
is,
you
know
called
by
cloud
in
it,
but
we're
not
actually
laying
down
the
manifests.
We
get
it
going
or
maybe
there's
some
preliminary
stuff.
So
there's
some
stuff
to
look
at
right.
There
I
think
what
we
have
right
now.
If
it's
useful
then
use
that
it's
it's
still
valid
and
hopefully
whatever
you
have,
it
would
be
compatible.
A
If
we
move
over
and
you'd
say
here's
how
to
migrate
towards
that,
it's
definitely
not
something
you're
going
to
see
real
soon
and
the
rest
of
the
pieces.
We're
going
to
try
to
make
I,
don't
want
to
say
backwards,
compatible,
but
a
migration
path.
So,
let's
go
on
the
slide.
23
just
got
a
couple
minutes
the
gait
lab
implementation.
A
So
we
had.
This
is
something
talking
about
earlier.
We
use
get
lab
as
the
main
CI
platform.
We'd.
Probably
look
at
trying
to
keep
something
separate
and
not
have
it
so
dependent
on
the
gait
lab
space
it
pieces
from
the
start.
There's
definitely
some
parts
where
it
could
have
been
separated
a
little
bit
more.
Even
if
we
didn't
say
it
was
completely
independent,
it's
definitely
good
to
get
started
and
there's
some
really
useful
information.
But
maybe
a
specific
thing,
though,
would
be
these
web
hooks.
So
they're
API
is
not
really
reliable.
A
You
can
return
different
information
from
what
you
see
in
the
database
or
the
web
UI.
So
there's
also
some
benefits
from
using
the
web
hooks
for
the
events,
but
having
more
of
that
knowledge
ahead
of
time,
which
is
hard
to
know.
But
if
you
know,
if
we
had
it,
then
that
would
have
been
something
to
do
once.
We've
really
got
to
know,
get
lab
the
status
repository.
A
A
Nice
would
have
affected
some
of
the
collaboration
metadata
and
everything
else
potentially
allow
other
folks
to
add
here's
an
integration
to
our
CI
system
and
we're
using
the
this
community
format
that
we
all
agree
to
some
of
that's
happening
in
open,
CI
and
Watson's,
been
working
on
white
papers
and
stuff
and
collaborating
so
I
think
we'll
see
that
that
would
be
an
early
thing,
so
yep
and
test
grid
and
all
the
different
systems
weren't
interested
in
so
let's
say,
directions,
feedback,
we're
kind
of
at
the
hour.
You
can.