►
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
Hello,
everyone
and
welcome
to
the
contour
community
meeting.
Slash
open
discussion
today
is
martial.
Third,
yes,
sorry,
thank
you.
The
valero
community,
I'm
hosting
way
too
many
communities.
Thank
you.
The
valero
community
meeting,
slash
open
discussion
today
is
march
23rd
2021
we're
almost
done
with
another
march,
so
close,
so
we've
got
some
status
updates
and,
let's
dive
into
them.
First
up
we
have
ashish.
B
For
me,
I
was
helping
out
new
pm.
I
don't
know
I
think,
she's
on
the
call.
Today
she
had
a
conflict.
I
was
helping
her
out
familiarizing
with
r17
road
map,
and
I
was
also
out
for
a
couple
of
days
last
week,
other
than
that
I
don't
have
anything
else
to
update
I'm
curious
to
know
where
we
are
with
the
one
six
release
and
how
what
we
can
do
to
get
us
get
that
out
of
the
door
at
least
an
rc.
A
Sounds
good
any
questions,
comments
for
ashish.
C
Do
you
know
is
is
dave
on
the
call
I
think
yeah
nope,
just
because
I
know
that
he
I
have
to
ashish's
question
on
the
one
six
really
status.
I
know
that
he
was
working
on
getting
some
tests
to
run,
so
I
think
we
probably
need
to
like
check
in
with
him
to
see
how
that's
going,
and
that
should
give
us
a
better
indication
of
of
when
we
can
create
the
rc.
A
I
see
a
lot
of
hands
going
up
right,
maybe
later
maybe
later
right.
Next
up
we
got
brigitte.
C
Yeah,
so
during
last
week
I
don't
know
if
you,
I
don't-
have
a
huge
amount
of
stuff
to
report
with
regard
to
the
the
road
map
and
progress
there.
I've
been
focusing
on
some
internal
build
stuff,
but
one
thing
I
did
add
which
we
decided
we
needed
was
a
document
to
describe
the
the
testing
requirements
that
we'd
like
to
put
valero
through
as
part
of
any
given
release
process
at
the
minute.
C
We're
still
doing
some
manual
testing,
so
we've
documented
that,
and
hopefully
we
can
try
and
convert
this
into
n10
tests,
which
would
run
automatically
in
the
future.
C
But
for
now
we've
documented
it,
and
that's
really
all
I
have
to
report
with
regard
to
items
towards
the.
C
A
Sounds
good?
Do
we
support
all
the
way
back
to
kubernetes
112.
C
It's
currently
documented
that
we
support
all
the
way
back
to
1
10..
However,
it
was
discovered
during
this
really
cycle
that
some
changes
in
the
crds
mean
that
they're
no
longer
compatible
with
kubernetes
111
earlier.
So,
yes,
I
think,
as
of
right
now,
our.
C
D
I
was
going
to
point
out
we're
actually
using
blairo
one
even
earlier,
but
we've
had
to
modify
the
crds
to
conditional
basically
for
111
earlier
we
can't
run
the
validation,
otherwise
we
haven't
run
into
any
issues
in
the
code
base,
yet
that
you
know
has
been
a
clash.
Although
we
understand
it's
not
supported.
C
I
think
so
yeah
I
know
I
I
noticed
that
just
before.
Just
before
this
call,
I
noticed
that
genting
had
put
up
a
pr
to
upgrade
them
to
v1.
We've
also
had
a
few
community
requests,
given
that
crd
v1
beta
1
is
going
to
be
deprecated,
I
think
in
kubernetes
1
22
or
it's
going
to
be
removed
in
122,
it's
deprecated
now,
but
will
be
removed
in
122,
and
so
I
think
that
we
need
to
have
developed
some
kind
of
plan.
For
that
I
don't.
C
I
don't
know
what
it
is,
but
I
don't
think
that
we
can
just
do
a
hard
switchover
given
that
folks
are
still
running
earlier
versions
of
kubernetes
and
rely
on
that.
B
A
Would
that
be
something
that
we
add
for
the
the
roadmap
for
1.8?
Maybe.
C
Yeah
yeah,
I
think
so
I'll
I'll
make
a
note
I'll.
I
think
it'll
come
up
in
discussion
on
genting's
pr,
but
I
think
it's
something
that
we
need
to
have
a
plan
of
action,
for
I
saw
how
we're
going
to
do
that
upgrade.
A
That's
good
any
other
questions,
comments
for
bridget.
B
I
think
I
was
asking
what
what
is
preventing
us
from
shipping
one
dot
release
candidate
for
1.6
and
bridget
mentioned
they've
had
some
tests.
So,
oh,
we
have
a
set
of
release
criteria.
A
F
Hello,
everybody
so
I
checked,
and
there
are
no
below
contributions,
which
makes
sense
because
we
sort
of
called
freeze
and
not
merging
anything
unless
it's.
F
Release
related
there's
also
no
q,
a
contributions.
Nobody
except
dave
has
answered
the
last
questions
there.
F
I
fell
in
a
sort
of
rabbit
hole
last
week
when
I
started
testing
the
1.6
1.6,
actually
not
even
the
the
actual
release,
but
just
against
maine,
with
the
plugins
that
I
built
images
for
and
so
there's
something.
I
think
there
was
something
funky
with
my
aws
cluster
and
then
I
started
running
the
uninstall,
and
then
I
noticed
that
the
what
uninstall,
if
you
found
an
error,
it
would
return
but
not
clean
up
the
rest
of
the
things.
F
So
that's
a
bug
that
was
a
bug
that
I
fixed
so
that
I
have
that
pr
which
does
two
things
fixes
the
uninstall
issue,
because
if
even
if
there
is
an
error
with
one
part
of
the
uninstall,
we
should
continue
uninstalling
removing
as
much
as
it
can.
And
of
course,
if
there
is
any
error,
we
return
the
error
but
clean
up
as
much
as
we
can.
So
I
fixed
that.
A
Zuma's
been
acting
up,
I've
had
a
lot
of
people
drop
off
throughout
the
day.
A
Here
we'll
get
back
to
carlesia
when
she
rejoins
here
babe,
you
want
to
go
on
your
your
status
updates.
E
Yeah
sure
so
we're
trying
to
move
forward
with
the
gain
to
the
1
6
rc.
So
the
main
blocker
right
now
is
getting
everything
running
against
vsphere
and
I'm
just
running
into
some
issues.
There
should
be
able
to
work
through
it
and
get
something
in
today
or
tomorrow.
E
I
think
that's
about
it
for
our
release,
candidate
plus,
we
have
carlesia's
update
on
the
uninstall,
so
we
need
to
review
and
merge
that
and
and
we
should
be
ready
to
start
cutting
the
rc
and
we
need
to
see
about
you
know
running
our
automated
tests
on
the
various
clouds
and
yeah.
A
Yeah
welcome
back
alicia
yeah.
I
was
just
telling
everyone
here:
I've
had
a
lot
of
people
drop
off
zoom
throughout
the
day,
so
far,
so
might
be
just
not
lucky.
Do
you
want
to
continue
your
your
conversation
there
about
the
uninstall.
B
Before
before
we
start
go
back
to
college,
do
you
need
any
finishing
up
with
that?
Do
you
need
any
any
any
help
with
the
vsphere
stuff
that
you're
looking
at,
or
is
it
all
like
being
look
get
kind
of
taken
care
of
just
trying
to
see?
If
I
can
help.
E
I
will
probably
reach
out
to
the
easter
team
and
see
it
there's
a
known
issue
that
I'm
fixing
okay
and
if
we
could
work
on
even
getting
the
aws
tests
with
the
volume
snapshot
or
running
through
corgi.
That
would
be
good.
So
I
think
I
checked
in
everything
we
can
when
we
sync
up
a
little
bit
off.
I
think
I
checked
in
everything
so
that
volume,
snapshotter
volume
snapshots
should
run
versus
aws
and
maybe,
if
we
can
get
the
corgi
runs
kicked
off.
B
B
Well
and
kalisia,
I
think
you
were
explaining
the
where
the
uninstall
would
error
out
even
on
the
first
occurrence
of
any
failure,
and
we
wanted.
We
wanted
it
to
clea,
remove
or
uninstall
as
much
as
possible
and
kind
of
plow
through
the
errors.
F
Okay,
yes,
okay,
thank
you,
so
I
fixed
that
and
another
issue
that
I
noticed
was
that
some
resources
that
had
been
created
in
the
cluster
as
part
of
a
test,
not
as
not
not
I'm
not
talking
about
the
little
resources
but
other
resources,
like
other
workloads,
were
being
left
behind.
If
if
there
was
a
natural
error
for
some
weird
reason,
unexpected
error,
because
I
was
getting
unexpected
errors,
so
I
get
the
chance
to
notice
that
so
I
made
so
I
cleaned
up.
F
So
I
went
through
every
test
where
everywhere,
where
there
was
a
potential
to
air
out
and
I
made
sure
to
call
a
function
to
just
clean
up
the
resources
that
had
been
installed
at
the
beginning.
So
this
is
something
that
going
forward.
We
should
be
mindful
of
whenever
we
add
a
text,
and
I
also
added
documentations
as
a
reminder
forever
for
us
and
for
anyone
who
adds
tests
in
the
future
that
whenever
resource
is
added,
we
have
to
make
sure
at
every
error
point
that
resource
resources
cleaned
up.
F
Otherwise
it
just
is
going
to
stay
behind,
and
the
next
test
might
not
like
that.
So
that's
the
second
thing
that
I
cleaned
up
and
the
third
thing
that
I
cleaned
up
and
I'm.
F
I
think
this
is
going
to
be
helpful
when
whoever
reviews
that
pr
is,
I
noticed
that
we
were
instantiating
api
clients
multiple
times
unnecessarily,
so
I
wiped
out
all
that
out,
put
everything
into
one
little
function,
and
now
you
know
if
you,
if
you
need
a
client,
just
call
this
factory,
this
constructor
and
you
get
your
clients
and
I
made
sure
to
just
you
know
instantiate
once
at
the
beginning
of
the
test
and
then
that
client
can
be
used
everywhere
in
the
test.
F
So
that's
another
thing
to
be
mindful
of
I
also
added
documentation
and
now
so
fourth
thing
not
like
not
nothing.
That's
breaking
the
test
before
going
forward,
we
should
be
using
the
controller,
runtime
api
client
and
not
the
go
client.
So
just
just
first
to
be
mindful
of
that,
and
whenever
we
review
prs2,
if
people
use
anything,
that's
not
the
runtime
could
build
their
clients.
We
should
say:
hey,
please
change!
F
And
I
should,
I
think,
I'll,
have
this
pr
pushed
today
for
sure
pretty
sure
pretty
solid
and
then
our
thank
you
all
to
make
sure
he
gets
revealed.
A
F
It's
mostly
that
I
was
in
the
process
of
doing
that
when
I
found
these
issues
with
the
test,
so
I
basically
once
this
is
all
working
I
just.
I
still
need
to
to
run
that
and
review
bridget's
pr
unless
other
people
review
it
first
and
by
the
way
dave
that
problem
with
creating
that
that
deletes
custom
resource
it
went
away.
F
A
A
A
All
right-
and
we
don't
have
any
contributor-
shout
outs
as
kalisia
mentioned,
because
we're
in
a
code
freeze
and
we
don't
have
any
qa
q
and
a
not
a
q
and
a
questions
outside
of
the
the
ones
that
they've
had
to
answer.
So
with
that.
Thank
you
all
for
joining
the
valero
community
meeting,
the
valero
community
meeting
and
open
discussion
on
march
23rd
2021
have
a
good
week.
Everyone
see
you
all
next
week.