►
From YouTube: Kubernetes SIG Apps 20180319
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
Welcome
to
the
March
19
2018
kubernetes,
sig,
apps
I
will
be
chairing
this
meeting.
My
name
is
Matt
Farina
and
to
kick
this
off.
I
will
drop
the
agenda
and
notes
into
chat
here.
So
everybody
can
see
that
and
if
you
want
to
add
notes
or
details,
please
feel
free
to
do
so.
The
first
thing
we
have
is
an
announcement.
Last
I
checked
the
planned
release
date
for
kubernetes
1.10
was
March
26th,
which
is
next
Monday.
A
A
Yeah,
this
is
for
the
application
CRD
that
CRD
that
we
talked
about
that
has
metadata
in
it
similar
to
what
is
in
a
chart.
Yamo
file
here
is
the
link
to
that
repo.
If
you're
wondering
why
there
is
so
much
in
there
a
few
weeks
ago,
there
was
Kuby
builder
was
demoed
and
it
was
talked
about
how
to
generate
a
controller
and
Ciardi
and
metadata
from
that
and
as
I
understand
it.
That's
what
was
used
to
build
this,
and
so
the
structure
and
everything
comes
from
that.
A
So
we've
got
that
thanks
for
reading
that
in
and
so
with
that.
The
next
thing
we
have
on
here
is
a
demo
of
Kubb
apps
and
service
catalog
Evan.
Are
you
on.
C
Right,
great
so
hi
everyone,
my
name
is
Evan
lui
I
am
a
software
engineer
and
Microsoft,
and
today,
I'm
gonna
be
giving
a
talk
and
demo
about
the
result
of
some
work
that
my
team
and
I
did
with
Adnan
and
his
team
in
Vietnam
II,
actually
on
integrating
service,
catalog
functionality
to
cube
apps
I,
know
and
tells
me
about
a
couple
of
weeks
ago.
You
all
talked
about
service
catalogs
and
service
brokers
in
a
more
in-depth
conversation.
C
So
I
won't
go
too
in
depth
on
that,
but
I
will
go
over
some
general
overview
and
terms
yes.
So
when
we
start
the
actual
demo
you're,
not
all
any
of
you
who
missed
that
are
completely
lost.
So
before
our
collaboration,
we
sorta
had
two
things:
we
had
the
Service
Catalog
and
open
service
broker,
OSB
on
one
side
and
vietnamese
cube
apps
on
the
other
two
separate
tools:
sort
of
living
on
separate
ends
of
the
kubernetes
toolshed,
Service,
Catalog
and
OSP.
C
For
those
who
aren't
familiar,
it's
an
API,
an
API
to
manage
off
cluster
data
resources
in
the
context
of
a
kubernetes
cluster.
So
what
that
pretty
much
means
is
that
you're
able
to
provision
and
manage
data
services
in
the
cloud
all
without
actually
leaving
your
kubernetes
cluster,
and
then
we
have
been
Amex
Cube,
apps
I'm
sure
many
of
you
tried
it
before
it's
fit
nummies
web
dashboard
for
managing
and
employing
home
charts
to
your
Crimmins
cluster.
C
So
what
we
wanted
to
do
in
this
collaboration
was
to
sort
of
integrate
the
Service
Catalog
functionality
into
cube
apps,
because
really
often
you're
want
to.
If
you
want
to
deploy
a
production
grade
database
to
your
cluster
you're,
most
likely
gonna
well
many
times,
you're
gonna
want
to
use
a
top
providers
serving
so
just
give
a
quick
rundown
of
the
result.
We
went
from
a
user
experience
that
looked
a
lot
like
this.
C
Hopefully
you
can
all
make
that
out.
That's
the
if
you
played
with
Service
Catalog
before
that's
the
SV
cat
CLI
tool.
It
gives
you
a
basic
interface
for
interacting
with
the
Service
Catalog
right
now.
I'm
just
example:
you're
seeing
the
available
service
classes
from
the
open
service
broker
on
Azure,
so
we
went
from
a
I
user
experience
of
this
to
something
more
akin
to
this.
C
C
And
one
last
thing
to
cover
before
the
demo
are
some
basic
terms
just
so,
if
I
throw
these
terms
out
during
the
demo,
you're
not
completely
lost
if
you're
familiar
service
brokers,
the
open
service
broker
OSB,
that's
the
standardized
API,
which
stands
in
front
of
all
cloud
providers.
Now,
as
your
AWS
GCP
bulk,
you
don't
have
it
and
that
is
talked
to
using
the
service
catalog.
The
service
catalog
is
what
lives
inside
your
kubernetes
cluster
and
translates
kubernetes
resources
into
calls
vos,
be
you
have
a
service
class.
C
This
is
a
type
of
service
made
available
from
the
catalog.
So
that
could
be
my
sequel.
Databases,
toast
rest
databases.
Redis
caches
list
goes
on.
We
have
service
plans,
these
are
the
actual
in
stanchion
units
of
a
service
class.
So
if
you
wanted
to
provision
a
my
school
database,
you
don't
have
a
bunch
of
plans
varying
based
on
storage
capacity
and
dtu's.
C
You
have
the
notion
of
provisioning.
This
is
the
action
of
telling
service
catalog
to
tell
the
OSB.
To
give
me
an
instance
of
a
plan.
Of
instance,
that's
pretty
self-explanatory.
It's
the
provision
instance
of
a
service
plan,
and
then
we
have
the
notion
of
binding.
This
is
the
action
of
the
service
broker,
telling
source
catalog
the
credentials
and
secrets
for
an
instance
so
that
you
can
use
it
in
your
application.
C
D
C
Ok,
so
when
we
start
up
cube,
apps
we're
greeted
by
the
applications
view
currently,
as
you
can
see,
I
have
one
WordPress
application
installed,
but
before
we
start
doing
anything
else,
let's
take
a
look
into
the
configuration
go
into
configuration.
Take
a
look,
you'll
see
a
proposed
tours
and
service
brokers.
Let's
take
a
look
at
our
service
brokers.
You
see,
we
currently
have
awesome
asura
setup.
The
open
service
broker
for
Adger
Cubase
currently
expects
you
to
install
your
service
records
prior
to
prior,
but
outside
of
the
actual
Cubase
experience.
C
I
still,
managing
and
selling
brokers
is
outside
of
the
scope
of
cubes
and
felt
so
I
currently
have
one
service
broker
set
up
calls
ba.
Let's
take
a
look
at
our
app
repositories.
We
currently
have
3
a
purple,
Satori's
setup,
incubator,
stable
and
the
Service
Catalog
repository.
These
are
the
repositories
that
cube
apps
are,
is
going
to
draw
its
charts
run
for
installation.
C
So
let's
go
back
to
applications
and
let's
say
we
wanted
to
deploy
a
new
wordpress
instance,
so
a
new
wordpress
instance
using
a
managed
by
sequel
database.
So
in
that
case,
we're
gonna
provision
new,
my
sequel
database
using
Azure.
As
you
can
see,
we
currently
have
two
my
sequel
database,
that
set
off
cluster
right
now.
But
let's
provision
a
new
one
here-
and
here
we
see
the
screen
that
I
showed
in
the
slides
earlier.
C
It
will
give
our
service
instance
a
name,
so
my
brand-new
PI
sequel,
we're
going
to
provision
to
the
default
namespace
and
then
you'll
see
the
list
of
available
classes
here
and
planned
pre-selected.
Here
are
some
basic
parameters
that
we're
going
to
be
passing
off
to
adjure
as
well.
These
are
as
your
specific
parameters
right
now,
so
that's
going
to
be.
This
database
will
be
provisioned
in
the
east
us
data
center
and
in
the
default
resource
group
and
sure.
C
And
then
up
right
here
so
now,
as
you
can
see,
we
have
a
third,
my
sequel
instance
and
it
is
currently
being
provisioned
asynchronously.
So
if
we
click
into
details,
you
will
see
a
more
detailed
view
as
to
what
we
just
did.
You
can
see
the
status
of
that
service
instance,
so
it's
not
currently
ready
and
it's
currently
being
provisioned.
You
see
the
class
and
the
plan.
C
That
is
that
it
has
and
any
available
bindings
for
it
because
provisioning
databases
on
Azure
and
in
general
it
takes
a
while
we're
going
to
instead
use
some
presentational
magic
and
take
a
look
at
one
of
the
data
that
I
provisioned
last
night.
So
let's
take
a
look
at
my
new,
my
sequel,
as
you
can
see
here,
it
is
ready
and
successfully
and
currently
has
no
bindings,
as
I
mentioned
earlier
bindings
on
it.
Creating
bindings
is
the
action
of
generating
secrets
so
that
your
applications
within
kubernetes
can
consume
it.
C
So
if
we're
going
to
create
a
board,
a
new
WordPress
we're
gonna
need
some
bindings,
that's
great
a
binding.
So
we
can
go
my
new,
my
sequel,
binding
yep,
we're
pointing
it
to
that
instance,
this
instance
and
we're
going
to
create
the
binding
in
the
default
database.
Let's
create
the
binding
and,
as
you
can
see
the
bindings
here
and
the
binding
has
been
injected
successfully,
we
expand
it,
and
here
you'll
see
a
list,
the
list
of
secrets
that
you
will
need
to
actually
use
the
database
inside
your
application.
C
So
now
that
we
have
the
binding
created,
let's
go
back
to
applications
and
click,
deploy
new
app
we're
brought
to
the
charts
view.
These
are
the
charts
surfaced
through
the
three
app
repositories
you
saw
earlier
and
if
we
scroll
all
the
way
to
the
bottom,
you'll
see
word
for
us
right
here.
So
I'm
gonna
click
on
WordPress
and
if
any
of
you
have
used
a
Cubase
before
this
used
for
a
fairly
familiar
got
the
readme
and
we
also
have
short
versions
available
for
deployment.
So
you
can
click
through
these
and
you'll.
C
You
can
choose
which
version
of
the
church
deploy
so
right
now
we're
just
going
to
choose
the
latest:
we're
gonna,
collect
employees
and
helmet.
This
is
another
function.
Another
feature
that
we
worked
on
bit:
Nami:
there's
the
ability
to
actually
modify
the
package
values.
I
am
will
file
that
comes
with
the
chart.
This
is
this
one's
very
important
and
makes
thanks
using
it
a
lot
of
user.
So,
let's
give
our
WordPress
application
a
name.
C
I
knew
WordPress,
let's
put
deploy
it
to
the
default
namespace
and
if
you
look
through
the
value
style,
Yama
file,
you'll
notice
that
you
can
know
it
an
external
database
to
do
so.
Where
you
should
mark,
you
should
tell
the
chart
to
not
provision
in
in
questa
Maria
DB,
so
set
where
you
DB
to
false
under
bindings
on
the
right
side.
Here,
you'll
notice
that
we
have
a
list
of
bindings
currently
in
our
cluster,
my
new,
my
sequel,
binding,
that's
the
one
we
just
created.
Let's
click
on
that,
then
you
can
see.
C
C
Database
and
that's
it-
you
click,
Submit
and
the
chart
starts
to
its
deployment,
because
and
because
deploying
databases
takes
a
while
in
the
cloud
we're
gonna,
pull
some
more
presentational
magic
and
take
a
look
at
the
WordPress
instance
that
I've
deployed
last
night
as
well.
So
we're
gonna
take
a
look
at
default.
My
WordPress!
This
is
the
one
that
I
deployed
last
night
and
this
is
deployed
using
the
exact
same,
the
exact
same
way
that
we
just
employed
the
other
one.
So
with
a
after.
C
C
C
A
C
F
C
This
was
a
UX
pain
point
that
we
mean
done
and
the
rest
of
team
are
discussing,
because
there's
no
standardized
way
to
initial
standardized
values
yet
will
file
or
no
standardized
way
to
map
bindings
to
any
particular
yellow
file
like
there's
no
name
convention
or
anything
like
that
it
for
now
it
has
to
be
a
copy
and
paste
job
until
we
sort
of
reached
that
standardized
way
of
exposing
finding
information
inside
of
Bally's.
C
A
E
One
other
thing
to
mention
on
that
front
is:
there's
some
work
going
on
in
six
service
catalogs
well
to
try
and
solve
this,
because
one
of
the
issues
is
that,
depending
on
what
broker
you
use,
you're
going
to
get
different,
you
know
AWS
might
call
it
hostname
for
its
articles.
It
host,
for
example,
in
the
secret.
E
So
how
do
you
know
what
those
piece
is
is
an
issue
right
now,
so
there's
some
work
going
on
to
create
some
sort
of
mapping
in
in
service
catalog,
so
so
that
might
be,
and
essentially
correct,
treating
bindings
kind
of
like
persistent
volume
claims
so
that
the
binding
would
just
go,
and
you
could
just
say
I,
wonder
my
sequel
service
and
then
the
cluster
would
know
something
that
exists.
That
can
provide
for
that.
My
sequel
service.
G
Like
I
mean
they're,
just
just
a
bit
of
an
outside
comment,
I
guess,
but
it
doesn't
seem
like
it
would
be
much
easier
if
we
just
had
a
convention
for
these
things
there
versus
providing
layers
and
layers
of
configuration.
I
would
think
that
you
know
it
could
be
just
a
my
sequel
service
in
that
namespace
that
the
client
is
deployed
to
and
and
there
could
be
a
secret
like
just
called
my
sequel
house,
and
that
secret
would
contain
two
standard
keys
like
password
and
usually
well.
Why?
Why
do
we
need
extra
layers
of
configuration?
G
C
A
G
E
A
A
A
H
You
so
much
for
having
me
and
hello
to
everyone
in
sagat's
land
I've.
Actually,
you
know
I,
don't
think
been
on
the
call
in
five
months,
so
that
I
am
actually
intending
on
changing
and
that's
actually,
why
I'm
here
today?
For
those
who
don't
know
me,
I
am
a
co-chair
of
contributor
experience.
Please
disregard
my
hat.
I
am
technically
on
PTO
today,
but
I
did
not
want
to
miss
this.
So
first
things,
first
I
did
drop
a
link
in
the
agenda
and
I
did
share
it
with
the
kubernetes
saying
the
apps
Google
Groups.
H
So
you
should
have
access
to
what
I'm
talking
about,
but
it
is
a
very,
very
long,
verbose
dock
that
I'm
not
going
to
be
able
to
get
through
in
ten
minutes.
But
the
intention
with
this
is
a
roadshow
of
sorts
that
contributer
experience
is
going
to
be
doing
now
on
a
quarterly
basis
and
going
to
all
the
SIG's,
which
is
roughly
37,
SIG's
and
working
groups
at
this
point,
just
to
make
sure
that
everybody
is
on
the
same
page
with
the
work
that
we're
doing
in
contributor
experience.
H
It's
very
important
that
we're
all
on
the
same
page
for
multiple
reasons,
but
one
the
most
important
is
that
everybody
on
this
call
right
now
is
considered
a
contributor
in
some
fashion.
So
this
is
all
very
relevant
stuff
and
I
know
Matt
and
several
other
people
in
leadership,
as
well
as
just
several
of
your
members
have
come
to
our
meetings
talked
about.
Why
and
how
we're
changing
things
across
the
board
and
how
we're
communicating-
and
this
is
just
really
us-
just
kind
of
making
these
connections.
H
So
what
I'd
like
to
do
is
just
kind
of
blow
through
this
really
quickly
and
if
you
have
any
immediate
questions
for
me,
shoot
but
I'd
really
like
you
to
take
all
this
information
in
and
then
maybe
I
come
back
or
maybe
Matt
or
someone
can
can
come
to
one
of
our
contributor
experience
meetings
and
then
give
it
any
feedback,
or
we
can
even
start
a
discussion
on
on
your
mailing
list,
etc,
etc.
So,
first
things
first.
H
So
that
is
a
lot
and
we're
noticing
that
if
someone
is
contributing
to
one
repo,
it
is
highly
likely
that
they're
contributing
to
another,
whether
or
not
they're
contributing
more
than
that
is
kind
of
I,
don't
know,
but
it
would
be
nice
so
that
contributors
have
the
same
experience
across
the
board.
We
have
CI
and
things
like
that.
For
example,
some
of
the
recent
things
that
we've
been
working
on
but
again
I
think
some
of
your
folks
already
know
is
what
exactly
the
explicit
meaning
of
looks.
H
Good
to
me
is
the
Phaedo
ba,
which
is
the
scale
issues.
Label
definitions
across
the
board
is
something
that
we're
working
on
right
now,
like
what
exactly
does
it
mean
when
you
throw
down
the
Help
Wanted
label?
Does
that
mean
that
it's
a
good
first
time
issue
for
someone?
Does
that
mean
it's
a
it's
good
for
first
for
new
contributors
or
doesn't
mean
exactly
what
it
says
with
please
new
contraband
freak
she's
me
please.
Current
contributors
come
and
help
us
with
this.
We
need
immediate
help
on
this,
which
isn't
necessarily
great
for
first-time
contributors.
H
We've
also
been
doing
a
lot
with
issue
triage
and
we're
really
wondering
and
curious
what
your,
what
the
thoughts
are
on
applying
current
issue
issue
triage
guidelines
across
all
of
the
kubernetes
repo
orgs,
as
I
said
before,
the
guidelines
are
included
in
the
docx
that
I
shared.
So
please
feel
free
to
take
a
look
at
that
and
give
us
some
feedback
on
the
on
the
issue
itself.
H
New
labels
work.
That's
something
that
we're
working
on
identifying
issues
for
closing,
so
that
we
can
do
things
like
the
snail
bot,
and
this
really
is
helping
us
with
providing
relevant
stats
on
dev
stats
and
for
those
who
have
not
seen
dove
stats.
Yet
it's
Cates,
I'm
gonna,
throw
this
in
the
chat
right
now.
Actually,
it's
kate's,
that's
das,
at
CNCs
IO,
and
that's
where
all
these
metrics
and
things
that
are
coming
from,
and
so
one
of
them
one
of
the
dashboards
actually
is
talking
about
labeling.
H
How
are
you
actually
finding
out
about
this,
and
we
lay
this
out
in
our
Charter
actually
just
recently,
and
we
thought
that
it
was
very
important
for
us
to
lay
this
out
so
that
we
have
consistency
across
the
board
again
because
there
are
37
SIG's
and
it's
impossible
for
us
to
go
to
them
all
of
the
time,
every
time
we're
making
a
change.
So
what
we're
going
to
do
is
we're
gonna
lazy
consensus,
this
with
a
time
box
of
at
least
72
hours
to
to
first
the
contributor
experience
mailing
list.
H
So
that's
where
we'll
actually
socialize
it
within
our
group.
First
and
we'll
also
have
a
very
specific
subject
line
so
that
people
can
notice
that
this
is
a
change
that's
coming
out
and
then
once
we
socialized
it
and
gotten
me,
the
appropriate
okay
is
from
from
our
group.
Then
we're
gonna
time
box
it
again
with
a
lazy
consensus
for
at
least
72
hours
with
the
following
mailing
list.
And
that's
what
excuse
me?
H
That's
going
to
be
a
contributor
experience
again,
that's
going
to
be
sig
leaves
mailing
list
and
that's
going
to
be
the
kubernetes
dev
mailing
list
and
then,
after
with
no
objections,
we're
going
to
release
and
then
announce
it
at
the
community
meeting
every
Thursday
in
the
announcement
section
or
if
we
have
a
contributor
experience
update,
then
we'll
do
it
there.
So
that's
the
communication
channel,
if
you
will
fur
for
us,
so
does
anybody
any
questions,
concerns
or
comments
about
that?
H
H
H
Okay
cool
now
we
do
have
a
new
version
of
the
contributor
guide.
This
is
something
that
we've
been
working
on
for
a
long
time,
so
he
wanted
to
see.
If
you
could
review
it,
make
comments
poke
holes
at
it.
This
is
our
first
shot.
We
had
lovely
lovely
contributors,
help
us
with
this,
and
we
actually
had
a
lot
of
new
contributors
help
with
this,
which
was
awesome
to
get
their
perspective
and
that
really
helped
us
with
making
edits
and
things
like
that.
Now,
a
developer
guide
portion
is
coming
to
that.
H
Both
of
these
Doc's
will
actually
be
surfaced
on
a
new
contributor
site
which
I'll
talk
about
in
a
second,
but
right
now,
they're
actually
being
surfaced,
kubernetes
io
and
that's
where
that
information
will
be
populating.
One
of
the
biggest
things
that
we've
heard
from
those
contributors
is
the
discoverability
of
docs
in
the
community.
Repo
is
lacking.
So
this
is
our
attempt
to
a
make
those
better
and
B
make
them
more
discoverable.
So
now,
if
you
do
Google
search,
do
some
Google
searches
on
things
that
are
related
to
kubernetes
contributing
it.
H
You
should
be
getting
first
page
results
at
this
point
for
the
for
the
correct
information.
So
one
thing
in
that
same
breath
that
we
are
trying
to
push
is
to
make
sure
that
all
repos
have
contributing
markdown
files.
That
link
to
this
main.
This
means
contribution
guide,
as
well
as
any
differences
that
that
repo
has
against
that
guy.
So,
for
instance,
you
know
if
your
repo
is
using
some
other
version
of
CI,
then
it
should
be
indicated
and
you're
a
contributing
markdown
file.
If
not
that
it
just
shouldn't
flick,
then
it
should
just
simply
list.
H
The
contributor
died
link
in
your
contributing
markdown
file.
We
have
taken
some
pummels
with
new
contributors
and
they
are
indeed
looking
for
contributing
markdown
files
and
all
repo-
it's
not
just
community
repos.
If
you
need,
if
anybody
on
the
colony
it's
a
template
like
I
know,
helm
has
a
really
great
one,
but
if
anybody
on
the
line
has
a
repo
on
the
side
and
needs
a
contributing
markdown
file
template,
we
can
help
you
so
just
reach
out.
H
Now.
Next
part
is
mentoring
and
I
know.
We
do
have
quite
a
few
see
gaps.
Folks,
helping
us
out
with
the
incubation
of
some
of
these
mentoring
initiatives,
all
the
initiatives
that
I'm
about
to
say
are
what
I
consider
incubation
stage.
What
that
means
is
that
we're
trying
them
out
all
of
them
are
non-traditional.
This
is
actually
something
that
I'm
talking
about
acute
con
in
Copenhagen,
so
quick
plug
for
my
talk,
but
these
are
all
not
traditional
one
on
one
where
you
stay
with
that
mentor
forever.
H
H
This
is
sort
of
a
mentors
on
demand,
if
you,
so,
if
you
have
a
quick
question,
whether
it's
about
your
career,
whether
it's
about
your
growth
within
the
kubernetes
organization
and
whether
it's
about
end-to-end
testing
or
you
know,
if
you
want
to
know
what
Matt
Farina
does
on
the
weekends,
all
of
those
questions
are
applicable,
and
that
happens
once
a
month,
every
Wednesday
there
are
two
time
zones,
we've
had
two
of
them
already
and
they're
actually
really
really
fun.
We
had
six
contributors
on
the
first
Wednesday
of
this
month
and
it
was
really
really
fun.
H
It's
giving
them
a
stipend
to
do
the
work,
which
is
very
helpful
with
underrepresented
folks
per
research
on
why
they
don't
contribute.
So
since
we're
now
over
the
next
semester
starts
in
the
fall
slash
winter.
So
the
call
here
is
more
like
if
you
are
a
sponsoring
organization
that
would
like
to
help
us
out
with
this
Google
and
CNCs
helped
us
out
this
last
semester.
But
if
you
are
a
sponsoring
organization
or
would
like
more
information
to
reach
out
to
me
or
if
you'd
like
to
sponsor
a
sponsor
a
project.
H
H
No
group
mentoring.
This
is
something
that
is
targeting
all
contributor,
laughs,
bladder
levels
and
it's
really
taking
a
lot
of
peer
mentoring,
concepts
and
pairing
them
with
some
of
the
scalable
infrastructure
that
we
already
have,
which
is
slack
and
putting
people
together
that
are
all
on
the
same
matter
level
so,
for
instance,
members
currently
who
we're
all
looking
to
decode,
reviewers
and
taking
them
and
seeing
if
you
can
elevate
and
escalate
their
their
time
to
that
reviewer
level.
Right
now,
we
are
in
a
test
case
with
that.
H
The
test
case
is
wrapping
up
here
shortly
in
the
next
couple
of
weeks,
and
from
that
test
case
we
know
that
we're
gonna
have
at
least
three
people
graduate,
which
is
great
one
of
the
things
that
we
learned
is
that
we
are
not
going
to
do
group
mentoring
across
time
zones
that
have
been
our
major
major
killer,
but
I
really
just
wanted
to
launch
the
test
to
see
to
see
what
it
looked
like
and
how
we
could
operate
this
because
fruit
mentoring
is
not
a
concept
that
is
familiar
in
open
source
territory.
So
this
is.
H
This
is
kind
of
what
I'm
I'm,
placing
a
lot
of
bets
on
on
how
we
can
scale
fast
in
areas
that
we
feel
we
need
that
kind
of
scale.
So,
if
you
are
on
the
call-
and
you
are
interested
in
this
kind
of
a
program-
I
am
going
to
whip
together
another
cohort
here
shortly,
but
this
cohort
is
going
to
be
new
contributors
to
members.
I'd
also
like
to
spend
one
up
for
reviewers
who
are
Kurvers
as
well,
and
the
cool
thing
about
group
mentoring
is:
there
is
no
start
date.
There
is
no.
H
There
are
no
like
hard
rules
necessarily
so
this
means
that
we
can
spin
up
groups
at
any
time
anywhere,
and
these
groups
are,
you
know
at
least
eight
people.
So
that's
where
the
scale
idea
is
coming
from
and
then
now
we
have
also
a
proposed
Buddy
Program.
The
name
is
definitely
TBD
there,
but
the
idea
here
is
to
kick
it
a
little
bit
more
traditional
with
that
one-on-one,
but
it's
a
one-time
one-hour
deal.
H
So
that's
something
that's
we're
going
to
try
to
roll
out
within
the
next
two
weeks
as
well,
and
then
I'm
almost
done.
I
swear
on
my
life
that
ended
the
mentoring
section,
slack
maintenance,
I,
know
slack
is
a
very
hot
topic
in
our
group
right
now,
but
regardless
of
whether
or
not
it's
a
hot
or
cold
topic,
slack
maintenance
is
very
important.
That's
actually
how
we're
onboarding
a
lot
of
new
people
into
our
projects.
H
I
looked
at
the
data
last
night
and
we
on
board
a
2,000
people
in
the
last
30
days
on
slack
alone,
which
is
key.
That's
a
nine
percent
difference,
which
is
it
again
huge,
so
things
like?
Do
you
have
important
Doc's
pinkier
channel?
Do
you
have
a
purpose
description?
This
is
important
because
new
people
will
be
able
to
pick
things
up
a
lot
faster.
We
also
have
slack
guidelines.
Now
we
have
a
slack
admin
channel.
H
Please
join
us
if
you
need
anything
at
all
and
feel
free
to
pin
things
like
charter
meeting
notes,
agenda
items,
etc.
That
really
helps
out
other
people
try
to
figure
out.
What's
going
on
in
your
groups
and
then
office
hours
office
hours
is
for
users,
it's
something
that
we
do
once
a
month
as
well.
It's
this
Wednesday
and
George
passed
wrote
ft.
/
NZ
and
we're
always
looking
for
new
folks
to
help
field
questions.
H
This
is
a
great
way
for
you
to
get
in
contact
with
your
user
base
and
other
people
that
are
using
kubernetes
that
are
having
questions
a
lot
of
these
questions.
We
actually
pick
up
as
routine
questions
and
then
George
save
that
saves
those
so
that
we
can
try
to
the
docks
in
that
area
and
then
it's
it.
Oh,
my
gosh
I
was
so
long-winded,
I'm,
so
sorry
that
it's
only
this
is
only
hopefully
a
one-time
thing.
H
A
I'm
taking
silence
as
no
all
right
Paris,
if
you
actually
wants
to
ground,
we
do
have
a
charter.
We're
gonna
talk
about
that,
actually
in
a
doc
based
on
the
template.
That's
what
we're
gonna
come
up
to
here
in
just
a
minute.
So
so
thank
you.
Paris!
Then
we'll
get
into
a
number
of
updates
from
some
of
the
different
projects.
If
we
have
them,
and
so
the
first
we'll
start
with
the
kubernetes
core
stuff,
do
we
have
any
updates
on
sets
or
jobs.
D
A
Yes,
I
around
with
it
I
would
wait
until
next
Monday
to
play
around
with
it.
If
I
understand
it,
there's
some
bugs
in
it
that
are
being
worked
out
this
week.
But
and
it's
an
alpha
feature
only-
you
have
to
turn
on
alpha
feature
stuff.
Will
they
work
through
this,
but
the
idea
is
to
the
daemon
set
scheduler
daemon
set
has
scheduler
code
in
it,
and
we'd
like
to
consolidate.
That
down
is
is
what
some
of
the
scheduling
folks
would
like
to
do,
and
so
this
is
work
being
done
to
head
in
that
direction.
Yeah.
B
So
it's
like
Matt
said
it's
an
abled
alpha,
meaning
that
it's
not
enabled
by
default
and
only
the
demon
set
scheduler
for
the
core
workloads.
Api
went
around
the
default
scheduler
anyway,
so
it
doesn't
affect
staple
center
deployment
or
anything
else
you
can
play
around
with
it
and
the
main
use
cases
that
we
needed
to
do
this
well.
B
This
was
one
path
to
supporting
priority
and
preemption
and
in
order
to
deconflict
the
demons
that
schedulers
interaction
with
the
default
scheduler,
this
was
the
fact
that
was
taken,
so
it
the
bug,
fix,
was
merged,
I
believe
today,
so
it
should
probably
be
available
on
head
in
somewhat
functional
today.
If
you
do
want
to
play
with
it,.
A
All
right,
so,
if
there's
nothing
else
that
sets
our
jobs,
we
will
jump
into
the
sig
charter
because
we're
a
little
short
on
time.
Here
we
got
about
13
minutes
left
and
we
want
to
get
through
that.
There's
a
link
here
to
the
Charter.
Let
me
make
sure
my
screen
real
quick
and
we
can
I
want
to
maybe
highlight
this
for
a
minute
and
talk
through
it,
and
then
we
can
make
any
decisions
on
it.
Next
week
see.
A
Let
me
can
you
all
see
my
screen
yep
all
right,
so
this
is
the
Charter
it's
linked
in
the
document.
I've
highlighted
and
commented
on
the
areas
that
we've
changed
or
decisions
that
were
made.
Some
of
us
discussed
it
throughout
the
week,
but
really
there
are
only
a
few
of
us
who
did
any
of
the
discussion
on
it.
So
we
would
love
more
input
and
feedback,
whether
it's
a
comment,
a
thought
or
anything
like
that.
A
There's
the
default
template
for
charters
and
I'll
talk
through
here,
real
quick
on
what
we
deviated
from
really
the
template
talks
about
governance,
and
it
doesn't
include
a
section
for
scope,
and
so
what
I
did
was
I
copied
over
the
current
scope
from
the
readme
to
stick
scope
into
the
Charter
as
well
as
governance,
I
mean
that's
the
first
thing.
A
But
we've
acted
more
in
a
chair
role,
and
so
in
this
it
kind
of
changes.
What
we've
done
to
chair
it
formalizes?
How
folks
come
into
being?
How
many
there
are
all
of
those
details
we
lined
out
the
sig
technical
leads,
because
really
the
way
we've
operated
is
the
owners
of
the
sub
projects
have
been
the
technical
leads
for
their
sub
projects
and
we
didn't
see
a
need
to
add
or
change
anything
between
chairs
and
that
or
in
any
other
capacity.
A
And
so
that's
just
because
it's
optional,
we
lined
it
out
because
we
don't
need
it
on
the
sub
projects.
The
one
change
we
made
to
the
sub
projects
was
to
say
15
as
a
possible
set
of
owners,
because
the
reality
is
we
have
over
ten
on
a
couple
of
sub
projects
today
now
that
number
may
need
to
be
adjusted
and
accommodated,
but
that
15
was
just
bumped
out
to
not
say
unlimited,
although
we
could
probably
have
a
discussion
on
whether
there
should
be
unlimited
or
you
know.
A
Where
does
that
come
from,
and
that's
that's
the
number,
because
a
couple
of
them
have
like
10,
11,
12
and
so
thoughts
totally
open
to
whatever?
Should
we
drop
the
Mac?
Should
we
not
there
is
this
identification
of
somebody
who's
a
member
in
in
all
of
this?
This
is
part
of
it,
and
I
would
love
for
folks
who
are
here
to
maybe
give
their
two
cents
on
it,
because
I
know
we
have
a
whole
lot
of
people
who
who
drive
by
or
or
attend
the
meetings
and
whatnot.
A
And
if
anybody
has
comments
on
what
it
is
to
be
a
member-
and
we
don't
do
really
much
with
that
at
the
moment.
But
there
might
be
things
in
the
future
that
take
advantage
of
this,
and
so
it
would
be
important
to
get
two
cents
on
the
other
things.
Let's
see
sub
project
creation
all
right.
So
one
of
the
things
that
we
did
here
was
there
were
two
options,
one
by
federation
of
sub
projects
and
all
their
owners.
And
then
the
other
was
by
technical
leads
and
we
didn't
have
technical
leads.
A
So
I
changed
this
to
say,
chairs
and
instead
of
Federation
of
sub
projects.
Because
if
you
look
at
all
of
the
sub
projects
owners,
we
have
across
all
of
the
sub
projects,
we're
probably
talking
to
30
people,
30
some
people
and
that's
a
lot
of
people
to
get
together
to
try
to
make
any
decisions
on
creation
of
sub
projects
and
repos,
and
things
like
that
who
have
very
different
concerns,
and
so
this
was
stuck
in
here's
a
spit
ball.
A
But
if
people
have
other
ideas
on
how
to
change
this,
please
do
this
is
pretty
much
how
we've
operated
today
and,
of
course,
we
always
try
to
do
lazy
consensus.
The
other
thing
we've
updated
is
they
can
be
created
by
kept
proposal
with
a
fallback
to
majority
vote.
So
look
at
how
the
sub
projects
are
created,
but
really
this
was
just
a
tweak
to
what
we've
done
today,
because
trying
to
get
together
all
the
sub
project
owners
to
talk
about
how
to
create
another
sub
project.
Is
it's
just
a
complicated
task
for
a
cigar
size?
A
A
There
were
some
changes
that
were
made
to
the
technical
process
here
for
proposing
and
making
decisions
on
those
because
a
lot
of
the
sub
projects
we
have
don't
follow
the
typical
sub-process
you
might,
if
you
were
just
created
in
the
kubernetes
sense,
helm,
charts
compose
a
lot
of
these.
Don't
follow
the
normal
standard
way
about
going
with
things
and
then
the
other
thing
was
at
the
bottom
here.
Issues
involving
since
there
aren't
technical
leads.
We
updated
that
to
just
say,
chairs
and
really
the
way
we
have
been
doing.
That
is.
A
We
just
try
to
sit
down
and
get
folks
together
and
work
on
some
kind
of
consensus.
We've
never
really
had
to
do
anything
other
than
that,
because
most
of
the
projects
are
at
the
end
of
the
day
owned
by
their
owners,
and
it
hasn't
really
been
an
issue,
and
so
this
is
this
is
the
updates
from
the
templates.
Otherwise,
it
generally
follows
the
the
short
template.
That's
been
proposed
and
been
merged
into
the
community
repo.
A
My
hope
is
because
I'd
like
to
get
to
some
of
the
other
stand-ups
here,
real
quick
that
we
can
review
it.
Y'all
can
review
it
add
comments
in
here.
As
you
see
fit,
ask
questions
and
then
maybe
next
week
we
can
give
a
little
bit
more
time
and
lazy
consensus
vote
on
it.
If
that's
alright,
does
that
sound
acceptable.
A
J
I
was
just
waiting
for
someone
else
to
respond,
but
I
can
I
can
respond
to
that
not
not
too
much
from
helm
side
over
here
there
was
282
was
released
last
week
and
there's
a
couple
of
good
fixes
that
were
in
there.
So
if
anyone
is
on
two
eight
zero,
two
eight
one,
please
upgrade
it
to
a
two.
Otherwise
steady
as
she
goes
until
Cabrini's
1.10
is
released
and
we'll
go
with
communities.
1.9,
I
guess
I
mean
helm.
2.9
I
also.
A
A
All
right,
I
guess,
I'll
a
little
bit.
Ooh
charts
is
moving
along
at
a
breakneck
pace.
We've
had
lots
of
merges
in
the
last
month,
we've
had
well
over
300
PRS
merged,
we're,
probably
getting
just
under
a
hundred
a
week
right
now,
so
things
are
moving
at
at
a
pretty
good
pace.
There
have
been
a
couple
of
changes
and
proposed
changes
to
CI
to
kind
of
add
more
detail
when
CI
fails,
so
we
can
understand
what's
going
on.
A
We
also
have
a
whole
lot
of
comments
or
a
whole
lot
of
spelling
fixes
and
grammar
fixes
coming
to
charts.
So
if
you
see
that
the
PRQ
is
kind
of
high
right
now,
that's
probably
because
there's
you
know
20
or
30,
or
maybe
even
more-
that
are
just
language
fixes
within
the
church
themselves
as
folks
go
through
and
nitpick
on
those
that's
kind
of.
What's
going
on
there
I'd.
E
Also
add
that
one
of
the
things
that
we're
doing
right
now,
it's
specific
me
right
heart
is
doing-
is
adding
support
to
have
custom
Yama
files
going
through
CI.
So
if
there
are
particular
values
that
are
required,
we
can
still
make
the
CI
a
pass
with.
You
know,
dummy
values
or
something
that
would
allow
it
to
to
pass
and
test
that,
because
right
now,
that's
not
really
possible
for
required
helm
values.
F
F
So
it's
a
little
bit
limited
right
now,
but
you
can
there's
some
instructions
on
the
readme.
If
you
want
try
it
out,
there's
also
discussions
around
authentication.
So
if
you're,
if
you
have
strong
opinions
on
how
authentication
in
chart
repose
should
work
in
general
come
join
us-
and
some
of
this
is
gonna
kind
of
tie
into
down
three
talks
as
well.
So
yeah.
E
I
can
do
a
quick
update
so
we're
working
on
integrating
cube
lists,
the
function
platform,
seventh
platform
for
communities
in
Turkey
BAPS.
So
right
now
it's
kind
of
a
loose
integration,
so
we're
trying
trying
to
integrate
more
and
hopefully
have
a
release
for
that
by
the
end
of
the
week.
Other
than
that
to
try
out
give
us
feedback.
A
Oh,
we
may
have
lost
Ken
yeah.
B
Okay,
I'm
here,
okay,
so
the
repo
is
open.
I'm,
gonna
start
opening
in
some
issues
to
continue
discussions,
I'd
really
love
to
get
feedback
from
some
of
the
hell
maintainer.
In
terms
of
what
else
we
feel
like
needs
to
go
into
the
CR
D
or
if
there
are
things
that
we
think
should
be
removed.
I
for
this
I
took
a
minimal
subset
of
what
people
had
kind
of
agreed
upon,
based
on
the
gap
and
tried
not
to
include
things
that
were
contentious
and
then
I
want
to
open
issues
up
to
discuss.
B
Them
were
contentious
points
and
come
up
with
the
right
solution,
as
opposed
to
just
a
solution,
so
it's
there
and
whenever
people
want
to
start
carousing
through
it
getting
feedback,
that's
great
I'm
gonna
have
to
probably
make
some
modifications
based
on
updates
to
cou
B
builder
in
the
near
future,
and
Kuby
builder
is
now
a
an
official
sub-project
of
API
machinery.
So
access
to
that,
for
everyone
should
be
a
lot
easier
and
that's
pretty
much.
It.
A
All
right:
well,
that's
what
we
have.
We
had
another
discussion
topic
for
the
application.
Crd
metadata,
there's
a
whole
bunch
of
metadata
in
that
that
we
wanted
to
kind
of
walk
through
and
get
to,
but
it
doesn't
look
like
we're
gonna
get
to
it
this
week.
So
next
week's
a
discussion
topic
week,
I
move
the
discussion
there,
along
with
the
cig
Charter,
and
so
we
can
chat
about
that
next
week,
and
so
we
got
a
minute
left.
Did
anybody
have
any
final
parting
words.