►
From YouTube: Pinniped Community Meeting - October 7, 2021
Description
Pinniped Community Meeting - October 7, 2021
We meet every 1st and 3rd Thursday of the month at 9am PT. We'd love for you to join us live!
This week we discussed Pinniped participating in Hacktoberfest, project roadmap updates, and the Helm chart discussion from Slack. Meeting notes can be found here: https://hackmd.io/rd_kVJhjQfOvfAWzK8A3tQ?both#October-7-2021-Agenda
A
A
If
you're
watching
this
from
home,
we
would
encourage
you
to
come
and
join
us
live
we
meet
every
first
and
third
thursday
of
the
month
at
9
a.m.
Pacific
time
it's
a
good
opportunity
for
you
to
meet
the
maintainers,
hear
what
we're
working
on
provide
feedback
and
ask
any
questions
that
you
may
have
on
using
pinniped
you're
also
welcome
just
to
sit
and
listen
in
silence.
A
A
And
next
we
also
are
wanting
you
to
put
down
your
name
in
any
organization
that
you
represent
when
you
attend
these
meetings.
It
just
helps
us
keep
track
of
who,
from
outside
of
the
maintainers
is
joining,
and
we
want
to
keep
the
discussions
open
and
just
kind
of
learn
more
about
who
is
using,
pin
ipad.
A
A
Next
up
we
have
some
announcements,
just
a
reminder
that
pinniped
has
a
few
talks
surrounding
kubecon
and
cloudnaticon.
Next
week
we
have
the
one
that's
on
friday
october
15th
at
2,
30
p.m,
pacific
time
your
you
can
watch
it
either
virtually
or
if
you're
attending
in
person
you
can
watch
it
then
as
well.
B
C
A
Yeah
75
bucks
to
attend
virtually
and
then,
if
you
want
to
attend
in
person,
there's
a
few
rates
here,
if
you're
an
individual
that
doesn't
work
for
a
company
that
is
paying
for
your
way,
then
it's
700
academic,
if
you're
a
student,
150
bucks
and
then,
if
you're
you
know
attending
on
behalf
of
a
company
that
is
paying
for
your
your
ride.
It's
1550
bucks.
A
D
D
A
C
D
A
A
C
C
C
I
did
some
searching
through
our
slack
channel
for
the
string
helm
to
find
all
the
other
people
in
the
past
that
have
mentioned
it
in
some
capacity
and
I
sort
of
cc
been
on
there.
I
think
that
puts
us
at
least
five
people
within
our
community
that
have
either
written
their
own
home,
charts
or
requested
that
we
have
a
helm
chart
and
in
in
that
slack
thread
there
are
at
least
two
examples.
So
two
separate
individuals
have
written
their
home
charts
and
posted
them
online
somewhere.
C
Well,
it
makes
it
near
technically
impossible
for
someone
to
make
a
pr
that
actually
is
tested,
certainly
make
a
pr
that
they
have
tested
locally,
but
they
can't
make
that
vr
that's
tested
in
our
pipelines.
So
that's
a
little
that's
a
little.
It
wouldn't
be
good,
wouldn't
sort
of
match
the
rest
of
the
project.
C
C
C
C
We
could
maybe
have
something
like
have
a
ci
flow.
That's
like
adds
on
to
our
current
ci
flow,
but
it's
like
based
off
of
github
actions
so
that
the
cines
of
it
lives
in
the
main
repo,
and
thus
you
could
make
a
pr
and
also
update
that
ci
thing
and
thus
also
get
validated,
and
thus
it
will
meet
the
requirements
that
you
need
to
test
stuff
that
you
put
in
this
project.
C
It
would
be
kind
of
weird
because
then
we'd
have
like
two
ci
systems,
or
maybe
it's
not
that
big
of
a
deal
because
it'll
just
be
like
some
ammo
or
whatever
jacob
actions,
users,
you
know,
but
yeah
those
those
are
sort
of.
I
think
the
high
level
thoughts
I
had
I
I
do.
I
do
get
the
sense
that
there
is
a
need
and
desire
for
this
to
exist.
You
know
people
are
willing
to
go,
write
their
own
and
sort
of
suffer
through
it.
D
Hard
for
me
to
estimate
exactly
what
that
support
burden
would
be
like
if
we
just
said
you
know,
picked
a
bullet
and
said:
hey
we're
going
to
actually
fully
support
this
and
we're
going
to
have
all
these
tests.
I
think
it's
it's
its
own
kind
of
different
syntax
from
deep
ctl
or
ytt.
So
we
need
to
kind
of
understand
that
third
way
of
writing
everything
and
continually
update
it
when,
if
it
changes
or
when
helm,
changes.
C
Yeah,
the
the
the
only
thing
that
sort
of
made
me
vaguely
even
considered
like
you
have
access
things
was
the
fact
that
today,
with
cube
ctl,
we're
kind
of
we
cheat
a
little
bit
because
we
say:
hey
we're
just
going
to
render
the
defaults
with
ypt
and
just
tell
qtl
to
apply
it,
but
we
don't.
We
don't
do
any
validation
of
any
tweaking
of
that
yammer
with
tipsy
tail
we
just
kind
of-
and
I
think
that's
fine.
I
don't
think
that's
a
big
deal.
C
We
want
to
replicate
that
in
helm,
not
really
sure
how
we
validate
that
any
of
that
works
yeah.
We
would
run
it
and
hope
it
doesn't
immediately
crash,
but
you
know
you
could
you
could
forget
to
wire
the
replicas
and
it
would
not
crash
right
like
so.
It
would
run
with
whatever
number
of
rep,
because
probably
one
or
something
so
I
have
concerns
there
because
we're
not
home
users
right
like
I
don't
I
don't
have
anything
for
or
against
how
I'm
just
in
the
sourcing
way.
C
F
F
F
F
Maybe
it's,
maybe
that's
not
a
concern
anymore.
The
concern
would
be.
Can
we
come
up
with
a
way
to
make
sure
that
if
we
do
an
official
helm
chart
that
it
stays
kind
of
in
sync,
with
our
ytt
manifest
that
you
know
all
the
knobs
that
we
offer
on
itt
release
the
ones
that
we
care
to
offer
and
how
we
offer
them
and
they
work
correctly,
meaning
that
they
render
the
right
yaml
at
the
end
of
the
day
correctly.
F
So
I
wonder
if
we
can
write
some
kind
of
if
we
do
want
to
support
home,
because
it
does
seem
like
there
is
some
signal
from
the
community
that
we
didn't
have
before
that
people
are
interested.
But
you
know
more
than
just
one
person
like
quite
a
few
people
for
us,
at
least
in
the
scale
of
our
community.
F
Fine.
I
guess
we
want
to
do
the
same
thing
with
home
and
for
context
for
people
watching
the
video
normally
in
ci
we
deploy
with
cap,
which
is
one
of
the
carvel
tools
for
deployment
similar
to
group
cuddle,
but
has
some
nice
fancy
options?
What
margaret
did
recently
was
make
sure
we're
also
testing
what
is
google.
F
F
F
Idea,
scott,
you
may
or
may
not
be
surprised
to
know
that
we
don't
really
know
the
bitnami
folks,
even
though
we're
at
the
same
company,
it's
a
big
big
company,
although
we've
interacted
with
them
a
little
bit
like
I've,
submitted
a
pull
request
against
one
of
their
container
images,
but
I
think
a
lot
of
them
are
based
in
europe.
So
there's
a
time
zone
challenge.
I
think
that's
a
good
idea,
something
we
could.
We
could
reach
out
to
that
team.
B
I
mean
I
can
also,
I
know
a
lot
of
the
charts
are
added
there
just
from
issues
on
their
github
of
whatever
of
you
know,
requesting
a
chart.
I
think
it
may
be
a
way
to
start
is
just
by
having
a
community
thread.
I
can
open
up
an
issue
there
even
and
then
we
can
whatever
just
add
that
into
the
slack
thread
and
have
anyone
that's
interested
in
it
ping
there
as
well
on
the
issue
and
maybe
through
community
request.
It
may
also
happen
through
the
vietnamese.
F
Thanks
scott,
that
actually
kind
of
makes
me
think
of
one
more
small
thing,
which
is
somebody
volunteered
to
do
the
work
and,
as
mo
pointed
out,
we
aren't
set
up
yet
for
that
person
to
do
the
ci
work,
but
we
could,
potentially,
you
know,
think
about
some.
What
what
would
our
requirements
be
if
we
wanted
to
do
our
own
helm
charts
like?
Would
our
requirement
be
that
we
specif
that
we
have
exactly
the
same
knobs
between
ytt
and
home,
for
example?
Or
could
we
drop
some,
but
whatever
our
requirements
are?
F
If
we
shared
them
with
that
person,
maybe
they
would
want
to
do
the
work
and
then
we
would
just
have
to
figure
out.
How
do
we
accept
that
work
like
how?
How
do
we
add
it
to
ci?
How
do
we
make
sure
we
feel
that
we
can
test
it
and
make
it
going
forward
because
they'll
do
the
initial
work,
but
that's
no
promise
that
they'll
come
back
and
keep
it
maintained
to
every
time
you
make
a
change.
That'll
be
nice.
C
All
right,
so,
if
I
understand
the
suggestion
ryan,
it
would
be
that
if
we
can
nail
down
the
set
of
requirements
for
the
for
lack
of
a
better
term
for
the
production
side
of
the
helm
chart,
we
we
could
directly
have
a
community
member
do
that
work.
And
then
we
would
take
the
non-production
site,
the
maintenance
burden
and
the
ci
style
stuff,
because
that's
sort
of
still
in
our
area
of
influence
and
control.
Right
now,.
F
It
sounds
like
we
have
a
few
different
avenues
to
explore
right
scott
had
to
get
some
folks
and
see
if
they'd
be
interested
in
maintaining
such
a
thing.
We
had
to
explore
trying
to
guide
someone
from
the
community
who's
interested
in
contributing
it
so
that
we
can
work
with
them
to
do
the
testing
part
explore.
Do
it
all
ourselves,
it
might
not
be
that
hard,
just
adding
the
additional
maintenance
burden.
That's
the
initial
work
might
not
be
very
much.
F
E
A
B
Yeah
I'll
open
up
a
issue
there
and
then
also
send
the
link
to
the
issue
in
the
slack
conversation
so
that
people
can
comment
there
and
you
know
thumbs
up
the
issue
so
that
they
get
some
traffic
traction
on
that.
And
I
know
that
there
have
been
a
few
that
have
been
added
into
vietnam
explorer
where
they
say.
We
can't
do
the
initial
leg
room,
but
we
will
maintain
it
after
so
that
baby
also
away
for
the
community
member
who
said
that
he
would
be
willing.
F
B
That
initial
work
would
be
possibly
you
know
the
you
guys
sitting
down
with
him
deciding
what
those
requirements
would
be
of
that
helm
chart.
He
could
do
the
initial
work
create
a
pr
for
them
if
they're
willing
to
through
the
issue
through
the
conversation
there,
and
then
you
know
they
can
maintain
it
from
that
point.
C
C
B
C
B
B
F
B
If
this
happens
in
the
documentation
of
pinniped-
and
you
know
at
that
point
people-
you
know
just
go
to
vietnam,
if
there's
an
issue
with
the
chart,
so
I
think
that's
definitely.
I
think
it
would
be
cool
to
have,
because
that
also
means
to
get
that
into
cube
app
and
things
like
that
which
people
then
have
a
ui
to
deploy
it
into
their
clusters,
and
can
you
know,
do
some
special
things
in
that
case
as
well,
so
it
adds
some.
F
A
All
right
so
yeah,
thank
you,
everyone
for
today's
community
meeting.
Thank
you,
scott,
for
your
participation.
As
always,
and
all
your
help,
we
really
appreciate
you
and,
if
you're
watching
this
from
home
again,
we
would
love
to
have
you
join
us,
live
and
learn
more
about
you
and
your
usage
of
pinniped
and
hopefully
you'll
become
an
active
member
of
our
community.