►
Description
[JH] Can we remove/replace the stale link to topic suggestions above in this doc? Done!
[JH/DW] API config validation (issue here)
We don’t currently have any validations of configuration when we load it at startup. Should we? yes!
[GS] Release: What’s Left?
Milestone is almost complete.
Need to trim down service account role (in flight)
Need contributor guide
This is in flight, a pair picked it up yesterday
https://github.com/cloudfoundry/korifi/pull/970
Need installation doc- In flight from Ioannis from S+W
Need to complete the Korifi rename (maybe we still need to rename the domain)
Probably we can leave the domain as-is until we have completed the release. Changing the domains of Concourse and Vault could be disruptive.
Should we fix the cf cli which has a “cf on k8s enabled” setting in the config
This is in the response payload from our API to the CLI. It describes the login flow we use so maybe it is not bad.
[DB] - what will we actually release? Proposal is to release a tarball containing yaml that is deployable to Kind. Container images would live in Docker Hub.
No dissent, so the proposal will be adopted.
Release notes: we aren’t sure what to document here. Probably the release notes will be short.
[JH] Korifi logo: next step?
⛰️ Chris has asked for a few more variations combining different permutations of graphics and fonts & also a seven pointed gear instead of an eight pointed gear.
Onus for actually coordinating voting is on the WG. We can use the same ranked choice algorithm we used for the name. We should wait for the new graphics to appear.
[Ram] Reminder: About the Press Release document
Please feel free to add comments to the document in advance of the meeting. Feel free to reach out to Ram directly via slack also.
Release date? This would be good to firm up for marketing and PR to work against. Even a rough date would be useful. We **might** be technically ready by the end of the week. Friday is a VMware company holiday and also Eastern Orthodox easter weekend.
Marketing + PR might need a couple of weeks to get an announcement out, but engineering doesn’t need to wait to cut a GitHub release. (We can make a draft release and hold it until we are closer to ready for announcement.)
[IT] Maybe choose a date that has historic significance
[Ram] CF CAB call tomorrow: live demo Korifi/cf-on–k8s. Inputs welcome!
This call is getting better traction lately
Ram will do a live install on GKE–Georgi to message Ram with the scripts we use in Concourse to deploy to GKE for PR testing.
A
A
C
A
Presumably,
if
your
configuration
is
terribly
wrong,
bad
things
will
happen
and
your
api
shim
won't
start
up,
but
we
don't
have
a
lot
of
confidence
that
we're
gonna,
give
useful
error
messages
to
people.
So
we
tossed
an
issue
into
the
backlog
to
go,
add
some
validations
and
maybe
make
nice
error
messages.
A
D
Yeah,
I
just
wanted
to
bring
up
a
couple
of
things
and
pretty
much
synchronize
on
the
release
and
what's
left
so
basically,
we're
almost
done
like
milestone
is
almost
complete,
a
big
thanks
to
american
people
who
offer
their
hand
because
we're
a
little
bit
understaffed
right
now
with
giuseppe
out
ill
and
all
that.
So,
in
my
personal
view,
there
are
just
a
few
things
that
are
left.
One
thing
is
that
we're
currently
working
on
trimming
the
role
of
the
service
account
and
training
the
ship
to
take
out
all
permissions.
D
We
have
we're
not
done
with
this,
yet
there
are
also
the
two
documents,
the
contributing
and
the
installation
markdown.
So
distillation
dock
is
probably
going
to
be
contributed
by
johannes.
I
don't
remember
an
exact
name
star
and
wayne
employee
who
is
in
touch
with
us.
We
pretty
much
gave
him
a
preview,
basically
a
script
that
installs
a
release
together
with
a
terrible
of
the
release.
D
So
I
commented
in
that
story
and
we'll
probably
spin
a
chart
with
that
after
the
release,
because
you
know,
users
of
the
product
will
not
care
about
rci,
vault,
etc
and
its
domains,
but
something
that
I
came
across
while
reviewing
those
renaming
prs
was
the
cfcli
has
a
config
section.
That's
called
something
like
cfoncage
enabled
true
or
false,
so
I
wanted
to
bring
it
up.
Do
we
want
to
rename
that
before
we
release?
Do
we
do
we
care
actually
at
all?
It's
somewhat
internal?
E
If
we
release
before
we
change
cfo
cat's
enabled
setting
in
the
config,
that
would
be
a
bit
grim
that
we
would
have
to
support
cfoncage
settings
and
curify
settings,
because
we
would
probably
want
to
be
backwards
compatible,
which
is
going
to
be
very
annoying
or
maybe
we
just
don't
want
to
be
backwards
compatible.
It's
fine.
D
Maybe
at
this
point
we
are
not
very
much
concerned
like
it's
a
beta.
It's
a
zero
one.
Zero
is
going
to
be
zero
one
zero.
So
I
think
we
can
probably
make
breaking
changes
and
also
we
can
choose
to
never
do
it.
I
mean
if
we
decide
that
it's
not
user
phasing
and
we
don't
care,
we
can
just
leave
it
like
that
forever
and
then
we
are
backwards
compatible
and
after
all,
it
is
cfon
gates.
It's
just
called
griffy.
C
E
B
D
C
D
D
Cool
yeah-
I
was
kind
of
leaning
towards
this
anyway,
because
I
didn't
want
to
block
anything
yeah.
I
guess
if
someone
one
thing
that
I
wanted
to
point
out
like
in
terms
of
the
rename
and
the
domains,
I
would,
I
think,
it's
wise
to
not
touch
the
domain,
not
touch
concourse
and
not
touch
volt
until
we
release
because
we're
going
to
release
using
the
pipeline,
which
is
resolved.
So,
let's
just
make
sure
we
don't
disturb
these
systems
and
after
we
release,
we
can
pick
up
a
chart
to
to
switch
the
domains.
C
D
D
I
would
prefer
it
to
be
persistent
first
and
to
be
able
to
all
to
unseal
itself.
So
we
have
choice
for
that,
and
I
guess
we'll
deal
with
that.
First
and
then,
then
we
can
switch
the
domains.
I
just
wanted
to
raise
it
so
that
no
one,
no
one,
does
it,
because
if
we
crush
the
eye
right
now
it
would
be
a
bit
annoying
and
yeah.
The
other
thing
is
pretty
much.
Can
anyone
think
of
anything
else
that
we
need
before
the
release.
E
I
would
like
to
piggyback
on
that
topic.
So,
while
working
on
the
release
pipeline,
we
asked
ourselves
what
are
we
actually
going
to
release
so
at
the
end,
we
decided
that,
provided
that
we're
currently
not
going
to
release
pm
charts
or
whatever
that's
customizable,
our
release
should
include
the
ammos
that
are
deployable
on
a
local
kind
cluster.
E
E
We
thought
that
this
is
a
reasonable
approach,
because
we
currently
don't
have
the
means
to
have,
for
example,
various
files
which
you
can
change,
and
we
also
hacked
a
sample
script
which
deploys
such
a
release
tarball
on
a
kind
cluster.
It
actually
creates
the
kind
cluster
and
deploys
it
which
internally
calls
our
install
dependency
script
and
so
on
and
so
forth.
E
E
Currently,
this
is
done
in
our
test
accounts,
because
we
are
lacking
permissions
of
the
cloud
foundry
docker
team,
or
something
like
this,
but
we
are
going
to
sort
it
out,
but
the
main
thing
is
that
the
release
turbo
is
only
going
to
contain
yamls.
That's
it
they're
going
to
reference
the
proper
docker
images.
Yes,
but
if
you
want
to
configure,
for
example,
namespaces
secrets,
whatever
you're
on
your
own.
D
And
that's
why
we
have
to
install
dock
right,
because
it
will
advise
what
you
need
to
do
in
order
to
make
the
thing
run
like
you
need
to
create
certain
secrets:
put
them
in
there
and
then
apply.
You
also
need
to
install
the
prerequisites
like
hnc
and
others,
or
you
can
use
our
hack
script.
That
just
does
everything
if
you're
impatient
or
something,
and
so
we
we
thought
a
good
thing
to
release
will
be
something
that
can
run
standalone
like
local
registry,
the
local
registry
back
thing
that
we're
deploying
against
on
kind.
D
D
E
D
F
D
Sounds
like
it
might
be
the
right
choice.
Okay
and
yeah-
I
mean
that's,
probably
it's
probably
it
really
and
then
the
the
last
thing
is.
When
do
we
do
the
release?
But
I
guess
after
we
are
done
with
everything
we
just
wait
for
for
someone
to.
We
either
just
cut
it
or
maybe
we
consult
with
eric
or
someone
saying
when
they
want
it.
D
Not
really
sure,
let's
think
I
guess
geppy
probably
had
a
plan,
I
never
thought
about
it.
But
now,
if
he's
going
to
be
out-
and
we
want
to
release
it
quickly-
I
mean
I
would
even
wait
for
him
to
get
back
and
talk
you
through.
But
if
someone
says
that
it's
more
urgent
to
to
get
the
res
out,
we
don't
need
to
wait.
A
G
Well,
I
would,
as
in
most
things
I
will
leave
the
hard
work
to
you
all
and
I've.
Given
you
these
logos,
I
there's
my
first
time
working
with
lf
creative
services
and
I
think
they
did
a
pretty
good
job.
I
did
follow
up
with
them
on
friday
and
I
asked
them
to
do
a
couple
tweets
like
you
know
what
did
I
say,
I
asked
them
to
do
a
few
more
things,
because
it's
always
good
to
make
the
decision
making
even
harder
yeah.
G
So
I
asked
them
to
do
one
a
with
with
the
cloud
foundry
font
logo
from
2a,
and
I
asked
them
to
do
1a
with
the
mountain
from
concept
3,
but
with
the
gear,
and
I
asked
them
to
do
2b
from
the
uppercase,
1b,
kariffy
font
and
likewise
1b
with
the
lowercase
2b
gradient
font,
and
then
I
also
asked
them
that
they
implement
concept
2a
with
the
seven-pointed
gear,
as
opposed
to
the
eight-pointed
gear.
So
basically,
I
just
tried
to
go
through
the
comments
and
various
things
that
seemed
popular
or
that
people
were
inclined
to
do.
G
You
know
I
asked
them
to
do
a
few
more
things.
I'm
not
surprised
they
didn't
get
back
to
me,
because
that
was
you
know
friday
before
easter
weekend.
Now
it's
tuesday,
so
you
know
I
hooked
up
a
few
more
things,
but
but
I'll
I'll
leave
the
difficult
job
of
deciding
on
the
actual
logo
to
the
working
group.
So
how
you
want
to
do
that?
How
you've
you've
voted
on
the
name
in
the
past?
If
you
want
to
do
that,
but
you
know
this
is
sort
of
tricky.
G
G
So
I
want
you
to
like
it
too
so
yeah,
like
I
said
I
will
defer
this
difficult
job
of
deciding
on
the
logo
to
you
all,
but
just
let
me
know
once
the
decision's
been
made
and
I'll
make
it
so
and
I'll
get
you
some
swag
and
we
can
work
yeah
I
mean
next
step.
Then
too
is
updating
the
website
and
putting
some
technical
docs
and
things
like
that
up
and
we'll
want
the
logo
ready
for
that.
So
this
is
something
we
should.
You
know
prioritize,
but
I
don't.
G
G
G
Yeah,
so
if
you
want
to
use
the
exact
same
approach
you
did
for
for
settling
on
the
name,
I
think
that's
that's
a
good
way
to
go
and
I'll
hopefully
get
that
back
from
them.
I
can
follow
up
tomorrow,
or
so
you
know,
but
I'll
hopefully
get
that
back
from
them
later
this
week,
and
then
people
can
put
in
ranchos
votes
and
then
hopefully
have
that
settled
by
maybe
next
week.
H
Yeah,
so
there
is
a
meeting
that
you
scheduled
for
the
29th,
where
we
want
to
discuss
exclusively
about
a
few
items
that
have
to
go
to
the
press
release
but
then,
generally
speaking,
the
idea
is
folks
do
not
have
to
wait
for
the
meeting
per
se
you're.
More
than
welcome
to
add
your
comments
to
the
document
that
I've
shared
a
link
to,
if
you
have
some
specific
inputs
about
some
of
the
non-technical
or
non-engineering
aspects
of
the
whole
release,
I
think
the
document
the
questions
in
the
document
are
a
great
place
to
start.
H
So
we
obviously
welcome
inputs
from
everybody.
Doing
this
async
is
a
lot
easier
than
you
know,
trying
to
schedule
something
because
of
time
zones
because
of
vacations
because
of
different
calendars.
I
know
it's.
You
know
hard
enough
to
get
folks
to
meet
once
in
a
while
for
the
working
group
meetings.
H
I
don't
want
to
necessarily
study
more
meetings
and
things,
but
obviously
we're
going
to
have
a
sync
meeting.
But
if
folks
have
some
inputs,
please
please
feel
free
to
add
them
to
the
doc.
If
you
want
to
chat
one-on-one
or
if
you
want
to
make
this
something
on
slack,
you
know
feel
free
to
do
that
as
well.
It's
easier
for
folks
to
just
work
that
way.
I
guess
so.
That
was
my
thing
for
the
pr
document
and
I
guess
one
of
the
more
pertinent
questions
that
we're
looking
for
an
answer
to
is
a
release
date.
D
D
We
we
have
just
literally
three
stories,
one
of
which
technical
we're
currently
doing.
There
are
some
minor
problems
I
think
we'll
manage
to
to
complete
it
this
week
and
then
we
need
the
documentation
so
we're
basically
waiting
for
the
install
talk
from
johannes.
I
think
he's
on
the
call
and
the
other
thing
is
probably
going
to
be
written
up
by
the
us
colleagues,
so
I
have
the
feeling
that
by
the
end
of
the
week
we
might
be
able
to
technically
able
to
cut
it.
F
F
Okay,
so
the
the
talk
itself
does
get
you
to
a
point
that
you
get
everything
set
up
installed,
but
it's
apparently
it's
failing.
The
only
thing
that
I
really
need
to
go
through
is
the
script
provided
and
go
ahead
and
jump
in
make
those
changes,
and
hopefully
I
will
have
the
work
invasion
which
I
can
then
depict
on
the
documentation
itself.
D
D
D
H
Any
sense,
probably
a
couple
of
weeks,
would
be
a
good
estimate.
I
mean
it.
I
think
it's
the
same,
as
you
know,
I
think
a
marketer's
promise
is
just
the
same
as
an
engineer's
promise
like
this,
so
give
them
two
weeks.
Give
them
four
give
them
six
they'll
have
enough
to
enough
to
do,
but
I
guess
a
couple
of
weeks
is
runway
is
not
too
bad.
I
will
reach
out
to
those
folks
and
speak
to
them
as
well.
A
H
This
was
also
discussed
like
a
couple
of
weeks
ago.
Somebody
brought
it
up
asking
if
it's
a
blocker
for
any
of
the
engineering
work.
It
absolutely
is
not.
You
folks
can
continue
to
do
your
work,
and
then
we
can,
just
you
know,
pick
up
stuff
and
announce
it
on
on
different,
like
channels
and
things
like
that,
independent
of
any
engineering
work
that
is
on.
G
Yeah
I
I'd
say
that
the
the
actual
github
release
doesn't
need
to
be
too
tightly
coupled
to
the
marketing
push
right.
They
should
be
close,
but
so
yeah
I
mean
whenever
the
github
release
is
ready.
You
know
you,
I
don't
think
you
need
to
hold
it
up,
but
but
it
would
be
nice
to
have
soon
like
okay.
This
is
when
we're
gonna
make
the
marketing
push
like
that
date.
We
want
to
have
a
set
some
weeks
in
advance.
D
F
D
D
G
F
A
H
H
We've
been
having
improved
traction
on
this
call
since
since
last
year,
so
we
have
a
lot
of
people
who
come
in
and
like
discuss
like
a
bunch
of
different
things
about
different.
You
know
aspects
relating
to
cloud,
foundry
working
groups,
different
projects,
and
so
I
thought
it
would
be
good
to
give
them
like
a
preview
of
what
corey
fee
is
what
it
can
do
and
basically
try
and
install
this
on
a
gk
cluster
live
during
the
car.
H
F
H
I
wanted
to
invite
folks
from
this
channel
to
be
part
of
that
call
if
you
can
make
it
the
link
to
the
call
is
available
on
the
community
calendar.
So
if
folks
are
you
know
interested
in
being
a
part
of
that
call,
you're
very,
very
welcome
to
be
part
of
it.
Help
answer
questions
help
me
out.
If
you
know
the
demo
crashes
and
burns
and
do
what
demos
are
supposed
to
do
so
yeah.
That
was
my
big
announcement.
A
A
H
D
D
D
F
D
Can
pm
I
can
pm
to
terraform
config
to
ram
if
it's
a
personal
message,
it's
fine.
I
mean
it's
not
too
secret
by
itself.
There
are
no
secrets
in
it,
but
we
just
wanted
to
make
sure
we
don't
disclose
exactly
how
exactly
what
resources
we're
locating
stuff
like
that,
but
I
could
pm
the
public
scripts
and
the
configs,
which
are
private
to
to
ram
for
some
reference.
Without
my
help.