►
From YouTube: Extending kubectl with plugins and krew
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
Okay,
thank
you.
Everyone
for
joining
us
today
welcome
to
today's
cncf
live
webinar,
extending
cubectl
with
plugins
and
crew,
I'm
libby
schultz
and
I'll
be
moderating.
Today's
webinar
I'm
going
to
read
our
code
of
conduct
and
then
hand
over
to
james
sterdamont,
principal
sde
at
microsoft,
a
few
housekeeping
items
before
we
get
started
during
the
webinar.
A
You
are
not
able
to
speak
as
an
attendee,
but
you
are
welcome
to
pop
any
questions
into
the
chat
box
on
the
right
hand,
side
of
your
screen,
please
feel
free
to
post
everything
there
and
we
will
get
to
as
many
questions
as
we
can.
At
the
end.
This
is
an
official
webinar
of
the
cncf
and,
as
such
is
subject
to
the
cncf
code
of
conduct.
A
Please
do
not
add
anything
to
the
chat
or
questions
that
would
be
in
violation
of
that
code
of
conduct
and
please
basically
be
respectful
of
all
of
your
fellow
participants
and
presenters.
Please
also
note
that
recordings
and
slides
will
be
posted
later
today
to
the
cncf
online
programs
page
at
community.cncf.io,
under
online
programs.
A
B
Cool,
so
the
agenda
today
is
to
go
through
cube,
ctl
plugins,
just
an
introduction
to
what
they
are
and
then
we'll
talk
a
little
bit
about
crew,
which
is
kind
of
the
way
to
distribute
your
plugins
and
then
we're
gonna
dive
into.
How
do
we
develop
one
and
in
publishing
them
so
we'll
go
through
all
that
and
ask
questions
as
we
go
along
and
we'll
either
be
able
to
answer
them
as
we
go
or
at
the
end
of
the
session.
B
We
do
a
lot
of
work
in
kubernetes
and
all
the
related
sigs,
I'm
also
a
lead
for
sig
windows,
and
I
guess
the
reason
I'm
here
today
is:
I
created
a
windows,
debug
crew
plugin
recently
and
showed
it
to
some
folks
and
they
thought
it
was
cool
and
wanted
to
know
how
to
develop
their
own
plugins
and
so
hopefully
can
lay
those
lay
that
groundwork
for
you
and.
A
B
You
know
related
to
my
twitter
handle
down
in
the
bottom.
There
is,
I
can
create
fire
six
different
ways
with
using
only
sticks
and
stones.
B
You
can
reach
out
to
me
on
twitter
and
you
can
chat
about
a
little
bit
about
what
that
what
that
means
so
cube
ctl.
I'm
gonna
take
a
little
bit
of
an
assumption
here
that
folks
are
pretty
familiar
with
cube
ctl.
It's
the
command
line
tool
for
interacting
with
your
cluster,
your
kubernetes
cluster.
B
B
The
thing
that
you
may
not
know
is
that
you
can
do
a
lot
more
with
it
that
doesn't
come
right
out
of
the
box,
and
so
here
I'm
showing
another
tool,
there's
a
link
to
it
down
at
the
bottom
here,
but
this
actually
lists
all
of
the
our
back
rules
for
a
given
type
of
resource
and
prints
it
out
in
this
nice.
B
Fancy
list
shows
you
exactly
who
has
access
and
and
what
kind
of
access
they
do
have,
and
this
is
this
isn't
built
into
cubectl
out
of
the
box,
but
it's
you
can
add
it
as
a
plugin.
B
Another
cool
example
of
this
is
a
plugin
called
sniff
and
you
can
point
it
at
a
particular
pod
in
your
cluster
and
it
will
take
care
of
wiring
up
all
of
the
different
components.
It
will
run
the
tools
to
be
able
to
look
at
all
the
network,
traffic
and.
A
B
It'll
even
launch
wireshark
for
you
and
stream
the
live
traffic
into
wireshark,
so
so
this
is
a
really
cool
extension
for
using
cubectl,
and
when
I
saw
this
I
was
like
this
is
awesome.
I
need
to
be
able
to
create
something,
that's
as
cool
as
this.
So
hopefully.
B
So
what
is
a
cube,
ctl
plugin?
This
is
from
the
cube,
ct
whole
documentation
if
you
think
of
cube
ctl
as
the
command
tool
for
like
the
essential
building
blocks
of
interacting
with
the
kubernetes
cluster.
The
plugins
are
ways
of
interacting
with
the
those
building
blocks
in
the
kubernetes
cluster
in
a
much
more
complex
way,
as
you
just
saw,
we
were
able
to
connect
to
a
pod
stream.
The
live
traffic
running
on
on
that
pod
to
wireshark.
B
That's
a
much
more
complex
scenario
than
you
know,
cube
c
table
set
out
to
so
solve,
but
we
can
integrate
directly
into
it
and
and
make
that
part
of
our
development,
workflow
and
so
plugins
would
essentially
extend
the
cube
ctl
with
new
sub
commands,
which
allow
for
new
and
custom
features
that
aren't
part
of
the
initial
cube
ctl
distribution,
and
so
I
pulled
that
from
the
docs
that
there's
quite
a
bit
of
really
interesting,
well
written
docs
out
there
that
you
should
go
check
out.
B
If
you
are
interested
in
this
type
of
thing,
does
anybody
out
there?
Maybe
you
can
drop
it
in
the
chat
here,
but
is
anybody
out
there
using
any
interesting
plugins
that
they'd
like
to
share
with
the
with
the
team
with
with
everybody
here.
B
Keeps
details
free,
okay,
I
don't
know
about
that.
One,
but
I'll
have
to
look
it
up
afterwards.
It'll
be
interesting.
B
So
what
makes
up
a
cube,
ctl
plug-in,
it
is
literally,
very
simple:
it's
a
standalone
binary
that
begins
with
cube
ctl,
and
so
here's
a
couple
examples.
The
one
that
I
I
developed.
I
named
it.
Qctl
windows,
debug,
there's
another
tool
called
neat,
and
so
it's
just
cube.
Ctl
neat.
B
Once
you
have
the
binary
named
that
you
move
it
onto
your
path
and
it
can
be
anywhere
on
your
path
that
you
want
to
be
as
long
as
it's
accessible
and
and
then
it
can
be
written
in
any
language,
so
it
doesn't
have
to
be
written.
Go
it
could
be
written
in
bash.
It
could
be
written
in
rust.
Just
depends
on
on
what
you
feel
comfortable.
Writing
that
plugin.
Once
it's
on
your
path,
you
can
start
to
use
it.
B
So
it's
it's
pretty
simple
mechanism
here
to
be
able
to
extend
cube,
ctl
but
very
powerful,
as
you
saw.
B
So
you
can
install
a
plug-in
by
you
know,
just
taking
the
the
binary
and
copying
it
to
anywhere
in
your
path.
It
doesn't
have
to
be
this
particular
location
here,
but
it
does
have
to,
as
I
mentioned,
have
to
start
with
that
cube
ctl
component.
There.
B
There
you
can
list
all
of
the
various
plugins
that
are
on
your
system,
that
cube
ctl
is
aware
of
it
will
iterate
through
your
path
and
list
anything
that
starts
with
cube
ctl,
and
so
here
let's
say
this
is
compatible
plugins
and
then
once
it's
on
your
path,
you
can
use
it.
So
this
this
one
is
a
little
extension.
I
wrote
for
cluster
api
for
azure,
it's
a
little
bash
script.
B
That
lets
me
connect
to
the
any
node
over
ssh
uses,
the
ssh
key
that
I
have
on
my
my
tool
and
when.
B
Was
having
a
lot
of
trouble
connecting
to
the
nodes?
B
We
do
a
lot
of
the
infrastructure
and
so
the
the
nodes
wouldn't
necessarily
come
online,
because
I
I
messed
something
up
when
I
was
developing
and
so
but
ssh
was
usually
available
and
so
knowing
what
the
ip
address
of
the
node
was
and
and
all
those
types
of
things
was
just
a
lot
of
work.
And
so
now
I
can
just
say,
cube
ctl
capsi
sh
and
the
name
of
the
capsi
crd
and
I
was
connected
to
the
node.
B
So
I
I
kind
of
simplified
my
workflow
by
by
writing
a
little
bash
script
and
then
and
dropping
it
into
the
binary.
And
so
this
is
a
a
great
way,
and
hopefully
it
can
inspire
you
to
kind
of
simplify
your
workflow
in
some
way
and
so.
A
B
Saw
a
question
from
somebody
in
the
chat
there
said:
is
there
a
central
place
platform
marketplace
for
third-party
plugins?
That's
actually
my
next
topic
here.
So
obviously,
if,
if
you
have
it
in
your
repository,
it's
maybe
available
to
your
developers
but
being
able
to
share
it
out
to
the
wider
world,
that's
what
crew
is
trying
to
solve,
so
you
can
think
of
it
as
the
apt-get
or
npm
for
cubectl
and
there's
over
currently
over
200
plus
plugins
on
there.
B
You
can
find
the
windows
debug
one
if
you're
a
windows
developer
out
there
and
but
there's
just
so
many
out
there.
The
ones
that
I
demoed
earlier
in
the
slides
are
are
also
out
there.
I
would
assume
cube.
Ctl
tree
is
available
through
crew.
If
it's.
A
B
We
should
should
look
at
trying
to
have
that
there
it
it
helps
the
entire
life
cycle
of
the
plug-in,
so
it.
A
B
Installing
removing
updating
you
can
search
for
all
the
plugins
right
through
the
command
line
and
the
plugins
don't
necessarily
need
to
start
with
cubectl
in
this
case.
So
if
you
developed
some
binary
binary,
I
think
actually,
access
matrix
is
not
doesn't
start
with
cube.
Ctl,
it's
a
different
binary
name
and
crew
will
manage
that
for
you,
so
they
they
copy
it
to
a
local
folder.
With
that
cube,
ctl
specification,
that's
that's
needed
to
become
a
plugin,
and
then
it
also
helps
with
the
distribution.
B
So
you
can
push
it
up
to
the
this
this
chart
here
and
it
helps
through
the
command
line
tools,
be
able
to
pull
it
pull
all
that
down.
B
So
it
looks
slightly
different
when,
when
you're,
when
you're
interacting
with
crew,
before
we
start
you
just
kind
of
to
install
it,
you
would
copy
the
binary
into
your
onto
a
path
in
sorry
into
a
folder
on
your
path
and
with
cube
ctl.
We
can
search
for
anything
we
want
by
any
kind
of
command.
It
does
a
fuzzy
search
and
comes
back.
So
here
I
searched
for
windows.
You'll
see
the
windows
debug.
B
A
B
Install
it,
I
then
run
cubectl
crew,
install
windows,
debug,
and
it
will
manage
pulling
it
down,
selecting
the
proper
platform
so,
whether
I'm
on
linux
or
windows
or
my
mac
or
whatever
it
is
it'll,
get
those
all
installed
in
the
right
place
and
then
tells
you
how
to
use
it,
and
so
really
nice
interface
for
for
distribution
and
and
consumption
of
these
all
right.
B
B
B
So
first
thing
I
wanted
to
show
here
is
that
first
tool
that
I
sent
so
I
I
haven't
already
installed
the
plug-in
you
can
see.
I've
got
I'm
connected
to
a
cluster.
B
This
is
my
cluster
that
I'm
connected
to
up
here
and
you
can
see
what
I'm
running
is
just
access,
matrix
resource
config
map,
and
so
this
binary
cube
ctl
invokes
it
and
it
goes
out
and
does
a
bunch
of
mapping
across
all
of
the
rbac
rules
and
crds
out
there
and
then
comes
back
and
says
you
know,
here's
who
has
access
and
what
they
can
do
with
those
tools
so
really
really
cool
way.
To
get
more
information
about
your
system.
B
The
next
thing
is,
it
interacts
just
like
any
other
cube,
ctl
tool.
So
there's
you
know
we.
When
I
do
dash
h,
I
get
the
usage,
I
get
various
examples
you
can
see.
I
can
specify
a
different
context
that
I
want
to
use,
and
so
a
lot
of
these
plugins
are
built
to
just
use.
A
B
There
we
go
so.
The
other
thing
I
wanted
to
show
is
that
cute
ttl
sniff,
so
I
have
a
pod
out
there
and
I'm
just
gonna
run
this
on
there.
What.
B
It
will
wire
itself
up
to
the
node
and
then
it
launches
firefox.
Oh
sorry,
it
launches
wireshop
for
me
and
you
can
see
that
I'm
actually
streaming
the
live.
Requests
from
that
pod
right
now,
so
10
2,
2
4
30
is
my
http
bin
binary.
So
getting
that
wired
up
and
getting
the
traffic
stream
to
me
would
have
been.
B
You
know
a
fairly
challenging
situation,
but
with
the
plug-in
it
becomes
very
trivial,
so
I'm
gonna
stop
that
there,
and-
and
so
if
I
look
back
at
the
pods
here-
you'll
see
that
this
this
is
indeed
what's
coming
from
that
pod.
It's
it's
not
from
you
know,
just
my
local
traffic
or
anything
it
was
being
streamed
over
the
top.
B
So
we
can
look
at
the
plugins
that
I
have
so
here
we
can
see.
I've
got
some
crew
plugins
that
we
were
just
looking
at
here's.
Here's
an
example
of
one
that
I've
installed
locally.
I
don't
have
this.
This
is
something
that
you
can
install
from
the
repository
of
cluster
api
for
azure,
but
it's
not
something
that
I've
deployed
into
crew.
So
it's
just
local.
B
B
To
my
system
now,
if
I
do
the
plugin
list,
I
should
see
that
added
there,
and
so
now
I
can
do
cube
ctl
windows
debug,
and
this
will
pick
a
random
node
to
run
it
on.
I
can
also
specify
the
node
I
want
and
I
get
dropped
on
to
the
actual
node
here.
This
is
powered
through
host
process
containers
and
we're
in
beta
right
now,
and
so
there's
this
long
goo
in
here,
but
this
will
eventually
go
away.
B
We're
planning
on
adding
support
for
host
process
containers
in
126.
It's
going
to
go
stable
and
you're
going
to
see
similar
features
here,
but
there's
cool
things
that
that
we're
doing
with
with
that
type
of
stuff.
B
So
when
I'm
using
crew,
I
can
also
use
crew
to
install
these
plugins,
and
so
I
can
kind
of
mix
and
match
here.
But
if
I
use
crew
you
see,
I
get
a
little
bit
nicer
ui.
It
tells
me
what
plugin
is
what
version
I'm
on
and
then
I
also
have
the
ability
to
do
things
like
I'm
searching.
So
here
I
haven't
installed
windows
debug
as
a
as
a
crew.
A
B
And
so
it's
not
showing
it
up
as
installed,
but
oh,
I
could
then
go
ahead
and
install
it
as
a
plug-in
and
it
would
work
so
so.
A
B
Now
it's
installed
and
I
can
use
it
just
the
way
I
just
showed
you
there.
So
that's
kind
of
just
a
quick
demo
of
kind
of
how
these
work
and
how
you
get
started
with
them
and
next
we'll
move
on
to
developing
plugins
again.
Let
me
just
switch
back
here.
B
All
right,
I
think
you
can
see
my
my
slides
again
here,
cool
so
developing
plug-ins.
I
think
the
first
thing
you
need
to
kind
of
address
is:
how
do
you
want
to
develop
it?
Do
you
want
to
develop
the
plug-in
directly
as
a
cube,
ctl
plug-in,
or
do
you
want
to
move
towards
crew
and
I
think,
there's
a
little
bit
of
trade-off
here.
I
think
you
know
developing
the
direct
cube.
Ctl
plugin
can
be
really
quick.
B
It
can
be
a
simple
bash
script
that
you
prefix
the
name
of
the
binary
with
cube
ctl.
That's
what
I
did
with
the
cluster
api
for
azure
script.
It's
something
that
I
you
know
had
a
little
script
on
my
side
and
just
wanted
to
integrate
it
into
cube
ctl.
It
kind
of
just
eases
me
my
developer,
workflow!
B
You
can
keep
it
right
in
your
your
repo,
so
you
don't
have
to
go
through
publishing
and
maintaining
versions
and
all
those
types
of
things
and
it's
super
simple
to
install.
So
those
are
kind
of
like
the
pros
of
that.
I
guess.
If
you
look
at
crew
crew
provides
that
distribution
platform.
It
also
manages
multiple
platforms.
My
batch
script,
it
doesn't
necessarily
work
or
no
like.
I
have
to
tell
different
commands
to
install
it
on
different
systems
with
crew.
A
B
B
It
has
a
wider
audience
because
it's
out
there
as
a
as
a
marketplace
and
then
it
does
have
some
install
metrics
and
then
one
other
thing
I
didn't
list
here
that
I
would
call
out
is
that
crew
also
has
the
ability
to
host
your
own
marketplace.
So
the
one
that
I
was
showing
and
demonstrating
from
is
from
the
public
marketplace.
B
But
if
you
were
an
enterprise-
and
you
wanted
to
give
your
give
access
to
some
of
your
plugins
to
the
developers,
you
could
you
could
host
your
own
so
that
that
way
you
knew
where
those
those
plugins
were
coming
from
and
could
manage
them.
From
that
perspective,.
B
The
next
thing,
when
you
start
to
talk
about
developing
these
is
what
language
would
you
start
in
the
the
bash?
Is
it's
just
one
of
those
really
easy
ones
to
get
started
with?
There's
you
know
no
build
process,
and
so
you
can,
you
can
kind
of
put
together
a
script
really
quickly
the
you.
You
can
write
them
in
any
other
language,
but
the
other
really
well
supported
language
is
go
it.
B
It
comes
with
the
cross
platform,
so
it'll
work
on
all
the
platforms
that
your
your
users
might
be
on.
You
get
access
to
the
cli
runtime.
You
can
also
get
access
to
the
go
library
for
kubernetes.
B
It
can
set
up
configuration
and
then
another
big
one
that
it
provides
is
some
clouds
require
some
additional
support
for
authorization,
and
that
comes
out
of
the
box
with
the
the
go
plug-ins,
and
so
when
you're
choosing
it,
it
probably
depends
on.
You
know:
are
you
going
really
simple
or
you
want
to
make
this
distributed
out
to
the
the
wider
ecosystem.
B
I
I
chose
to
go
with
crew
and
I
think
the
rest
of
the
presentation
is
going
to
be
kind
of
focusing
in
on
crew.
I
think
developing
a
plug-in
in
your
local
repository
is
pretty
straightforward.
B
Developing
for
crew
requires
a
few
extra
components
and
some
of
the
things
that
that
need
to
be
in
that
crew
package
at
the
very
least,
is
a
license
file.
A
read
me
on
how
it
works
and
then
any
of
the
binaries
that
you're
going
to
be
copying,
and
so
you
can
put
this
as
a
tar
file
or
a
zip
file
and
and
host
it
somewhere
and
that
that
becomes
your
crew
package.
That
crew
will
go
and
grab
and
then
drop
onto
the
nodes.
So
at.
B
Are
three
things
that
you
need
to
have
the
the
next
part?
Is
the
crew
manifest?
This
doesn't
go
inside
the
the
package?
It
goes
actually
in
part
of
the
crew.
B
The
crew
index,
which
is
where
everything
is
queried
from,
and
so
this
manifest
is
just
to
be
ammo.
B
You
add
information
like
the
meta
metadata
for
the
name,
the
version
the
home
page
and
then
what
platforms.
So
this
is
how
crew
manages
the
platforms
that
are
that
it
unpacks
for
so
you
can
specify
you
know
if
you
match
this
particular
platform
in
this
architecture,
and
this
is
where
you
go
and
get
the
package
for
that
particular
architecture
and
the
rest
of
it.
Crew
will
handle
and
deploy.
The
crew
does
provide
kind
of
a
templated.
B
Templating
language
and
which
you
can
see
here,
I'm
I'm
using
add
yuri
and
shop,
so
it
will
go
out
and
drop
all
those
binaries
in
there.
It
can
also
drop
in
the
tag
name,
and
so
this
is.
This
is
kind
of
a
template
that
you
use
when
you're
actually
going
and
publishing
your
manifest.
B
The
there
are
some
starter
templates
out
there,
there's
an
unofficial
one
called
crew
plug-in
template,
and
it
will
give
you
that
package
it
sets
up
go
for.
You
has
all
of
the
components
installed.
B
It
has
the
pipelines
for
you
to
enable
to
get
going,
so
you
can
essentially
fork
this
and
then
add
your
own
logic
and
you
can
be
published
and
running
in
crew
running
as
a
crew
pilot
pretty
quickly,
the
other
other
one.
That's
really
useful
is
the
kubernetes
sample
cli
plug-in.
So
this
is
a
example.
Go
lag
plug-in
that
you
can
use
to
get
started
for
the
plugins.
This.
A
B
B
B
There's
more
complicated
ways
to
do
this,
but
essentially
all
I
need
all
I
need
to
have
is
the
tar
file
with
the
license,
the
readme
and
the
binary
that
I'm
interested
in,
and
so
I
I
I
run
some
tests
and
then
I
tar
that
up
and
then
I
can
release
the
package
as
a
particular
file
and
then
I
call
this
crew
release
spot.
B
So
this
is
developed
by
the
crew
maintainers
and
since
99
of
changes
to
your
plugin
are
going
to
be
just
version
bumps
they've,
automated
the
entire
like
deployment
and
updating,
and
so
this
release
bot
will
look
at
that
template
file
that
we
just
reviewed
the
crew
template
file,
fill
it
in
with
all
the
relevant
information
and
and
then
open
up
a
pr
into
the
crew
index,
and
this
is
an
example
of
what
that
pr
looks
like
it
is.
B
So
somebody
ran
the
crew
release
bot.
It
opened
up
a
pr
in
the
crew
index.
I
said
we're
bumping
the
version
to
and
the
maintainer
has
another
bot
whose
verifies
that
it
was
just
the
version
bump
and
then
merges
that
pr
and
then
you
can
now
get
the
update
through
crew
update
whatever
plugin
you're
working
with.
B
B
B
B
So
the
there's
a
few
things
that
I
learned
when
I
was
going
through
this
process.
I
showed
you
the
cube,
ctl
windows
debug
and
it's
three
separate
commands.
B
The
way
that
qctl
plugins
work
is.
If
you
put
a
dash
between
the
commands,
they
become
separate,
commands
in
your
system
and
with
crew.
It
ends
up,
they
convert
those
dashes
to
underscores,
and
so
when
I
install
windows,
debug
without
crew,
I
can
say:
cube
ctl
windows,
debug
and
then.
B
Here,
if
I
install
with
crew,
it's
cube
ctl
windows
dash
debug.
I
didn't
find
this
out
until
after
I'd
already
published
it
and
had
some
folks
started
using
it,
and
so
I
didn't
want
to
have
to
change
the
ux
here.
So
it's
just
something
to
keep
in
mind
when
you're
developing
these
that
they're
they're
gonna
do
that
to
underscore
conversion
the
crew
index
bot
is
or
the
crew
of
the
spot
was
really
super
helpful.
B
I
spent
a
lot
of
time
getting
that
working
initially
and
it
submitted
the
first
pr
and
then
my
pr
immediately
closed.
It
didn't
get
merged
like
we
saw
in
the
previous
slide,
and
what
I
found
out
was
that
you
need
to
actually
generate
that
manifest
by
hand
the
first
time
the
cree
crew
release
bot
has
it's
an
extra
component
that
or
an
extra
flag
that
will
print
it
to
standard
out.
B
The
reason
this
is
done
is
the
crew
maintainers
want
to
make
sure
that
your
description's
good,
they
went
through
a
whole
process
with
me
and
and
said
they
don't
like.
This
should
be
shorter
change.
This
wording
here
that
type
of
thing
that
they
can't
do
through
those
bots,
since
you
don't
own
the
the
pr
itself
and
so
another
just
useful
thing
to
be
aware
of,
and
then
finally,
you
can
test
these
locally
using
the
crew
bot
release
you,
you
can
generate
that
manifest
locally
and
then
cube.
B
Ctl
has
a
download
package
and
use
archive
function,
so
I
can
point
it
at
a
particular
archive
on
a
url
somewhere,
and
I
can
it'll
unpack
that
for
me
it
won't
go
out
to
the
crew
index,
and
so
I
can
overload
that-
and
you
know,
do
do
some
testing
of
the
pre-release
of
the
binary
that
I
was
working
on
and
so
yeah.
Just
a
few
few
items
there
to
be
aware
of.
B
So
I
I
think
that
was
most
of
the
content
that
I
had
prepared,
and
so
I
just
wanted
to
call
out
the
the
docs
for
cube,
ctl
and
plugins
in
general,
the
crew
io,
the
crew
developer
guide
and
then,
if
you're,
looking
for
a
really
simple
example
to
to
get
started
with
my
windows,
debug
crew
solution,
there
is
it's
a
it's
a
one-liner
or
one.
B
You
know
it's
ten
lines
of
bash
script
and
and
a
bunch
of
pipelines
to
automate
deploying
it
to
crew,
and
so
I
hope
this
gives
you
a
quick
overview
of
how
how
to
get
started
with
plugins
and
develop
them,
and
I
hope
you
are
able
to
get
get
started
and
share
your
awesome.
Plugins.
A
Okay,
thanks
so
much
james.
Anyone
else
have
questions,
let's
go
ahead
and
pop
them
into
the
chat,
and
we
can
work
through
any
more
of
those.
B
Any
feedback
to
you,
if
you
had
any
questions
about
anything
else,
to
talk
about.
A
Well,
if
no
one
else
has
any
questions,
I
think
you
know
where
to
find
james,
if
you
think
of
one
post
event
or
curious
in
any
other
cube
ctl
information,
but
other
than
that.
If
no
one
else
has
a
question,
we
can
wrap
things
up
and
let
everybody
let
everybody
go
going
once
going
twice.
B
A
So
much
for
your
presentation
and
for
answering
everyone's
questions.
Thank
you.
Everyone
for
attending
another
cncf
live
webinar,
be
sure
to
catch
us
for
our
live
stream.
Show
tomorrow
at
9am
pacific.
You
can
also
register
through
cncf.io
and
thank
you
everyone
for
joining
us,
so
we'll
see
y'all
again
soon.
Thank
you.
James.