►
Description
[RI] Who wants swag?
Ram to get in touch with folks on Slack with a coupon code for ordering swag
[GC] Tutorials
Usage of deploy-on-kind.sh?
Production?
Link from README? - Check back in early March.
[KB] Kpack caching and app / image relationship
A
A
A
C
A
E
D
A
F
So
I
have
a
coupon
code
that
folks
can
use.
It
should
knock
off
the
cost
of
the
swag
bundle,
as
well
as
shipping,
at
least
the
basic
stuff.
That's
what
I
tested
so
I'll
get
in
touch
with
the
folks
on
Slack,
or
you
can
ping
me
whenever
you
have
a
minute
and
I
think
the
URL
is
pretty
clear,
store.lotfoundry.org
and
then
there's
like
a
code
that
you
can
use
for
the
big
fat
discount.
So.
A
G
Yeah,
so
this
went
up
I
think
this
week
and
it
looks
really
nice.
It's
like
a
webpage,
a
really
well
made
webpage
with
tutorials
about
griefy
I,
didn't
know
this
was
happening,
but
it's
fine.
It
looks
really
good
I
think
we
what
I
did
as
soon
as
I
saw
it
is
just
go
through
it
just
to
make
sure
that
we're
not
any
errors.
I
think
I
find
a
little
thing
to
remove
and
it's
already
been
merged.
So
all
good
I
have
a
couple
of
questions
about
that.
G
I
wanted
to
ask
like
the
team
in
general
about
the
a
couple
of
things
that
are
on
there
that
could
potentially
I.
Don't
know
that
we
might.
We
might
not
agree
on
like,
for
example,
the
tutorial
about
local
install
just
and
recommends
people
to
use
Deploy
on
kind,
which
means
I,
guess
lots
of
people
with
lots
of
different
configs
will
try
to
use
deployment
kind
now
if,
as
they
will
find
it
on
the
tutorial.
G
So
how
do
we
feel
about
that?
Because
I
guess
there
has
always
been
a
bit
of
a
fear
that
like
if
we
had
to
support
lots
of
if
we
forgot,
if
we,
if
we're
going
to
make
that
script
like
uninstall
script,
then
it
would.
It
would
become
like
very
expensive
to
maintain,
but
on
the
other
hand
like,
even
if
it's
just
targeted
the
contributors,
we
might
still
get
contributors
with
lots
of
different
configurations
and
lots
of
different
noises
and
stuff.
G
So
we
we
might
still
have
to
you
know,
spend
that
effort
to
make
sure
that
it
runs
on
everyone's
machine.
So
it's
probably
fine,
but
I
still
wanted
to
check
with
that
and
then
there's
a
paragraph
about
production
that
pretty
much
says
it's
not
production
already,
but
you
might
still
want
to
try
it.
It's
like
very
cautiously
worth
it,
but
I
wanted
to
check
with
people
about
what
they
think
about
it
other
than
that.
F
So
just
a
little
background
on
that
Giuseppe,
so
the
cloud
Foundry
Foundation
works
with
Steve
Greenberg
he's
part
of
this
organization
called
r
scale,
and
they
did
a
lot
of
work
with
the
cloud.gov
folks
about
adopting
Cloud
Foundry,
and
things
like
that.
So
one
of
the
things
that
they've
historically
been
doing
is
creating
tutorials
for
all
our
projects,
and
so
this
effort
stems
from
that
connection.
So
it.
F
As
a
first
release,
you
know
just
for
something
that
can
live
on
the
cloud
Foundry
website
itself,
alongside
some
of
the
older
stuff
that
they've
done
about
Cloud
Foundry
on
VMS,
and
they
also
had
like
a
category
tutorial
for
cloud
Foundry.
So
I
think
it's
now
migrated
to
killer
Coda,
whatever
the
replacement
is.
But
the
effort
is
basically
out
of
a
long-standing
relationship
that
the
foundation
has
had
with
and
Steve,
and
you
know
ask
him
for
what
it's
worth.
F
So
that's
the
background
in
which
in
which
this
was
created,
there's
probably
going
to
be
tutorials
on
other
projects
too.
That
we'll
add
to
that.
But
yeah.
We
just
thought
get
something
very
basic
going
for
query
fee
and
then
sort
of
open
it
up
to
the
larger
Community
for
feedback,
and
things
like
that.
F
G
Yeah,
that's
why
I
wanted
to
to
raise
the
issue
so
that
if
anyone
like
I
would
encourage
everyone
in
in
the
group
to
just
have
a
quick,
read,
it's
not
much
stuff
and
see
if
there,
if
you
feel
like
everything,
resonates
and
if
there's
anything
you
want
to
fix,
it's
there's
a
there's,
a
git
repository
connected
to
it.
So
you
can
just
PR
fixes
straight
away
and
yeah.
Maybe
I
don't
know
like
what
does
it
mean
to
officially
given
its
life
like?
F
Now
we
can.
We
can
have
that
released
and
by
released
I
mean
open
it
up
to
the
cloud
Foundry
Community
put
it
on
social
media,
put
it
on
our
blog.
What
have
you
so
just
maybe
write
a
byline
or
two
and
have
those
published
in
the
meantime,
so
we've
not
posted
about
it
anywhere.
So
that's
really
what
I
mean
by
a
release
more
than
anything.
G
F
Foundry
has
not
been
known
for
its
lightweight
releases,
so
if
somebody
wanted
to
try
it
on
their
laptop
first
before
you
know
actually
pushing
it
on
a
cloud
provider
somewhere,
Cloud
Foundry
has
never
been
able
to
do
that
at
least
not
popularly
one
of
the
changes
that
we're
kind
of
I
must
say
proud
of
with
karifi
is
that
you
know
it's
possible
to
try
it
on
a
laptop
before
you.
Do
it
anywhere
else.
F
F
Low
barrier
to
entry
and
something
that
people
can
use
where
you
know
they're,
probably
really
just
kicking
the
tires
around.
So
that's
the
big
win
in
my
opinion
for
the
usage
of
deploy
unkind.
But
if
you
really
feel
that
it
might,
you
know,
end
up
being
more
trouble
than
it's
worth
to
write
and
maintain.
Then
we
could
think
of
ways
around
it.
To
be
honest,.
G
Yeah,
as
I
said,
like
we
I,
don't
think
we
can
ever
assume
that
it's
only
going
to
be
used
by
just
people
who
work
on
it
on
the
day
by
day,
because
it's
going
to
be
used
by
anyone
who
wants
to
contribute
and
it
will
need
like
they'll
need
anyone
wants
to
contribute,
will
need
to
use
it
in
one
way
or
the
other.
So
some
effort
to
make
it
run
on
a
relatively
wide
range
of
configurations
is
needed
anyway.
G
I
would
say
we
one
thing
we
could
do
is
maybe
look
at
how
expensive
it
becomes
like
in
now
that
it's
been
put
into
tutorials
Etc
and
if
we
feel
like
it's
too
expensive,
we
might
want
to
restrict
like
basically
give
it
stricter
record.
At
the
moment
the
requirements
are
like.
Oh,
if
you
have
kind
running
it
should
run,
we
might
think
about.
I,
don't
know,
require
certain
versions
of
bash
or
certain
versions
of
you
know
the
other
dependencies
if
we
feel
like
it
becomes
too
expensive
until
then,
I
wouldn't
worry
too
much.
G
If
we
start
getting
12
PRS
a
week
about
people
trying
to
make
it
work
on
all
sorts
of
environments
that
it's
like
no,
this
is
too
much.
We
need
to
make
it
easy,
but
until
then
we've
got
one
and
we've
merged
it
and
is
kind
of
fine.
So
maybe
we
shouldn't
worry
about
it
until
the
problem.
Actually,
you
know
surfaces.
B
I
think
that,
having
such
a
script
that
installs
everything
and
provided
that
it
works,
at
least
for
our
workstations,
is
a
great
living
documentation
on
how
to
install
curriculum
kind,
I
mean
even
if
it
fell.
First,
on
your
specific
environment,
you
can
figure
out
what
to
do
instead
of
just
reading
some
outdated
talks
that
are
not
relevant
anymore.
B
G
Yeah
because
they
have
installation
you,
the
other
thing
is
this
installs
main
right:
it
just
tells
the
head
of
the
Repository,
which
is
also
something
that
maybe
it's
like.
If
you
just
want
to
play
with
it,
it
would
be
nice
to
just
install
latest
release,
but
this
installs
main,
which
might
be
broken
for
who
knows,
which
reason
and
I
don't
think
we
want
to
script
out
there,
or
maybe
we
do
I,
don't
know
it
kind
of
the
the
plan
kind.
G
D
Yeah
and
to
add
on
to
it
Danny
said,
like
I,
think,
since
the
scope
to
kind,
we
won't
have
the
issues
we
have
with
some
of
the
CF
for
kids
to
play.
Scripts,
which
were
like
meant
to
be
run
against
an
arbitrary
is
and
like
the
surface
area
was
just
so
huge
there
like
I,
I
I,
don't
see
a
huge
problem
with
with
people
using
it.
G
H
G
Yeah,
but
also
yeah,
but
also
that's
true,
but
the
easiest
way
to
just
you
know
without
needing
without
the
need
to
change
the
script
at
all.
It's
just
in
the
tutorials
tell
people
you
know
list
tags
pick
up.
The
latest
check
like
switch
to
that
one
and
then
run
the
player
on
kind.
That
kind
of
guarantees
that
you're
installing
a
released
version
which
is
supposed
to
work.
H
D
D
Yeah
I
I
think
I
think
what's
in
the
tutorial
is
actually
Okay
and
like,
like
I,
saw
like
we
had
one
contribution
where
someone
like
changed
a
couple
of
commands,
so
it
worked
with
their
like
older
version
of
bash
and,
like
that's
fine
like
it
wasn't
like
a,
they
were
like
just
like
yelling
at
us
that
was
broken
or
anything
they
took
it
on
them
to
fix
it.
So
I,
don't
know
it.
I
feel
like
if
that's
the
type
of
Engagement
we're
just
like
every
now
and
then
stuff
like
that.
A
F
F
There's
other
answers
that
we
could,
you
know,
potentially
create
where
we
say
we
have
like
a
bunch
of
things
on
our
roadmap,
which
we
imagine
will
make
it
more
suitable
for
production
or
something
like
that,
or
obviously,
there's
always
the
option
of
completely
removing
that
a
particular
item
from
the
FAQ.
So
any.
B
A
F
Yeah
I
mean
to
me
it
feels
like
we
can
definitely
link
from
the
readme
as
soon
as
all
of
the
open
PRS
that
we
have
right
now
are
closed,
and
you
know
we
don't
have
any
urgent
ones
that
are
being
opened
at
that
point
of
time.
So
I'd
imagine
checking
back
in
on
like
the
1st
of
March
and
just
linking
it
to
the
real
name.
E
So
yeah
at
the
moment
it
seems
kpac
image
has
a
cash
field
and
you
can
choose
to
either
make
it
create
a
PVC
for
the
cache
or
you
can
specify
a
registry
tag.
So
it'll
go
and
store
an
image
somewhere
in
a
registry
we
played
around
and
we
stuck
a
image
tag
that
was
using
the
app
good
in
the
kpac
image.
So
every
push
from
a
particular
app
would
use
the
same
image,
cache
and
yeah.
E
So
an
image
has
only
ever
used
one
build.
So
the
cache
is
irrelevant
at
the
moment
and
I
know
people
talked
about
kpac
getting
things
from
the
registry
and
how,
when
we
had
one
droplet
tag
per
app,
it
should
help
with
caching
and
I'm.
Not
it
doesn't
seem
to
work
that
way,
but
maybe
somebody
could
help.
D
D
D
Yeah
I,
don't
remember
why
we
didn't
do
that
like
that
was
suggested
of
something
we
could
do
when
we
start
doing
the
kpac,
Builder
and
I
think
it
was
I.
Think
it's
like
very
simple
to
think
of
it
as
one
image
per
per
build
workload,
but
like
I
I,
don't
know
it
might
be
worth
poking
on
that
a
bit
harder
and
see
why
we
can't
share.
E
E
D
D
Yeah
I
think
I
think
the
thing
we
need
to
do
is
make
it
so
that
you
can't
spawn
simultaneous
builds
like
you.
There
should
only
be
one
running
at
once:
I
I
think
that
is
like
some
of
the
the
complexity
there,
because
if
you
like,
create
like
three
builds
at
the
same
time,
they're
all
gonna
like
try
to
update
that
kpac
image
and
it's
unclear
which
one
actually
wins
out
and
stuff,
but
I
feel
like
there
should
be
ways
to
limit
it
and
I
I.