►
From YouTube: Contributor Summit NA 2019: New Contributor Workshop - Setting Up Your Dev Environment
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
A
So
if
you
know
how
to
use
get-
and
you
know
how
to
use
go-
and
you
know
how
to
check
out,
if
you
burn
a
tease-
and
you
know-
work
with
docker
you're
in
the
wrong
place
go
over
there,
but
I
think
we
got
that
figured
out
all
right
so
this
morning
we're
gonna
do
real,
quick
overview,
12:30
we're
breaking
for
lunch,
so
we're
gonna
push
hard
at
this
afternoon.
We're
gonna
do
a
bunch
more
fun
stuff,
all
right,
so
the
architecture
overview
I'm
gonna
talk
about
this
very
briefly.
A
It
is
designed
to
be
a
simple
image.
Essentially
you
have
congrads
those
can
be
vm's.
Those
can
be
bare
metal
whatever
you
want
to
run
it
on.
They
have
a
control
plane,
the
kubernetes
api
applied
to
them
and
they
can't
be
managed.
The
nodes
can
be
managed
with
some
of
the
kubernetes
api
is
actually
which
is
fun,
and
then
you
have
client
libraries,
a
UI
curl
and
cuba
cuddle
or
Kubb
cuddle.
A
However,
you
wanna
say
that
those
become
object:
definitions
into
the
API,
so
pretty
simple,
like
input
workflow
for
kubernetes,
but
there's
a
lot
of
machinery
behind
it.
So
some
more
of
that
machinery
imagery
right
here.
If
you
need
to
use
persistent
data,
there's
a
thing
for
that.
If
you
need
to
use
any
kind
of
network
policies
or
security
policies,
there's
options
for
that
as
well,
don't
be
afraid
it's
not
as
intimidating
as
it
looks
all
right.
B
A
A
You
all
right,
so
this
is
a
high-level
kubernetes
work.
Easiet.
If
you
notice
the
main
pendra
repository
is
kubernetes.
That's
where
everything
pretty
much
lives,
there's
also
community
repo
enhancements
the
website
itself,
everything's
in
a
repo,
every
sig
has
its
own
repo,
but
most
of
the
criminals.
Codebase
lives
under
crew
readies.
A
So
let's
go
into
that.
So
you
will
hear
this
github.com
kubernetes,
/
kubernetes,
referred
to
as
k
/
k
in
the
community.
Quite
often,
if
you
see
k,
/
k,
that's
what
they're
referring
to
is
this
organization
or
this
github
repo,
so
the
main
sections
that
we're
going
to
touch
here,
because
I
have
to
pull
up
my
notes
for
this,
because
so
you
will
see
all
this
to
build
super
important
directory
right.
So
if
you
want
to
build
crew
Moretti's
everything
you
know
is
in
here,
including
all
the
prereqs.
A
So
if
you
are
working
on
kubernetes
like
the
actual
codebase
come
here,
first
make
sure
you've
read
up
on
this
there's
also
a
contributor
guide,
that's
in
the
community
repo
as
well.
That
was
linked
in
the
slides
earlier.
That's
like
a
checklist
of
how
to
get
started,
but
when
you're
building
kubernetes
start
here
first
of
a
command,
so
this
is
the
CLI
library.
A
So
all
the
CLI
tooling,
for
kubernetes
is
under
these
directories,
cube
idiom,
a
cube,
cuddle,
the
cubelet
itself.
All
the
you
know
see
lights
wings
right
there
for
it
that
all
lives
here.
So
if
you're
interested
in
improving
coop
cuddle
outputs-
or
you
know,
you
want
to
add
some
functionality
to
cuddle
itself
great
place
to
start.
A
A
So
all
the
so,
let's
look
at
cube,
cuddle,
there's
a
command
itself.
There's
the
docs
build
files,
everything
you
need
right
there,
but
there's
all
the
coop
cuddle
code
right
there.
That's
it!
That's
it!
It's
a
lot
of
it's
a
lot
of
lines
of
code,
but
don't
be
intimidated
by
it.
You
can
get
to
it.
It's
right
there,
sorry,
all
right!
A
A
A
Instructions
for
using
it
adding
things
to
staging
everything
is
here.
The
one
thing
that
we
are
trying
to
work
on
very
hard
is
getting
the
documentation
that
isn't
github
exposed
better.
So
if
you
have
ideas
around
that,
I
was
talking
to
somebody
earlier.
Let
me
know
because
this
isn't
easily
found,
that's
why
we
have
to
do
these
code
walkthroughs,
so
Scylla
growing
projects
everything's
in
github
and
it's
hard
to
expose
things
and
get
up
we're
finding.
A
A
So
there
are
groups
that
we
create
to
help
manage
that,
but
there
are
reviewers
and
approvers
generally
speaking
right.
So
if
you
push
your
first
PR-
and
you
say-
hey
I
want
to
make
this
change
to
a
bi
code,
a
reviewer
for
that
organizational
unit
will
have
to
come
in
and
say
hey.
This
looks
good
to
me.
I
often
pass
all
the
CI
checks.
A
So,
but
when
you
put
into
PR
the
manures
I
have
to
come
along
once
it's
reviewed.
It
then
requests
an
approver
like
automatically.
We
have
bots
that
you
know
handle
this
for
us
because
we
believe
in
automation.
So
once
an
approver
comes
along
the
PR
gets
approved
and
off
it
goes.
The
CI
it'll
eventually
get
pushed
out
of
the
real
world
in
the
next
build
and
release
so
yeah
like
you're,
just
a
few
steps
away
from
having
code
committed
to
the
kubernetes
codebase,
not
like
a
big
leap
to
become
a
contributor.
It
might
seem.
A
A
C
A
A
So
all
the
documentation
actually
lives
in
a
repo
that
generates
the
website.
So
if
you
get
a
PR
approved
here,
it's
gonna
be
live
for
everybody
to
see
pretty
quick.
The
website
gets
build
super
fast,
hosted
on
net
laughs
I.
So
thank
you.
Net
will
fine,
but
there's
also
read
meets
for
various
languages,
and
this
is
where
we
need
a
lot
of
help
to.
If
you
speak
a
foreign
language
and
you
see
like
a
grammatical
error
or
something
like
that
and
you're,
you
know
one
of
your
native
tongues.
Please
help
if
you.
A
A
Your
people,
sig
Docs,
super
easy
way
to
a
get
started
on
kubernetes
community
and
be
kind
of
learn
your
way
around
how
things
are
done
so
when
everybody
says
start
with
Docs
seriously
like
if
you
find
a
typo,
that's
a
good
repo
like
that's
a
good
change,
commit
that
submit
a
PR
it'll,
walk
you
through
the
whole
process,
including
how
to
build
the
site
and
test
it
locally,
which
is
awesome,
alright
and
then
test
so
test.
Infra
is
relatively
new
right
working
group
test.
Infra
is
this
year,
but
basically
yeah.
A
So
all
so
all
the
fun
stuff
right,
like
all
the
CI
everything
that
gets
built.
In
the
background
that
you
don't
see
that
checks
all
your
commits
and
your
issues,
your
pull,
requests
all
that
stuff
and
then
actually
all
the
testing
against
the
various
supported
hardware
and
architectures
all
happens
through
tests,
infra
or
yeah
all
happens
through
testing
for
us,
and
that
is
not
another
KK
right.
A
Marry
Bernays
test
in
for
a
super
fun
group,
if
you're
into
infrastructure
at
all
and
I'm
talking
like
managing
servers,
cpc's
network
stuff,
like
that,
please
join
this
group
I.
Try
to
help
this
group
as
much
as
I
can
because
I
have
ops
experience.
This
group
is
kind
of
like
the
dev
ops
team.
For
now,
like
yes,
re
team
for
the
actual
kubernetes
like
back-end
build
processes.
That's
where
testing
for
lives.
A
It's
a
big
group
because
there's
a
lot
of
people
willing
to
help
which
is
awesome,
but
it
takes
you
through
the
entire
test
process.
There's
all
the
documentation.
You
need
to
know
about
tied
and
prowl
and
all
the
fun
tools
that
are
part
of
our
automation
and
including
all
the
other
various
tools
that
go
into
work
here.
A
So
we
are,
it's
kinda,
you
know,
as
you
saw,
was
pretty
monolithic.
You
know
KK,
we
are
breaking
it
up
right,
like
testing.
First
part
of
that
community
is
part
of
that
breakup
right.
That
was
very
monolithic,
repo.
What
we
want
to
have
happen
is
actual
Cooper
entities
like
API
code
only
living
in
KK.
Everything
else
needs
to
be
kubernetes
slashed
the
thing
or
the
sub
project,
and
that
is
just
so
KK
is
easier
to
manage
right
like
if
you
cloned
it
or
you
forked
it
and
you
cloned
it.
A
Good
question:
where
does
that
CD
come
in?
Where
does
things
like
your
runtimes,
like
Rio,
OC
I
complained,
builds
the
docker
run
time
everything
else?
Where
does
that
all
come
into
play?
That's
all
part
of
that
stage.
So
when
you
start
pulling
in
all
its
you'll,
see
you'll
eventually,
you
like
understand
how
this
kind
of
comes
together
like
you,
do
it
go
get,
and
you
start
pulling
in
all
these
dependencies.
A
That's
where
it
comes
in
when
you're
doing
those
builds
you've
done
that
before
I've,
never
actually
done
like
a
full
compile
to
raise
until
the
day,
No
yeah.
So
it's
like
it's
not
a
very
common
thing
that
people
do
3-ounce
with
you,
but
you
need
to
be
able
to
do
it
if
you
actually
gonna
be
committed
against
KK.
B
A
Other
you
know
working
pieces,
so
in
generally,
it's
generally
speaking
you
to
lots
of
RAM
lots
of
disk
losses
CPU,
so
you
have
to
run
docker
to
make
a
mini
cube
work,
which
is
what
we're
gonna
use
today,
you
could
use
kind.
We
actually
had
a
commit
this
morning,
thanks
to
Tim
hongcun,
to
reach
out
to
bend
the
elder
and
to
make
a
commit
to
make
it
kind
work.
Today
you
need
go
1:13.
Does
everybody
understand,
go
like
how
that
dependency
tree
works?
Go
pass
everything
like
that,
no
ok
cool!
A
We
can
get
into
that
github,
everybody
have
a
github
account.
Everybody
have
SSH
keys
there.
Everybody
have
kubernetes,
forked
and
cloned
pulled
down
to
the
laptop
at
least
no
any
nose.
No,
as
well
now.
C
A
A
B
A
Golang.Org
just
download
it
for
your
OS
Nia.
We
good
to
go
alright,
so
this
is
kind
of
at
your
own
pace.
It
did.
Did
everybody
get
the
slides
in
advance?
Yes,
no!
Maybe
no!
Okay!
Let
me
figure
out
how
to
share
the
slides,
somehow
I
believe
so.
Okay,
so,
oh
sorry,
all
right,
you're
going
to
do
a
number
of
things
here,
follow
the
instructions.
If
you
need
to
copy
and
paste
from
the
slides-
and
you
don't
have
them.
Let
me
know:
I
will
get
you
access
to
them.
A
A
B
C
C
A
The
go
path
you,
okay
go
path
is
a
go
idiom.
Essentially
you
need
to
have
that
environment
variable
set
because
go
I.
Think
defaults
now
to
tilde
Co
for
your
go
path,
but
that
will
be
where
all
the
packages
for
dependencies
all
your
source,
all
the
binaries
everything
will
live
under
your
go
path.
So,
if
you
have
go
installed
and
it's
a
modern
version
of
go,
you
should
maybe
have
a
go
path
already
set
up.
A
If
you
have
installed
go
more
than
I
think
a
year
ago,
it
might
not
be
set
up
by
default,
so
latest
versions
of
go
should
use
a
default
go
path,
so
please
feel
free
to
run
through
these
commands.
If
you
have
issues,
please
raise
your
hand,
yeah
I,
don't
think
the
depth
flag
is
a
good
idea
here.
Sorry.
D
A
A
A
A
A
D
A
D
A
A
D
A
A
A
A
A
A
D
D
D
D
D
D
D
D
D
A
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
A
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
B
B
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
A
All
right,
so
what
does
each
package
do?
You've
got
a
base
image
there.
Dbm,
that's
just
a
a
lightweight
arm.
There
amd64
base
image
for
devian,
you
put
hypercube.
On
top
of
that
hypercube
handles
the
network
layer,
I.
Think
I
forget
iptables
vertical
part
of
all
the
segmentation
functioning
inside
gratis
node.
Oh,
that's
kind
kindest
is
that
Ben's
thing
yeah,
so
that's
kind
kind
is
kubernetes
in
docker.
A
D
A
All
right,
sorry,
better!
Thank
you,
yeah
and
then
Q
cross
I
have
no
idea
what
that
does.
I,
don't
know
what
that
doesn't
build
process,
but
you
need
it
feel,
free
to
google
it
and
tell
me
I'm
open
to
learning
here
at
CD.
Does
everybody
know
what
Etsy
D
is?
Who
does
not
know?
What
sed
is
it's
fine?
If
you
don't
know,
it
is
a
key
value
store.
It
is
essentially
the
state
for
kubernetes
database,
the
so
if
you
lose
at
CD,
you
are
screwed.
A
You've
lost
your
entire
configuration,
so
it's
vitally
important
that
you
back
it
up
and
there's
lots
of
backup
tools
for
kubernetes
out
there.
But
this
is
the
data
store
for
all
the
internal
settings
for
kubernetes,
including
any
number
of
settings.
There
are
very
large,
sed
clusters
running
very
large
crannies
clusters.
Right
now,.
A
A
So
what
does
this
tell
us?
This
is
a
large
project
right,
there's
lots
of
dependencies
because
there's
so
many
letters
of
retraction,
that
is
the
joy
of
kubernetes
old
version
coming
right
up
now.
Folks,
listen
I
am
opening
an
old
version
to
find
the
old
URLs
do
not
use
this
unless
you
are
connected
remotely.
A
Against
we're
done,
Kate's,
not
down
yeah
harbour
case
dev
is
the
external
name.
There
is
an
internal
server
setup
in
the
room,
next
door
running
harbour
to
pull
down
the
images.
This
is
where
you
get
them
from
on
the
internet,
but
all
the
version
numbers
are
wrong,
so
just
swap
out
the
domain
names
and
you're
good.
So,
instead
of
whatever
is
go,
harbor
or
contributor
go
Harvard
at
I/o,
it
is
Harvard
Kate's,
dev.