►
From YouTube: CNCF CI Working Group Meeting - 2018-01-09
Description
Join us for KubeCon + CloudNativeCon in Barcelona May 20 - 23, Shanghai June 24 - 26, and San Diego November 18 - 21! Learn more at https://kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy and all of the other CNCF-hosted projects.
A
A
A
D
B
B
Cool
so
a
lot
happening
through
from
Esther,
tubecon
and
I
know
at
least
some
of
y'all
were
there
and
what
we've
been
doing
pushing
forward
from
there.
B
Let's
see
and
we
a
lot
of
what
we're
doing
this
past
year
was
getting
the
first
version
and
as
the
CI
system
and
the
dashboard
out,
the
CI
systems
actually
on
a
release
to
and
the
dashboard
is
we'll
be
releasing
a
public
release
of
b1o
this
january
and
we
had
been
gathering
lots
of
feedback
and
making
adjustments
as
we're
going
along
from
epic
Yukon
and
pass
their
goals
for
January
are
to
release
v1l
of
the
dashboard.
So
this
is
the
overall
frostbite
CI
and.
B
This
we
now
have
across
pod
CI
project.
So
a
lot
of
these
were
repos
split
out
under
scenes.
Yet,
and
we've
now
set
things
that
were
like
other
projects
like
the
kubernetes
prometheus
everything
else.
So
the
different
repos,
including
the
dashboard
back
in
or
out
here,
front
end
the
different
configuration
for
how
these
work
within
the
CI
system
on
for
the
various
projects
in
CF
project.
So
that's
out
there.
B
The
CI
system
itself
is
we're
getting
ready
for
another
release,
and
this
is
where
we've
split
out
everything
for
the
build
system,
provisioning
and
app
deployment,
the
different
parts
and
trying
to
make
it
configurable-
and
this
will
tie
in
with
something
we're
doing
listed
here
as
well.
We're
trying
to
target
an
app
as
one
of
the
main
projects
integrations
for
the
cross
pod
system
and
that's
going
to
be
using
their
builds
so,
rather
than
using,
builds
within
the
cross.
B
Lab
we'll
be
pulling
artifacts
from
the
own
app
build
system
and
then
we'll
continue
with
provisioning
kubernetes
on
the
different
clouds
as
we're
doing
and
then
we'll
be
deploying
using
the
helm,
charts
and
everything
else
that
own
app
has
with
some
adjustments.
Working
with
them
be
able
to
have
deployments.
So
we've
been
building
the
system
out
to
support
this
for
each
one
of
the
parts
to
be
independent,
so
the
integrations
can
work
with
other
systems
and
we're
excited
to
be
working
with
own
app.
This
month
we
started
on
those
conversations
last
year.
B
B
B
This
is
part
of
the
goals
that
we
were
set
earlier
in
the
air,
and
this
is
one
of
the
last
items
here
once
we've
split
everything
off
into
those
build
provision
and
app
deployed
and
having
these
run
scheduled
and
being
able
to
use
the
internal
CI
system
API
for
doing
that,
so
we
will
be
continuing
those
items
we've
taken
in
some
feedback
on
various
things,
updating
security
and
the
different
timeouts,
because
the
system
now
is
composed
of
many
different
parts.
So
there
could
be
timeouts
and
integration
looking
at
stuff
like
working
with
own
app.
B
What
what
could
we
see
there
and
what
would
we
want
to
catch
as
far
as
exceptions
and
the
retries
incest?
So
these
are
some
of
the
parts
that
we
pulled
in
in
the
last
few
months
of
the
project,
getting
ready
for
v1.
Now
we're
also
doing
a
pretty
extensive
integration
test,
I'm
trying
to
have
as
as
many
as
possible
in
as
part
of
v1.
Oh
and
that's
in
the
works,
it's
I
guess
several
parts
on
the
system.
B
We
have
the
API
and
then
we
have
the
that
front-end
bjs
app,
which
is
the
the
main
and
viewing
part
for
everyone,
and
that's
we're
trying
to
test
that
as
well.
For
the
indian
test,
let's
see
what's
next
and
so
edy,
we
have
a
meeting
two
that
we're
planning
with
you
as
your
works
and
last
last
year
we
kind
of
bug
the
court
so
planning
on
doing
that.
We're
going
to
be
doing
a
status
update
with
the
mill
later
in
the
month
and
getting
her
feedback
for
current
progress.
B
The
v1
ever
had
mentioned
before
coming
along
with
that
we'll
be
updating
the
readme
for
the
various
readme
in
facts
for
the
various
parts.
A
lot
of
feedback
from
cube
con
that
we're
rolling
in
here
updating
to
readme
for
the
CI
system
be
able
to
show
how
to
get
the
different
parts
going
and
use
those
independently
updating
how
to
get
the
dashboard
and
everything
I've
been
going.
What
needs
to
be
configured
if
someone
was
going
to
add
different
projects
as
well
as
help
allowing
the
various
projects
start
working
directly
with
us
and
during
q
con?
B
We
talked
a
lot
with
Cordain
ass
folks,
and
so
we're
going
to
be
to
have
help
on
into
n
tests
and
involve
an
app.
How
do
we
do
integrations
on
the
CI
system?
So
there
will
be
a
lot
of
documentation
updates
and
hopefully
that
get
more
direct
community
involvement
with
with
the
integrations
and
adding
new
projects.
B
B
C
Yes,
your
ideas
working-
this
is
Edie
from
Hackett,
just
in
terms
of
scheduling
and
planning.
I
know
that
the
some
of
the
work
that
I'm
interested
in
is
dependent
on
a
version
2.0
starting
do
you
have
sort
of
a
timeline
for
when
you
expect
major
releases
and
and
when
things
are
either
hoped
for
or
planned?
It's
not
not
trying
to
hold
you
to
something
I'm,
just
trying
to
get
a
sense
for
my
timeline
for
putting
resources
together.
B
And
so
to
O
of
the
CI
system
as
far
as
the
cloud
deployment,
so
this
would
be
about
a
packet
and
in
general,
as
well
as
the
arms
for
packets,
I.
Think
that
we're
referring
to
that's
else
so,
oh
release
of
CI
system
actually
happened
before
Q
Khan
and
so
that's
ready
to
go.
We
are
I,
guess,
ready
to
start
looking
at
how
to
target
arms
as
far
as
an
uber,
Nettie's
and
then
I
a
separate
topic
would
be
deploying
the
projects
themselves.
That
would
kind
of
be
a
post
not
to
a
thing.
C
C
B
C
B
B
Awesome
so
anyone
else
have
comments
or
questions.
D
B
D
So
I'll
send
you
an
email,
just
like
a
quick
update
or
I
can
send
it.
You
know,
I,
don't
know
if
there's
a
different,
try
send
it
to
a
different
address
or
anything
like
that.
But
I
can
send
you
one
directly
and
then
we
can,
you
know,
go
from
there
to
see
if
it
makes
sense
for
us
to
discuss
further
before
before
the
if
anybody's
going
to
that
event,
if
it
happens.