►
From YouTube: CNCF CI Working Group Meeting - 2018-04-10
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
Okay,
now
this
is
a
scene
CF
CI
working
group
on
Tuesday
April,
10th
I've
shared
my
screen
and
also
shared
the
links
to
today's
CI
working
group
meeting
agenda
notes
and
the
slides
that
we're
using
today
feel
free
to
add
your
name
and
email
address,
contact,
information
to
notes
and
agenda.
Also,
if
you
have
any
updates
that
you
would
like
to
add
to
the
slide,
feel
free
to
do
so.
A
B
We've
had
a
few
releases
and
March
covering
quite
a
few
items,
including
adding
some
new
clouds,
as
well
as
projects
and
attended
ons
cloud
provider.
Wise
we
OpenStack
is
now
production
on
CN,
CF
CI
and
we
have
fluent
D
as
well
and
we
attended
OH&S
and
there
was
a
face-to-face
CI
CD
workshop
during
that
time,
go
on
to
the
slide
five
I
guess
and
we
can
hop
into
those
releases.
B
So
one
of
the
big
items
that
happen
during
March
was
adding
a
a
non
CN
CF
project,
the
Linux
Foundation
project
own
app
and
specifically
their
service
orchestrator,
and
that
added
a
external
integration
to
the
own
app
CI
system.
They
run
their
own
Jenkins
tied
him
for
the
CI.
They
built
their
own
containers
and
they
publish
those
in
a
registry
that
Linux
Foundation
provides,
and
we
did
the
integration
with
that
where
we
pull
in
those
artifacts
validate
that
they
work
and
then
use
them
during
the
app
deployment
phase.
B
We
also
use
their
integration
test
and
run
those
at
the
end
to
validate
the
service
organization,
all
the
pieces
that
were
running
at
that
time.
So
that
was
pretty
great
achievement.
We've
also
been
working
with
them
as
they're,
getting
ready
for
a
release
and
a
new
release
on
the
own
app
side.
Beijing
they've
had
a
few
items
that
were
changing
and
we've
done
simple
request
or
open
tickets
and
helped
them
with
those.
B
So
OpenStack,
as
I
had
mentioned,
was
another
big
one.
Chris
Hodge
did
the
large
majority
of
the
work
and
then
Melvin
also
helped
on
the
second.
We
kind
of
had
a
second
revision
of
the
OpenStack
side
as
we
moved
it
through
F
after
it
was
ready
for
us
and
we're
trying
to
integrate
and
do
some
testing.
B
It
went
back
and
we
worked
with
him
to
make
some
updates
and
Melvin
was
a
big
help
on
that
side
as
well,
and
so
that
was
a
contributed
cloud
provider
which
was
really
awesome,
great
coverage
and
it's
been
really
good
to
have
their
feedback
on
that
process.
I
think
we'll
be
using
that
as
we
were
working
with
some
other
folks
in
the
future.
B
B
B
There
is
some
deprecated
items
that
we've
now
covered
and
we're
going
through
and
updating
a
few
things
for
the
end,
end
tests
and
some
other
items
in
provisioning
and
then
that'll
be
ready
to
go
as
far
as
the
terraform
code
and
then
we're
good
to
go
and
110
will
be
up
on
the
dashboard
and,
as
I
mentioned
before
the
own
app
on
the
head
release,
they
they
made
a
change
upstream.
Things
were
breaking,
they
fix
their
build
now
and
we're
going
to
be
updating
our
integration
code
to
work
with
those
changes.
B
B
What's
next
and
we'll
be
we're
working
on
adding
Oracle
support
in
that
process
and
then
we'll
be
looking
at
Huawei
and
Alibaba
as
far
as
clouds
and
arm
support
still
in
the
in
the
queue
at
some
point
in
the
future.
After
these
clouds
we're
also
looking
at
envoi
and
Jager,
and
a
few
of
the
other
projects
as
far
as
the
next
and
boy
is
going
to
be
added
as
the
next
project,
though,
on
the
cross
cloud
CI
project
itself,
this
internal
software,
we
are
in
progress
on
automating
the
project
release
updates.
B
This
will
allow
us
to
be
tying
in
with
history
and
the
API
itself,
and
that's
going
to
allow
us
to
do
a
lot
of
other
things
in
the
API
server,
for
the
status
repository,
including
new
screens,
being
able
to
roll
back
to
previous
release,
tooltips
and
other
items
in
the
dashboard
for
different
versions
and
what
worked
and
what
didn't
work
and
then
providing
direct
access
to
the
API.
For
folks
to
query
and
look
at
stuff
like
Prometheus
196,
with
a
specific
version
of
of
kubernetes
and
other
items
like
that.
B
So,
what's
where
are
we
doing?
As
far
as
community
goes
the
open
CI,
which
I
mentioned
that
came
out
of
that
face-to-face
before
ons?
There's
a
white,
a
white
paper,
that's
being
collaboratively
built
and
HH
Rowan
Rowan
are
also
contributing
to
that:
hey
guys
and
some
other
quite
a
few
other
folks.
So
that
was
really
cool
and
we
are
actually
working
on
RFC
for
a
pipeline
messaging
protocol
and
we've
provided
a
link
there.
B
So
that's
continue
that
collaboration
so
that
they
can
start
maintaining
those
and
helping
both
within
their
project
and
cross
Claude
CI,
and
that's
about
it
for
us
upcoming,
Vince
Morse,
to
see
it
next
CI
working
group,
April
24th,
will
be
a
cube
con
Copenhagen,
May,
2nd
to
4th
providing
an
intro
and
deep
dive
on
the
cross.
Godsey
I
be
talking
more
about
how
to
add
cloud
providers
and
how
to
add
new
projects.
B
A
C
C
C
And
so
one
thing
we
were
when
we
first
as
a
list
of
things
were
wanting
to
solve
one
is
that
kubernetes
test
coverage
is
currently
calculated
using
our
end-to-end
logs,
so
we
have
to
run
the
edy
test
and
then
look
at
the
output
in
order
to
calculate
looks
there
that
only
works
for
the
PDE
test
and
doesn't
use
other
application.
Their
philosophy
is
for
application.
C
Then
we'd
like
to
figure
out
a
way
to
cover
API
for
not
just
the
end
intention
at
any
application
using
the
kubernetes
api
and
in
addition
to
that
conformance
group,
they
wanted
to
get
their
ete
test
percentage,
raise
it's
sitting
at
11%
right
now.
They
need
to
be
able
to
prioritize
which
tests
that
are
right.
Next,
in
addition,
there's
a
add
ons
for
a
non
conformance.
We
don't
know
which
particular
API
is
they're
using
and
if
add-ons
are
written,
a
different
language
that
they're
not
using
the
go
on
client
library.
C
C
C
Euro
we'd,
like
that
available,
not
just
to
Korea's
and
then
tests,
but
any
other
application,
we're
gonna,
look
at
the
inspect
the
actual
calls
on
the
wire
rather
than
looking
at
the
logs,
and
this
will
allow
us
to
do
it
from
any
add-on
or
the
Indian
test
inspecting
each
of
those.
They
should
do
your
request
against
the
opening.
C
In
an
implementation
news
field,
you
know
we
want
to
be
able
to
patient,
we
will
use
outside
of
kubernetes.
So
a
couple
of
steps
for
that
is
redirecting
the
ATA
request
to
the
proxy.
So
we're
gonna
do
that
by
watching
for
pods
coming
up
with
annotations
and
then
redirecting
to
the
proxy
using
IP
tables.
A
C
D
D
Sure,
okay,
so
hi,
my
name
is
Rowan
I'm,
just
going
to
walk
you
for
a
brief
demo
of
our
peripheral
concept,
so
I
guess.
The
first
thing
is
that
we've
just
got
a
kubernetes
cluster,
which
is
ready,
9
gke,
a
couple
of
notes
about
it
as
that
at
the
moment
it
requires
the
Alpha
features,
enabled
and
also
requires
legacy
authorization
enabled
which
basically
disables
our
Beck.
D
D
D
D
We
can
pretend
to
be
the
API
server
with
the
creek
like
with
suits,
which
are
signed
by
the
CA,
so
coop
cuddle
doesn't
care,
other
things
won't
care
as
well,
there's
no
difference,
and
so
what
we'll
do
and
set
up
in
my
tea
and
proxies
we'll
just
do
a
ham
install
in
enabling
initializes,
then
we're
going
to
deploy,
like
example,
app,
which
is
basically
just
like
a
pod
which
has
coop
cuddle.
That
makes
calls
to
coop
cuddle
get
pods
every
five
seconds.
D
At
the
moment,
we
have
a
little
bit
of
magic
that
we're
sort
of
using
to
determine
which
which
T
proxy
is
on.
The
same
note,
as
the
is
the
example
that,
because
we're
just
doing
like
a
port
for
instead
of
hearing
like
a
service
that
will
change
later,
and
then
we
just
once
with
port
for
two,
we
can
open
up
a
browser
to
their
port
and
we
can
get
the
MIT
M
web
interface,
which
is
part
of
your
my
TM
proxy.
B
B
D
D
D
It
is
approving
a
getting
the
result
insert
here
we
go.
We
can
see
that
this
is
being
signed
by
the
CA.
These
are
the
endpoint
addresses
for
kubernetes,
so
now
that
we've
got
that
all
ready
to
go
second
thing,
as
I'm
just
shows
sit
up
in
my
team
proxy.
So
currently
it
requires
so
it's
to
be
built
for
my
TM
proxy,
as
if
it's
going
to
run
its
own
CA
and
that's
just
I,
think
a
dependency
or
the
way
that
things
were
done
before.
D
D
Okay,
so
now,
let's
ping
deployed,
we
can
do
a
coupe
cuddle
get
hogs.
You
can
see
that
here
are
our
T
proxies
running.
There's
one
T
proxy
running
per
node
I
can
go
to
cuddle
nodes.
This
is
a
free
mail,
cluster
free
site,
so
one
to
copy
for
each
no
and
I'm
just
going
to
go
back
to
here,
because
I've
got
oh
yeah,
that's
right,
so
goo
cuddle.
So
next
step
is
basically
to
deploy
our
example
app.
D
D
D
D
D
Okay,
all
right
Chris
do
you.
Wanna,
looks.
D
C
The
only
one
which
side
press
gets
the
yeah
what's
next,
thanks
for
pulling
up
really.
B
E
Folks,
this
is
some
Dan
Kahn
I
just
have
a
closing
question
from
the
group,
but
we
could
solve
it
by
email,
which
is
just
that
this
remains
a
really
small
working
group.
There's
12
folks
here
and
obviously
many
of
us
talk
offline
I,
just
wonder
whether
it
might
be
more
productive
if
we
move
from
every
other
week
meetings
to
once
a
month
meetings,
but
there's
there's
no
pressure
on
it.
If
you
guys
feel
like
this
is
useful
to
get
together
and
share,
we
can
continue
to
do
it.
B
It
seems
like
different
folks
will
show
up
on
the
different
weeks
and
I.
Don't
know
if
that's
just
their
availability
or
not
I
think
we
could
have
once
a
month
if
we
had
a
day
that
works
for
folks,
I'm
also
willing
to
just
be
here.
For
the
conversation
it
seems
like
we
get
a
good
feedback
and
seeing
the
API
snoop,
maybe
if
we
get
more
and
other
folks
involved,
we'd
have
more
people
along
the
causal.
E
E
C
Is
Chris
I
had
another
thought,
my
muted?
No,
when
I
first
voted
for
this
time
of
day
it
was
during
the
New
Zealand
summer
and
as
we're
hemisphere
opposites
when
we
shift
and
everybody
with
the
time
zone,
it
actually
brings
us
from
5:00
a.m.
to
3:00
a.m.
in
the
morning
for
the
start
of
the
call.
C
B
Know
one
thing
I
was
thinking:
Chris
was
some
folks
may
prefer
afternoon's
as
far
as
northern,
who
was
here.
So
maybe
we
could
do
one
wake
in
the
morning
and
one
week
in
the
afternoon
and
that
might
give
more
opportunity
for
folks
anyways.
We
can
follow
up
with
both
of
those
offline
either
in
the
slack
see
our
group
channel
or
on
the
mailing
list.