►
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
A
We're
gonna
start
with
some
status
updates
and
then
we're
going
to
dig
into
a
really
big
announcement
here.
First
off
we
have
calicia.
B
A
C
Hi
everyone
yeah
so
like
carlos
you
mentioned,
we
were
doing
testing
last
week
and
as
of
this
morning,
we
have
officially
released
the
1.6
release,
which
is
great.
C
Check
it
out,
please
try
it
out
and
give
us
your
feedback
yeah.
It's
very
exciting,
very
happy
to
finally
get
out
so
that
everyone
can
finally
make
use
of
it.
So
yeah
we're
all
very
excited
to
see
it
land.
C
So
what's
in
the
1.6
release,
okay,
wow,
so
we
have
a
few
different
highlights,
so
I
think
probably
one
of
the
biggest
features,
one
of
the
things
that
people
have
been
asking
for
is
support
for
multiple
credentials
for
backup
storage
locations.
C
So
what
this
new
feature
enables
you
to
do
is
if
you
have,
if
you
want
to
configure
multiple
backup
storage
locations
with
different
providers,
you
can
now,
through
the
valero
cli,
assign
different
kubernetes
secrets
to
those
backup
storage
locations
to
like
more
seamlessly
back
up
to
different
providers
and
also
have
multiple
backup
search
locations
with
the
same
providers.
So
if
they
need
different
credentials.
This
is
something
that
wasn't
possible
on
valero
before
but
is
not
available.
C
So
we
also
have
loads
of
the
great
features
and
improvements
from
the
community
as
well,
so
pranav
had
added
progress,
reporting
for
restores
frankie,
who
is
on
the
call
with
us
today?
She
had
added
restoring
the
api
groups
or
kubernetes
api
groups
by
priority
level,
so
this
is
building
on
a
feature
that
raphael
had
added
back
in
one
four.
We
also
have
an
upgrade
for
rustic,
so
we're
now,
including
the
latest
version
of
rustic
and
also
during
this
release
cycle
as
well.
C
We
added
antenn
testing
for
valero,
so
just
trying
to
continue
with
keeping
the
reliability
and
stability
of
the
the
project
going
forward,
and
I
think
that's
going
to
help
with
our
release
processes
in
the
future
and
really
help
us
get
those
releases
out
the
door
quicker,
as
we
add
more
features
and
yeah,
then
there's
also
a
variety
of
cli
usability
improvements
as
well,
so
there's
loads
of
other
stuff.
C
B
We
still
have
to
do
some
things
by
hand
and
it's
great
that
there
is
a
script
that
you
can
run
and
add
a
workload
with
a
bunch
of
data
to
any
of
the
providers
that
we
support,
including
vsphere,
and
I
we
used
it
to
do
some
manual
tests
and
it's
part
of
the
e3
test
to
to
add
this
data,
and
it
was
fantastic.
It
was
just
so
great
having
them.
There
was
stable.
B
We
always
every
time
everyone
it
worked
and
we
are
going
to
have
a
system
where
the
e3
tests
will
be
run
on
p
before
merging
prs.
C
Yeah,
definitely
it's
been
such
a
huge
improvement
to
our
workflow,
so
yeah
thank
you,
dave
and
the
sheesh.
A
Awesome
stuff
does
anyone
else
have
anything
to
add
for
the
1.6
release
here.
A
A
All
right,
speaking
of
testing
dave,
you've
been
doing
some
testing
in
release
physics.
E
Well,
yeah,
it's
just
the
getting
the
release
out,
so
we
did
that,
and
that
is
pretty
good.
So
that
means
that
we're
also
we
can.
We
can
start
merging
prs
again,
so
anything
that
gets
approved.
We
can
roll
it
in
we'll
try
to
keep
this
window
smaller
for
the
next
release
for
1.7,
but
we're
going
to
keep
on
this.
E
This
simple
code
freeze
model
for
a
while
until
it
becomes
un,
you
know
until
it
gets
to
the
point
where
we
really
need
to
branch
things
at
release
time,
just
to
avoid
the
amount
of
cross-porting
and
thinking
that
has
to
go
in.
Ideally,
when
we
go
into
the
next
rc
phase,
the
pr
backlog
will
be
very
small
and
the
intent
is
that
as
we
go
into
rc,
we
should
have
a
lot
of
confidence
and
everything
will
just
pass
the
tests.
E
F
All
right
ashish
for
me
it
was
mostly
rcc2
testing
on
like
gcp
autistic
and
all
that
stuff,
so
nothing
else
going
on
going
forward
going
to
pick
up
some
stuff
from
the
170
roadmap,
especially
the
csi
stuff.
So
let
me
have
some
stuff
to
report
next
week.
I
guess.
A
Sounds
good,
does
anyone
have
anything
else
they
want
to
add
today?
D
Awesome
so
I
was
just
I
thought
I
had
a
issue
already
up
there,
but
I
I
was
going
to
share
this
just
if
I
can
just
type
this
up
and
put
it
in,
but
essentially
what's
happening
is
I
I
wanted
to
take
some
time
to
access
questions
of
valor
maintainers,
where
we're
using
valero
in
our
environment
and
what
we're
seeing
is
we're
passing
in
the
ca
set
to
the
valero
cli,
we're
able
to
take
backups
successfully
against
the
cloud
service
provider,
but
whenever
we
do
a
whenever
we
do
a
restore,
we
get
this
issue,
I'm
going
to
share
that
in
the
chat
and
I'm
I'm
putting
up
I'm
creating
a
valeria
issue.
D
D
What's
the
life
cycle
of
their
set
are
we
are
we
posting
passing
that
into
a
directory
in
the
host?
Based
of
what
I
saw,
I
saw
that
it
was
creating
like
a
temp
directory
for
the
set,
but
I
just
wanted
to
learn
more
about
that
process
and
see
if
this
is
something
that
is
being
tracked.
F
So
we
don't
valero
does
not
manage
the
life
cycle
of
the
cert.
It
basically
is
that's
a
that's
just
a
way
that
we've
set
up
whether
or
to
use
certificates
that
our
users
have
set
up
and
going
going
by
this
error
looks
like
the
csr.
This
search
verification
is
not
completing,
because
valero
is
not
able
to
verify
the
cert
presented
to
it
by
the
storage
or
whatever
api
that
you're
calling.
H
Today,
can
I
chime
in
yep?
Yes,
please
go
ahead.
Thank
you,
hi
everyone.
My
name
is
karanos
and
I
work
with
ten
day
on
some
projects.
So
what
we
were
noticing
is
that
when
we
passed
in
the
certificate
with
the
ca
cert,
it
seems
like
it
gets
added
to
the
backup
storage
location,
but
it
doesn't
appear
that
the
certificate
is
used
anywhere
else.
H
So
in
environments,
where
you
have
proxies
that
sit
in
front
of
endpoints,
it
seems
like
that
certificate
should
potentially
be
provided
to
the
valero
pods
themselves,
because
the
pods
seemingly
are
able
to
make
backups
and
push
the
push
to
s3.
Since
the
backup
storage
location
has
the
ca
cert,
but
any,
but
any
other
action
because
valero,
like
you,
said,
isn't
able
to
verify
those
those
certs
that
it's
encountering
in
the
proxy
that
sits
before
it.
It
errors
out.
So
I
guess
from
when
I
was
reading
the
documentation
I
mistakenly
assumed.
H
F
And
to
clarify
to
your
other
point
of
you
are
giving
csrts
to
the
backup
storage
location.
So
you
are.
You
are
not
giving
the
back
certificate
to
the
backup,
storage
location
that,
but
you
are
associating
the
backup
storage
location
with
a
certain
certain
cssrt
and
valero
uses
that
to
when
it
is
trying
to
interact
with
that
particular
backup
storage
location.
It
uses
that
csr
to
establish
that
secure
connection
with
the
backup
storage
location,
to
put
and
retrieve
backup.
F
It's
interesting
that
you
say
that
weather
is
able
to
store
the
backups,
but
you
are
still
getting
this
error.
H
Yeah,
it's
possible
that
it
was
telling
us
it
was
successfully
storing
the
backups,
but
since
we
had
no
way
to
actually
test
the
restore
right,
because
we
were
getting
errors
on
pv
actions
to
actually
create
the
persistent
volumes
within
aws,
it's
possible
that
the
backups
weren't,
even
created
correctly
right
and
valero,
was
reporting
back
that
they
were.
I
mean
we
did
see,
files
in
s3
and
the
buckets
that
we
specified,
but
obviously
we
weren't
able
to
restore
to
actually
test
the
validity
of
those
backups.
E
So,
okay,
let's
look
at
what's
going
on
here,
so
what
you're
saying
so
on
the
restore
path,
so
you're
using
are
using
rustic
or
evs
snapshots,
abs,
snapshots,
okay,
so
on
that
path,
after
on
both
paths,
we're
going
to
actually
yeah
on
that
path
where
the
ebs,
the
aws
plug-in,
is
going
to
need
to
be
able
to
communicate
with
the
aws
control,
plane
and
say
things
like
create
a
volume.
E
H
To
an
extent
yeah,
I
mean
we're
working
with
machines
that
have.
I
am
roles
that
have
the
proper
permissions,
but
I
think,
since
some
of
the
actions
are
actually
right,
hitting
those
end
points
and
making
calls
to
those
end
points
that
were
that's
where
we
run
into
the
certificate
issues.
H
Yeah
I
mean
I
was
as
well
and,
like
I
said,
that's
why
I
I
couldn't
test
the
validity
of
the
snapshots
that
were
taken.
I
can
tell
you
that
my
work
around
was
to
take
the
same
cert
bundle
that
I
passed
via
the
flag
to
create
a
config
map
and
to
mount
it
to
the
valero
pod
at
what
is
it
etsy
ssl
right,
that's
the
search!
Okay
and
then
I
set
the
aws
underscore
ca,
underscore
bundle
environment
variable
to
that
path.
That
I,
where
I
put
the
starts
in
the
container
and.
F
H
C
I
have
a
feeling
that
the
I
need
to
look
into
it,
but
I'm
pretty
sure
that
the
aws
plug-in
that
we
use
only
applies
to
ca,
search
for
object,
storage.
It
doesn't
use
it
for
the
volume
snatcher
path
so
yeah
it
doesn't.
I'm
not
surprised
to
hear
that
it
didn't
work
for
the
volume
snapshotting
aspect
of
it.
E
E
Location,
so
I
think
what
would
make
sense
here
is
maybe,
as
part
of
the
install
even
being
able
to
install
alternate
certificates
into
all
the
containers
would
probably
get
around
this
kind
of
problem.
For
the
moment
it
sounds
like
you
have
a
workaround,
I
think
that's
a
good
workaround
yeah,
and
so,
if
you
put
in
you
know
we
can,
we
can
track
this
issue.
We
had
some
other
similar
things
coming
from
people
where
they
wanted
to
be
able
to
change
the
regions.
So
we
were
asking
this
in
community
meeting
a
while
back.
E
It's
like
because
this
this
concept
of
putting
a
proxy
in
front
of
the
cloud
provider
we
weren't
really
thinking
about
going
in
that
direction.
So
you
know
is
this
like
best
practices?
Where
is
this?
Coming
from.
H
It's
the
nature
of
this
particular
aws
environment
they're
in
it's,
it's
aws
region,
u.s,
iso,
east
one.
So
it's
an
isolated
aws.
H
But
yeah,
so
I
I
guess
I
like
how
you
guys
do
the
right,
the
installation
flag
for
ca
certs.
Maybe
you
can,
like
you
said,
be
either
extended
or
just
add
another
one
that
supports
it,
adding
to
the
containers
as
well.
That
would
definitely
work
for
us.
E
Yeah,
so
we
have
to
look
into
some
of
this
stuff
in
like
fully
proxied
environments,.
D
But
in
the
meantime,
with
a
with
the
walk
around
like,
would
this
be
like
a
good
walk
around
to
just
write
whenever
the
css
is
written?
We
write
that
into
the
same
file
path
that
we're
currently
using
with
the
config
map.
D
Would
this
be
something
we
can?
I
can
walk
with
someone
on
valero
team
to
make
a
pr.
I
don't
know
what
I
would
be
like
a
great
person
to
start
with,
but.
E
Yeah
yeah,
so
I
don't
want
to
just
slam
fixes
it.
So,
let's
make
sure
we
understand
what
we're
doing
and
how
absolutely
the
various
cloud
providers.
So
I
I
think
you
have
a
workaround
right
now
that
works
for
you,
and
I
I'd
ask
you
to
use
that
and
have
a
little
patience
as
we
work
through
the
process.
D
B
All
would
would
somebody
be
willing
to.
I
know
there
is
a
discussion
but
to
open
a
ticket
and
write
down
the
workaround,
and
you
know,
as
we
evolve
with
what
the
solution
is
going
to
be.
We
just
update
the
ticket
before.
E
Things
like
I'm
running
in
an
aws,
isolated
environment,
yeah
yeah-
I
mean
so
we're
doing
this
here
and
I'm
able
to
talk
back
and
forth
to
you
quickly,
but
you
know
in
in
general,
this
is
going
to
be
a
multi-day
extracting
information
process.
Sure
so
I'd
encourage
everybody
to
give
as
much
info
upfront
in
the
ticket.
As
you
can.
H
B
D
A
Good
one
awesome,
thank
you
folks,
so
I've
added
the
the
issue
to
the
notes
as
well.
So
if
anyone
wants
to
follow
along
later
on,
they
can
do
that.
B
Yeah
when,
when
the
issue,
so
that's
a
discussion
when
the.
A
Sounds
good,
does
anyone
else
have
any
other
discussion
topics
that
they
want
to
bring
up.
A
Today,
right
we
do
have
a
ton
of
contributor
shoutouts
in
the
release,
notes
we're
not
going
to
go
through
all
of
them
on
the
the
call
today,
but
yeah
huge
shout
out
to
everyone
who's
been
helping
out
with
this
release.
Thank
you,
everyone
from
the
community
and
thank
you
to
the
maintainer
team
here.
You're
awesome.
A
A
So
with
that,
thank
you
all
for
joining
have
a
fantastic
rest
of
the
week.
Try
out
the
new
release
and
talk
to
you
soon,
bye.