►
From YouTube: Kubernetes Community Meeting 20190314
Description
The Kubernetes community meeting is intended to provide a holistic overview of community activities, critical release information, and governance updates. It also provides a forum for discussion of project-level concerns that might need a wider audience than a single special interest group (SIG).
See here for more information: https://github.com/kubernetes/community/blob/master/events/community-meeting.md
A
B
Alright,
let's
get
started
everybody,
it
is
March
14th.
This
is
your
weekly
community
meeting.
The
purpose
of
this
meeting
is
for
cigs
around
the
project.
You
sync
up
on
what's
happening
around
the
kubernetes
community,
reminder
that
we
are
streaming
this
meeting
in
YouTube
and
as
always
with
any
of
our
events,
the
code
of
conduct
is
in
effect
and
we're
also
recording
this
on
and
making
the
archive
available
on
YouTube.
So
if
you
say
something,
it
will
be
archived
forever.
B
We
have
a
demo
today
from
Daniel
Messer,
that's
going
to
be
doing
automated
data
operations
using
operators
and
then
we're
going
to
go
into
release,
updates
with
sig
beard,
welcome
back
and
then
we're.
We
have
three
SIG's
going
today:
Sagarika
tech,
chure,
sig,
vmware
and
sig
multi
cluster,
and
with
that
Daniel,
are
you
online
I
have
not
seen
him
join
earlier
so
with
that,
if
he
shows
up
we'll
kick
back
to
it
Aaron
are
you
comfortable
just
going
now,
while
we
wait
for
the
demo.
A
A
So
let's
talk
about
the
release,
notes!
No
sorry:
let's
talk
about
the
fact
that
I
did
not
get
slides
done
this
week,
I
kind
of
fell
ill
with
something
resembling
the
flu
or
strep,
and
my
release
team
stepped
up
and
did
a
phenomenal
job.
So
I
think
I
may
have
called
out
some
specific
people
and
shoutouts,
but
like
well,
and
truly
the
entire
release
team
really
stepped
up
and
have
greatly
improved
the
state
of
things
this
week
as
compared
to
last
week.
So
before
I
dive
into
this
Fix
of
that
a.
A
Number
of
people
have
been
really
freaked
out
that
if
they
merge
their
PR
right
now,
it's
not
going
to
get
into
114.
That's
not
how
code
freeze
works,
like
the
reason
code
freeze
exists,
is
that
PRS
that
land
right
now
are
guaranteed
to
get
in
114
you're
going
to
have
to
start
worrying
about
cherry-picking
PRS
into
the
114
branch.
A
By
that
time
we
want
to
accept
no
more
changes
unless
100%
super
strictly
absolutely
necessary.
This
is
because
we
want
to
give
the
release
time
to
actually
soak
over
the
weekend.
Give
it
a
couple
days
really
like
run
its
through.
It
run
it
through
its
paces.
So
we
can
decide
whether
or
not
it's
ready
to
go
out
the
door
on
Monday.
I
should
add
that
day,
but
I
think
it's
March,
26th
nope
beyond
that.
A
A
Sorry
about
that,
okay,
so
see,
I
signal
has
been
our
biggest
concern.
This
week,
we've
had
a
number
of
tests
that
have
been
flaking
or
continuously
failing,
and
one
of
the
things
that
concern
to
me
specifically
was
that
a
lot
of
this
flaking
and
failing
it
was
unclear
whether
or
not
go
the
move
could
go.
Lying
112
helped
us
out
with
that
or
not
so
from
a
scalability
perspective,
it
seems
like
going
112
has
passed
both
the
performance
and
the
correctness
tests
and
did
not
impact
the
performance
negatively
there.
A
However,
it
appears
as
though,
thanks
to
the
detective
work
of
Lu,
Bo,
Mir
and
Liggett
and
DIMMs
and
Justin
Santa
Barbara
and
some
others
I'm
sure
on
leaving
danger
out,
seems
like
there's,
maybe
a
bug
somewhere
in
go
line.
112
around
I
think
sync
at
once,
which
was
causing
some
of
the
upgrade
tests
to
flake
and
fail
and
was
causing
a
couple
resource
leakages.
So
this
is
why
the
difference
or
PSA's
test
was
failing.
It
update
tests,
but
not
in
the
master
blocking
jobs.
A
So
I'm
talking
about
this
one
of
most,
because
where
we're
at
today
is
we
really
really
like
to
stay
on
code
Lang
112.
So
we
asked
very
nicely
if
the
go
line
team
could
cut
a
new
patch
release
because
we
believe
there
is
a
bug
fix
in
going
at
the
moment
that
would
address
what
we
are
running
into.
They
said.
Yes,
we
hope
to
see
that
patch
release
land
either
today
or
tomorrow
when
that
land
and
it's
they're
a
couple
different
PRS.
A
If
things
push
on
a
little
bit
further
than
that,
we're
going
to
consider
pushing
code
thaw
back
by
a
couple
days,
because
we
believe
it
is
extremely
important
to
stay
current
with
golang
here,
so
we're
doing
everything
we
can
to
try
and
make
this
happen.
If
we
discover
it
does
not
fix
our
problems,
we
will
most
likely
revert
back
if
ago
line
one
eleven
five
and
we're
working
on
a
plan
for
that
separately.
A
We
have
significantly
pruned
down
issues
and
PRS.
At
this
point,
any
PR,
that's
open.
We
believe
it's
critical
that
it
land
in
this
release
and
we're
actively
making
sure
that
it's
progressing
forward
if
new
PRS
are
mysteriously
appearing
in
the
114
milestone.
We're
going
to
be
asking
why
we're
specifically
looking
for
things
like
what
enhancements
does
this
PR
tie
to
or
what
bug,
because
this
PR
our
fix
come,
preferably
with
an
issue
that
describes
why
it
is
important
that
it
land
right
now,
as
opposed
to
the
next
patch
release
of
114
or
in
115.
A
Okay,
just
to
reiterate
we're
getting
pushy
here
now,
because
we
really
are
trying
to
burn
down
if
you
feel
like
something
has
gotten
kicked
out
or
pushed
out
in
air.
It's
time
to
come
talk
to
us.
So
we
have
our
burned
down
meetings,
dick
Billy
they're
at
10:00
a.m.
Pacific,
Monday,
Wednesday,
Friday,
they're
at
8:00
a.m.
Pacific,
Tuesday
Thursday,
and
we're
also
active
on
our
slack
Channel.
But
we
are
now
entering
the
point
where
we
kind
of
need
to
talk
some
things
through
and
use
the
exception
process
if
it
seems
like
it's
really
urgent.
B
C
Can
you
all
see
the
deck
looking
good,
all
right,
fantastic?
So
the
first
thing
I
want
to
talk
about
is
that
sick
architecture
is
making
changes
for
a
long
time.
We've
done
a
lot
of
talking
and
not
as
much
stuff,
and
so
today,
I
want
to
kick
off
by
talking
about
some
of
the
changes
that
were
trying
out
in
sick
architecture
to
make
us
more
sustainable
and
healthy,
and
all
of
that
good
stuff,
because
I
think
it's
important
for
anybody
who
wants
to
come
engage
in
in
the
past.
C
If
you
came,
you
might
have
been
involved
in
debates
or
heard
debates
and
and
a
lot
of
the
active
work
wasn't
talked
enough
about,
and
so
we're
highlighting
more
of
that
and
I'm
going
to
talk
about
what's
changing
and
even
how
people
can
get
involved
in
that,
and
so
in
reality
the
reason
we're
reinvasion
ik
architecture
is
because
there
were
things
we
could
do
better
right.
We
were
very,
very
centralized.
C
If
chase
did
this
wonderful
thing
where
he
actually
looked
at
the
different
sub
projects
and
then
looked
at
the
number
of
people
involved
and
being
active
in
all
of
it?
It
came
down
to
about
nine
total
people
doing
most
of
our
work
and
some
of
those
people
were
approaching
burnout,
and
so
there
are
better
ways
to
handle
that
in
to
scale
it.
We
don't
have
a
leadership
succession
plan
right
because
we
don't
have
enough
people
there
doing
a
lot
of
things
and
the
lack
of
pipeline
for
new
people.
C
It's
almost
like
you
get
into
some
of
those
leadership
positions
and
then
you
hold
on
to
them
and
we're
not
building
up
that
next
set
of
people
and
and
of
course,
we
had
a
little
bit
of
a
failure
to
make
decisions,
because
the
default
was
to
not
make
a
decision
which
is
stagnant
and
we
would
sit
there.
Having.
Maybe
debates
were
at
the
end
of
it.
C
We
did
not
have
clear
outcomes
and
so
we're
working
to
to
fix
that,
because
that's
a
problem,
and
so
we
revisited
what
is
the
purpose
of
sake
architecture,
and
this
is
taken
from
the
Charter.
We
maintain
and
involve
the
design
principles
of
kubernetes
and
provide
a
consistent
body
of
expertise
to
ensure
the
architectural
consistency
over
time
and
so
by
having
that,
with
a
small
set
of
people
doing
a
whole
lot
of
work.
C
We're
not
able
to
do
that
effectively
enough,
and
so
we
change
things
up
and
we
started
with
the
project
values
and
a
lot
of
this
that
I'm
going
through
Jase
put
together
in
a
wonderful
presentation.
He
gave
to
say
architecture
a
little
while
ago,
but
you
really
pulled
us
into
to
the
project
values
and-
and
as
the
link
here
says,
this
is
the
whole
kubernetes
community,
not
just
sake
architecture,
and
here
we
pulled
out
three
of
the
values
distribution.
This
kind
of
makes
sense.
C
We
build
distributed
systems
having
nine
people
centralized
doing
a
lot
of
the
work
doesn't
really
do
that
inclusion,
you
know,
is
better
than
exclusion,
and
that
means
including
a
whole
lot
more
people
and,
of
course,
evolution.
We
evolved
the
design
of
kubernetes
and
it's
come
a
long
way
in
the
last
couple
of
years.
C
We
kind
of
need
to
evolve
sick
architecture
to
get
better
at
all
of
the
things
we
need
to
do
so
I'm
going
to
break
down
each
of
these
in
a
little
bit
more
detail
for
distribution,
we
want
to
move
from
centralized
gatekeeping
to
documented
guidance
right
so
way.
You
don't
have
to
track
people
down
to
necessarily
get
keep
everything
to
make
sure
everyone
who's
doing.
Something
is
following
the
right
patterns.
It's
documented
it's
easy
to
find
and
it's
clear.
C
C
Leadership
is
earned
and
we
want
to,
you
know,
call
out
those
leaders
and
look
at
the
people
who
are
doing
certain
bits
of
work
and
rewarding
that
and
a
great
way
to
see
who's
got
the
authority
and
responsibility
for
something
is
to
look
in
the
owners,
files
and,
of
course,
work
on
those
owners
files
over
time
to
make
sure
the
right
people
are
in
that.
We
are
active.
A
lot
of
our
topics,
we're
now
going
to
start
doing
on
our
mailing
lists
or
in
the
appropriate
caps.
C
Because
in
the
meetings
when
we
go
and
talk,
that's
happened
in
a
certain
time
zone
with
certain
people
who
come-
and
you
know,
there's
lots
of
folks
who
are
in
other
parts
of
the
world
who
may
be
able
to
give
great
insights
but
can't
make
our
meetings.
And
then
there
are
people
who
like
to
take
time
and
think
things
through
not
have
something
just
show
up
at
a
meeting
and
be
talked
about
and
when
they
think
things
through,
they
can
give
fantastic
feedback
and
build
on
each
other.
C
And
we
want
to
have
those
opportunities
and
include
those
people
and
their
ideas
in
those
conversations.
And
so
that's
one
of
the
things
that
we're
going
to
start
to
do
so
the
cigar
context.
Our
mailing
list
is
going
to
become
much
more
important
and
so
will
the
conversations
on
the
caps,
and
we
want
to
focus
on
solving
the
requests
that
come
in
to
Sagarika
texture
and
actually
giving
it
an
actionable
output
and
clearly
documenting
that
to
the
people
involved.
C
C
So
what
have
we
done
in
all
of
this
because
I
talked
about?
What
we
want
to
do
here
are
some
of
the
things
we've
actually
done
so
far
in
the
process
we
transferred
the
cap
process
to
sick
p.m.
that
actually
just
happened,
formerly
even
though
we'd
been
talking
about
it
for
a
while
and
so
sig
p.m.
is
going
to
take
on
evolving.
That
process.
We
updated
our
charter
to
reconcile
with
the
new
path.
C
We
moved
our
meetings
to
every
other
week
because,
if
we're
actually
doing
a
whole
bunch
of
work
and
then
reporting
out
on
it,
it
turns
out,
we
don't
have
to
get
together
and
talk
face
to
face
nearly
as
much.
We
can
use
mailing
lists
and
things
like
that.
We've
scheduled
follow-ups
to
help
us
with
the
transition
tim
st.
C
Clair
is
going
to
come
and
help
us
talk
about
running
with
federated
sub
projects,
and
in
the
hour
after
this
one
Parris
Pittman
is
going
to
talk
to
us
about
mentoring
and
how
to
do
that
stuff
and
teach
us
four
wise
ways
here:
we're
going
to
start
building
these
sub
project
teams
up
and
we're
starting
the
API
review
shadowing
already
to
bring
people
in
and
teach
them
how
to
go
through.
That
process,
so
they
can
help
pick
up
some
of
that
work.
C
That
needs
to
be
done
so
this
is
this
is
some
of
the
practical
steps
we're
doing,
but
along
the
way
we
have
done
other
things
right.
So
I
can't
just
talk
the
whole
time
about
it.
When
we
talk
about
what
we've
been
doing,
I
do
want
to
touch
on
a
few
of
the
other
things
that
we've
been
doing
over
the
last
quarter
since
we
last
talked
to
you
and
granted.
In
that
time
we
had
December,
which,
like
everybody,
took
off.
C
If
you
look
at
the
stats,
you
just
see
this
trying
dip
in
there,
including
the
conference
coupe
con
cloud
native
con,
but
in
there
we
also
talked
about
how
we
work
on
untested
dart
code
and
our
guidance
for
that
is.
We
really
want
everything
to
be
tested
now,
that's
coming
in.
We
want
to
reduce
that
amount
of
dark
and
untested
code.
So
more
things
are
tested
to
give
us
a
better
signal.
C
Aaron
props
to
this
we've
talked
a
lot
about
caps
and
Aaron
put
forward.
We
talked
a
lot
about
it
and
Sega
architecture,
making
every
new
feature.
That
goes
into
kubernetes
114,
a
cap
with
upgrade
downgrade
and
test
plans
to
really
think
through
these
parts.
Aaron's
driven
a
lot
of
that,
but
a
lot
of
that
conversation
has
happened
in
Sega
architecture,
the
scope
of
kubernetes.
Where
does
kubernetes
end
so
other
things
begin
and
granted
there's
some
gray
area.
C
So
how
can
you
contribute?
So
there's
a
whole
bunch
of
you,
wonderful
folks,
here
in
community
meeting
listening
to
me
talk
about
all
of
this
stuff
and
we
really
do
want
to
onboard
people
into
roles
and
responsibilities
and
and
just
some
actual
fun
work
here.
At
least
I
think
it's
fun,
and
so
we've
got
three
sub
projects
and
here's
kind
of
what
we're
doing
and
looking
for.
If
any
of
these
are
interesting
to
you,
please
reach
out
to
me
or
one
of
the
other
co-chairs.
We
are
happy
to
help
onboard
you.
C
The
architecture
and
API
governance,
kind
of
deals
with
documenting
kubernetes
architecture
and
patterns
and
path
forward
there,
along
with
the
API
governance,
is,
is
everything
from
API
reviews
to
deprecation
policies
and
things
like
that.
We're
currently
working
on
a
shadowing
program
to
help
everybody.
You
know
to
help
onboard
new
people
to
this.
Also,
our
process
and
details
around
this
are
incredibly
well
documented.
So,
if
you're
interested,
you
could
go
to
the
community
repo
and
save
architecture
and
actually
see
what
it's
like
and
what
the
review
process
is
like.
C
You
can
look
at
our
Board
of
what's
in
the
review
process,
all
of
that
stuff,
but
if
you're
interested
in
in
shadowing
or
getting
involved
in
this
process,
please
let
us
know
we
can
help
you
with
that.
Then
there's
the
conformance
definition,
and
here
we
work
with
the
conformance
working
group
to
work
out
what
is
conforming
kubernetes.
We
hear
about
all
of
these
different
things
we
hear
about
k3s
and
all
these
other
projects
that
are
conforming
kubernetes.
What
does
that
actually
mean?
This?
C
Is
the
group
that
figures
that
out
and
it
they
document
it
and
they
work
with
the
people
who
do
the
testing
and
all
of
this
stuff
to
to
work
on
the
definition
of
conformance
and,
if
you're
interested
in
this?
This
is
a
group
that
meets
regularly
and
talks
through
this
stuff,
we're
happy
to
help
unboard
you
to
this
well
as
well.
C
So
if
you're
a
newcomer
and
you
don't
know
what
to
do
or
where
to
start,
this
is
a
place
you
can
contribute
and
we
don't
expect
early
anybody
to
know
how
this
works,
and
so
we
will
onboard
and
help.
You
learn
this
and
become
successful
in
being
part
of
this
and
then
our
third
sub
project
is
code
organization.
C
Are
you
interested
in
untangling,
kubernetes,
kubernetes
or
dependency
handling
and
all
that
stuff
in
vendor?
This
is
an
area
that
is
mostly
unstaffed
and
we're
looking
to
kickstart,
this
effort
and
looking
for
people
who
want
to
figure
out
what
the
tasks
are.
Where
should
we
go?
How
can
we
untangle
things
and
make
them
cleaner?
How
do
we
work
with
the
different
people?
Who've
got
different
processes
around
pull,
requests
and
changes
to
kubernetes
and
make
sure
those
processes
work
together,
as
well
as
cleaning
up
our
code
base.
C
If
you're
interested
in
helping
do
some
of
that
work
or
helping
to
kick-start
that
effort,
please
reach
out
and
we
will
help
get
you
set
up
and
empowered
to
do
so,
and
so
then
the
last
slide
is
here's
who
we
are
and
how
you
find
us.
If
you
want
to
get
involved,
here's
the
chairs
you
can
reach
out
to
any
of
us
on
it.
C
Here's
our
homepage,
our
slack
channel
our
mailing
list,
we're
happy
to
talk
to
you
in
any
of
those
places
to
try
and
help
get
you
involved
or
answer
questions
that
mean
talking
all
about
this
may
not
have
covered.
So
that's
it
I,
don't
know!
If
I've
got
time
for
questions,
I
did
talk
a
bit
today.
Oh
yeah.
B
A
I
just
wanted
to
point
to
dims
as
being
very
exemplary
of
that
behavior,
because,
though
he
does
not
have
a
chair
in
cig
architecture.
His
opinion
is
extremely
respected
because
he
has
showed
up
and
done
the
work
that
is
deemed
important.
The
other
point
I'll
just
emphasizes
the
part
of
this
discussion
came
about
because
it
seems
as
though
Sagarika
texture
was
turning
into
an
anti-pattern
of
a
clearinghouse
for
all
technical
decisions
whatsoever,
and
that's
not
the
goal.
A
D
Are
can
you
see
the
screen?
Yes,
sir?
Okay,
let's
start
with
what
we
did
the
last
cycle
with
the
out
of
tree
vSphere
cloud
provider,
we've
got
a
new
release
coming
up
at
the
end
of
this
month,
synchronized
with
114
we're
going
to
move
this
up
from
a
label
of
alpha
to
a
label
of
beta
and
the
new
feature
that
will
be
in
this
upcoming
version
is
support
for
availability
zones.
D
D
Finally,
we've
already
added
mini
cube
support
for
the
desktop
versions
of
VMware
hypervisor
fusion,
on
the
Mac
and
workstation
on
Linux
and
Windows,
and
these
are
available
now
in
the
latest
release
plans
for
upcoming
cycles,
we're
going
to
plan
to
move
that
out
of
tree
provider
up
from
beta
to
a
stable
production
release.
I,
don't
know
if
we'll
make
it
in
the
115
timeframe
or
the
one
after
that,
but
we're
looking
at
it.
D
Advancing
the
stability
and
feature
said
in
that
and
along
with
it
same
thing
for
CSI,
there
are
a
number
of
features
that
they
recently
bumped:
the
CSI
spec
to
1.1
and
they're
working
on
new
features
involving
snapshot,
volume,
resize
and
the
potentially
others.
So
the
plan
is
that,
as
we
move
towards
a
stable
release
of
that,
we
move
up
to
support
these
new
CSI
enabled
features,
and
then
the
cluster
API
is
going
to
track
the
general
pattern
of
what's
going
on
in
kubernetes
project
wide
with
cluster
API.
D
This
is
a
link
to
related
capsule
there.
In
the
deck
and
the
deck
is
linked
in
the
notes
for
this
meeting,
so
I'm
not
going
to
read
these
individually,
but
here
they
are
for
a
reference
related
working
groups.
There
are
meetings,
Wednesdays,
monthly,
real,
are
related
to
the
vSphere
cloud
provider.
There's
a
link
to
the
notes
and
agenda
there.
The
recordings
are
in
YouTube
cluster
API
also
has
recurring
meetings
with
links
to
the
notes
and
agenda
and
the
YouTube
videos.
D
How
can
how
can
you
contribute
to
this
group?
We've
got
a
couple
of
Help
Wanted
bugs,
unfortunately,
we're
still
working
on
getting
a
program
set
up
for
a
mentorship
program,
but
we
don't
have
anything
in
that
category.
Now
our
meeting
meets
immediately
after
this
one.
There's
a
link
there
to
the
agenda
notes
we
are.
The
sig
chairs
have
decided
that
at
this
upcoming
meeting,
we're
going
to
suggest
moving
it
off
by
a
week
simply
because
we've
been
in
conflict
with
sig
architecture
and
I
know.
D
Some
of
the
people
would
like
to
go
to
the
sega
architecture,
zoom
meetings,
but
haven't
been
able
to
so
we're
gonna
propose
that
we
slip
slip
a
week,
our
cycles,
you
see
there
the
two
chairs
myself
and
Fabio
and
links
to
our
slack
channel
mailing
list.
If
you
want
to
join,
that's
it
for
my
presentation.
If
anybody's
got
any
questions.
B
B
Alright,
that
looks
like
a
no,
so
I'm
gonna
reschedule
are
some
quick
announcements.
The
new
contributor
summit
site
is
live
at
the
URL
I've,
stuck
that
in
the
notes
on
the
registration
is
supposed
to
go,
live
by
the
end
of
day
today,
so
keep
an
eye
out
for
that.
We
also
have
a
new
channel
in
Slough.
If
you
didn't
notice
like
it's
back,
we
sent
a
mail
to
the
dev
list
and
we
have
a
new
channel
on
slack
called
hash
PR
reviews
to
help
people
find
reviewers.
B
A
So
look
for
a
PR
from
me
to
start
the
rest
of
that
process
shortly.
I
know
there
were
some
discussions
about
this,
while
I
was
out
the
release
team
meeting
on
Monday,
but
really
looking
forward
to
seeing
the
next
team
come
together.
Clare
has
been
phenomenal
throughout
this
whole
process
and
I
can't
wait
to
see
what
she
does
with
the
next
release.
Awesome.
A
B
Great
anyone
else
before
I
move
on
to
shadows
all
right
code.
Ranger
would
like
to
shout
out
to
Catherine
for
kicking
butt
on
slack
automation,
to
help
out
the
admin
team
and
mr.
Bobby
tables
would
once
a
second
bat
seriously
big
shout
out
to
Catherine
for
the
stuff
she's
doing
make
slack
a
better
place
for
us.
So
if
you've
noticed
Catherine
has
implemented
a
feature
in
our
slack.
Now,
if
you
see
a
comment,
that's
bad
and
it
should
be
flagged.
B
B
Aaron
would
like
to
shout
out
to
anneal
it
one
two
three
for
his
investigative
work
on
what
appears
to
be
going:
1.12
bug
and
Liggett,
just
in
Santa,
Barbara
and
dims,
for
the
continued
assists
and
the
golang
team
for
helping
us
get
to
go
one
dot
12.1
in
time.
Sorry
and
a
shout
out
to
Mike
arpaia
for
setting
up
and
running
the
EU
friendly
release
team
meetings,
stepping
in
so
much
whenever
Aaron
isn't
available
and
keeping
on
top
of
all
the
things.
B
So
as
usual,
if
we
have
a
hash,
shoutouts
Channel,
if
you
see
someone
going
above
and
beyond
the
call
of
duty,
please
feel
free
to
mention
them
there,
so
that
we
can
give
the
proper
props.
Since
we
had
a
signature
well
and
the
demo
not
show
up.
We
are
way
early
on
time,
so
I'm
going
to
give
you
28
minutes
back
any
last
comments
before
we
call
it
and
awesome,
everybody
will
see
everyone
next
week.
Thank
you.
Bye.