►
From YouTube: Technical Oversight Committee 2021/04/02
Description
Istio's Technical Oversight Committee for April 2nd, 2021.
Topics:
- New istio.io website, up on preliminary.istio.io, feedback welcome
- Working Group cleanup, proposal to convert Environments into Install/Upgrade group.
- Istio 1.9 user experience survey
B
B
B
C
Yeah
yeah,
I
think
we
only
expect
p0s
to
be
done.
Everything
else
is
best
effort,
yeah
yeah,
so
this
sounds
good,
there's
a
bunch
of
easier
than
risk
state.
I
I
see
yeah.
No,
I
mean
none
of
these
are
our
regressions
and,
and-
and
just
you
know,
it's
here
gets
better
every
release,
but
we
don't
do
everything
we
want
to
every
release.
That's
okay!.
B
F
B
B
Okay
and
the
docs
test
cases
are
out
for
review
for
the
first
community
testing
day,
which
is
approaching
very
close
13th
april,
and
the
good
news
is
we.
As
you
know,
most
of
the
operation
was
done
in
the
last
cycle.
Only
12
p0's
are
left
at
this
point.
The
only
caveat
is
what
we
have
not
done.
If
there
is
any
new
feature,
those
have
not
been
added
here
other
than
that
from
the
last
one.
Only
12
p0s
are
left
for
automation
for
p06.
A
A
B
Yeah,
that
will
be
great
because
last
time
we
went
up
to
83,
83
or
86
percent.
I
can't
recall,
but
that
is
a
great
number
right.
More
and
more
we
do
automation.
We
will
be
close
to
no
manual
testing,
eventually
yeah,
okay,
okay
and
for
110.
The
timeline
is
out,
so
the
launch
is
in
10th
august.
If
we
can
review
that,
if
we
have
time
now.
B
D
J
A
B
K
L
L
I
D
A
N
N
D
D
N
P
J
J
D
D
E
Saying
that
it's
about
operations,
because
we
focus
a
lot
on
the
day
one
but
the
day
two
is
way
more
important
and
there's
a
lot
of
overlap
with
user
experience
when
we
get
into
that
because
operations
and
user
experience
are
pretty
similar
when
we
get
down
to
it.
So
I
think
why
maybe
we
can
actually
consolidate
those
two
further.
If
we
wanted
to,
I
think,
that's
kind
of
what
nate
was
pushing
for
perhaps
yeah,
plus
one
of
that
no.
I
I
J
N
The
the
reason
for
the
existence
of
the
upgrade
working
group
was
that,
a
month
ago,
we
felt
like
this
was
an
important
enough
thing
for
the
project
that
we
needed
a
dedicated
set
of
people
focusing
on
this
with
a
dedicated
charter.
I
I
can
see
merging
it
with
installation
merging
it
with
ux.
I
worry
about
dilution
of
of
charter
and
of
focus.
P
I
I
D
J
N
J
J
D
M
K
M
C
That
that's
right,
sometimes
people
will
have
late
requests
and
feel
guilty
about
it,
but
but
there
is
pushback
and
we
start
looking
at
the
blast.
Radius
of
you
know
of
late
feature,
arrivals
and
then
there's
also
community
testing
and
anything
that
arrives
after
community
testing.
We
should
really
really
say
no.
D
H
At
least
for
one
six
and
four
one:
nine,
it's
been
informal.
If
there
were
any
changes
to
to
istio
api,
then
we
brought
them
forward
to
the
toc,
but
anything
that
wasn't
kind
of
related
to
that.
We,
at
least
for
one
six
and
one
nine.
We
we
tended
to
rely
on
the
subject
matter.
Experts
or
the
working
group
leads
to
provide
you
know,
kind
of
their
input
and
then,
depending
on
the
amount
of
code,
maybe
that
was
introduced.
H
A
K
There
are
a
couple
of
kind
of
in-flight
things
which
I'm
sort
of
informing
right
now
that
people
can
expect
yeah
like
telemetry,
api
and
related
things,
and
then
potentially
the
wasm
api
and
related
things
are,
are
potentially
going
to
come
in
just
a
little
bit
late
and
they
will
have
to
go
through
this
process.
So
so
we'll
see
what
actually
happens.
C
N
N
N
I
A
K
Yeah,
I
was
just
going
to
say,
like
following
up
on
on
lynn's
point
that
it
means
that
this
survey
should
be
repeated.
The
exact
same
service
should
be
repeated
when
there
is
more
one-line
data
and,
conversely,
it
means
that
the
one-eighth
survey,
if
it
was
there
like
maybe
now,
is
the
time
to
get
that
data.
If
we
expect
a
good
response.
N
I
A
H
A
A
That
would
be,
I
think,
that
would
be
very
useful.
We
had
something
similar
on
it
on
an
internal
project
like
five
years
ago.
That
was
really
helpful,
that
I
think
it
was
basically
that,
like
the
tool
there
was
a
tool
to
do,
you
know
actually
it
was
installed
and
upgrades,
but
there
was
a
tool
at
the
end.
That
said,
how
was
your
experience
take
the.
N
Survey,
okay,
so
I'll.
Take
that
as
an
action
item
moving
forward,
I
can't
change
istio
cuddle
now
for
one
nine,
but
moving
forward.
It
sounds
like
it'd,
be
a
good
idea
for
us
to
have
kind
of
a
standing
survey
for
each
version
after
upgrading
that
the
users
can
very
quickly
indicate
how
things
went.
Does
that
sound
about
right,
yeah.
D
So
mitch
I
would
recommend,
even
if
you
can't
say
steel
ctl,
to
do
some
of
the
dock
changes,
whether
it's
an
upgrade
nodes
or
this
the
one
line
block
to
have
a
link
to
the
survey
and
overall
it
looks
like
we
are
saying
that
if
you
do
a
blast
radius
for
this
survey,
we
might
not
get
a
lot
of
responses.
We
are
we're.
Gonna
live
with
it.
For
now
it's
okay!
If
you
don't,
we
will
just
have
to
either
repeat
it
with
110
or
in
110.
A
Like
I
was
thinking
right,
you
know
right
here,
like
they
finished
verifying
their
upgrade
right
here
say:
hey
here's
a
survey
to
take,
because
I
think
if
people
bang
their
head
against
things
a
lot
and
then
they
see
a
survey
they're
likely
to
take
the
survey
to
to
you
know
kick
us
around
a
little
bit
and
that's
good
right.
We
want
to
get
that
feedback
if
they
had
a
hard
time
or
if
they
had
a
great
time,
then
you
know
maybe
they
can
tell
us
it
was
great,
but
that's
a
yeah.
D
N
Thanks
yeah
and
actually
the
last
question
does
ask
users
for
their
contact
information
if
they're
interested
in
providing
longer
form
feedback
in
the
form
of
an
interview
in
the
fall.
The
ux
working
group
conducted
these
with
about
six
or
so
users
and
found
them
to
be
very
valuable.
So
if
they're
interested
in
providing
that
longer
form
feedback,
there
is
a
way
for
them
to
do
that.