►
From YouTube: Kubernetes UG VMware 20230406
Description
April 6, 2023 meeting of the Kubernetes VMware User Group. Coverage of recent cloud provider, and CSI storage plugin update releases.
Discuss future of this group.
Discuss possible physical "face-to-face" user meeting in Amsterdam during KubeCon timeframe.
A
Also
I'm
going
to
lightly
cover
a
physical
event,
we're
planning
to
have
at
kubecon
in
Amsterdam,
starting
about
two
weeks
from
now.
Also,
if
there's
anybody
who
wants
to
add
anything
to
the
agenda
or
if
not,
we
can
just
go
free-form
birds
of
a
feather
on
anything.
Anybody
wants
to
talk
about
at
the
end
of
this
I
did
prepare
a
deck.
What
I'm
about
to
present.
So
let
me
post
a
link
to
that
deck
in
the
chat,
and
it's
also
in
the
meeting
notes.
B
A
Okay,
here's
the
agenda
well,
I
just
discussed
it,
but
I'll
move
on
so
we'll
start
with
the
CSI
driver.
There
is
a
new
three-point
o
release.
It
came
out
fairly
recently.
The
feature
set
is
that
the
primary
feature
is
it
supports
version
1.26
of
kubernetes,
just
a
caveat
here.
I
know
that
the
company
datadog
conducts
an
annual
survey
on
kubernetes
usage,
and
their
survey
indicated
that
both
the
most
popular
current
kubernetes
release
deployed
is
1.21,
which,
interestingly
enough,
has
reached
ends
of
life
in
terms
of
service.
A
Nonetheless,
there
are
plenty
of
people
using
it.
This
new
CSI
driver
supports
a
minimum
of
1.24.
So
should
you
be
on
an
older
release?
What
am
I
want
to
say
here
is
something
you
might
use
in
the
future,
but
you
shouldn't
attempt
to
deploy
it
now,
because
it
isn't
supported
on
those
older
kubernetes
releases
prior
to
1.24.
A
The
key,
what's
new
features
are
that
it
supports
the
the
CSI
plug-in
supports
use
across
multiple
vcenter
instances.
Now
that
multiple
vcenter
instances
thing
is
potentially
valuable,
but
I
want
to
caution
you
that
it
it's
mainly
a
thing
that
you
do
for
availability
or
performance.
In
other
words,
getting
volumes
provisioned
more
quickly
or
going
to
larger
scale
such
as
going
Beyond,
10
000
block
volume
deployments,
but
when
it
says
multiple
vsphere
instances,
you
do
have
to
be
cautious
because
you
are
not
allowed
to
to
share
volumes
across
these
vcenter
instances.
A
What
I
mean
by
that
is
that
if
one
vcenter
happens
to
provision
the
volume
and
the
compute
that
is
consuming,
it
is
on
a
different
vcenter
that
will
not
work.
So
the
multiple
vcenters
can
be
used
to
host
components
of
the
what's
going
on
with
the
storage
plug-in,
it's
more
a
scale,
performance
availability
thing
you
do
have
to,
and
there
you
you
do,
have
to
be
careful,
and
there
are
mechanisms
in
kubernetes
to
allow
you
to
do
this
to
not
attempt
to
cross
share
volumes
across
the
B
Center
volumes.
A
It
also
added
GA
support
for
raw
block
volume.
So
these
are
the
situation
where
you've
got
an
app
like
mongodb
or
Cassandra
that
prefer
to
consume
their
storage
in
the
terms
of
a
raw
device
Mount,
rather
than
a
a
file
mount
for
purposes
of
accelerating
performance
and
then
the
last
two
bullets
you
see
there
are
support
for
the
xfs
file
system,
as
well
as
support
for
volumes
consumed
in
Windows.
A
These
are
the
issues
resolved
in
that
300
I,
don't
know,
I'm
not
going
to
read
them
to
you,
you
can.
You
can
read
them
off
the
PowerPoint
slide
and
if
you
get
this
deck,
all
of
those
things
that
you
see
here
in
blue
are
actually
links.
That
would
lead
you
to
the
actual
issues.
So
you
can
learn
more
about
these
resolved
issues
there
there
are.
There
are
not
any
other
patch
releases
to
the
older
ones.
Those
were
still
last
updated
a
while
ago,
and
we
covered
these
at
the
meeting
in
December.
A
So
I've
got
a
link
here
to
that
deck
from
December,
as
well
as
those
patch
releases
that
kind
of
have
happened
in
the
last
six
or
nine
months.
So,
if
you're
on
those
older
ones,
there
is
nothing
new
so
far
this
year,
but
if
you
haven't
updated
for
a
long
time,
this
information
that's
linked
here,
might
still
be
valuable
to
you
in
terms
of
known
issues.
I
just
looked
them
up
this
morning.
The
last
update
to
the
issue
list
was
three
days
ago
and
I.
A
A
Moving
on
to
the
cloud
provider
release
1.26.0
came
out,
and
once
again
this
is
support
for
kubernetes
1.26.
There
are
a
recent
doc
updates
at
the
link
shown
here.
There
is
a
current
issue
on
that.
The
latest
issue
update
occurred
on
February,
the
1st.
You
can
go
to
the
GitHub
repo
to
go,
learn
more
about
that.
A
They're,
unlike
the
CSI
storage
plug-in,
there
have
been
recent
patch
releases
in
March
to
just
about
all
the
cloud
providers.
The
those
items
here
that
you
see
referring
to
a
bump
in
the
golang
package
is
related
to
a
security
issue,
a
cve
and
you
can
click
on
those
links
in
the
deck
to
learn
more
about
those.
There
were
some
other
fixes
put
associated
with
these
updates
to
the
cloud
provider
as
well.
A
So
these
are
the
main
feature
updates
to
that.
One
points
to
1.26
release
vsphere
credentials
from
a
Secrets
directory
I
do
want
to
shout
out
shout
out
that
we
did
get
a
number
of
contributions
from
non-vmware,
employee
contributors,
Kenichi
homichi
from
NEC
Brian
topic
from
sap
and
Michael
McEwen
from
Red
Hat,
and
it
looks
like
there
are
a
number
of
valuable
feature
ads.
B
A
The
issues
resolved
on
this
list
so
once
again
click
on
the
links
to
drill
down
to
learn
more
the
docs.
For
this
now
we're
moving
on
to
updates
to
vsphere
itself,
specifically
here,
vsphere,
8
and
I'll
get
to
vsphere
7
next,
but
the
vsphere
8
docs
were
updated
on
February
the
7th
you
can
follow
the
link
here.
There
was
an
8.00
C
update
to
the
binary
and
I'm,
giving
you
the
release
notes
here.
A
That's
a
vcenter
update.
The
last
vsphere
update
was
just
a
little
older
than
that.
That's
Beast,
vsphere
8.0
B,
and
you
can
download
it
there
and
find
the
release
notes
if
you
still
haven't
moved
on
to
vsphere
8.
These
are
somewhat
older
blog
posts,
but
Cormac
Hogan
gave
a
good
summary
of
what's
different
in
vsphere
8
and
vsan
8
versus
7..
A
A
Moving
on
to
vsphere
7
update,
3
release,
L
the
release,
notes
for
that
were
just
updated
yesterday
and
the
actual
download
is
a
little
older
than
yesterday.
I
think
it
was
sometime
in
February
but
go
examine
those
release,
notes
to
learn
more
about
that
I
think
there
may
have
been
some
of
those
things
covered
in
the
release,
notes
that
are
in
the
realm
of
security
patches.
A
So
it
might
be
advisable
to
go.
Do
that
using
the
usual
methods
that
are
built
into
vsphere.
So
that's
the
end
of
my
slideshow.
Let
me
stop
sharing
getting
back
to
the
agenda.
We've
got
a
a
couple.
Other
things
going.
One
is
the
future
of
this
group,
so
this
group
came
about
under
a
kubernetes
project.
Charter
I
think
that
this
occurred.
A
Although
I
think
they
are
valuable
to
the
people
who
continue
to
attend
and
they've
never
spread
across
the
other
Cloud
providers,
so
they've
expressed
a
desire
that
maybe
this
group
get
green
twilighted
in
the
June
time
frame.
So
that
means
next
month
might
be
the
last
month
and
if
users
want
to
have
sort
of
an
equivalent
in
order
to
attempt
to
build
a
bigger,
critical
mass,
also,
an
observation
that
many
of
the
things
discussed
here
technically
are
not
the
kubernetes
project
itself,
but
collateral
things
like
load,
balancers
Ingress.
A
The
latest
activity
on
Ingress
is
actually
the
Gateway
API,
which
is
recognition
that
baby
Ingress
wasn't
standardized
as
much
as
it
should
be.
So
the
cncf
has
come
up
with
a
new
spec
called
the
gateway
API
that
takes
on
the
same
role
as
Ingress,
but
has
tighter
specifications
so
that
they're
perhaps
less
variations.
You
know
people
have
complained
that,
as
you
move
from
one
Cloud
to
another,
things
go
on
with
Ingress
that
make
you
non-cloud
native,
where
things
that
would
work
on
one
Cloud
don't
work
on
another
anyway.
A
The
bottom
line
is
that
there
is
a
suggestion
that
we
should
perhaps
commission
an
on-premise
User
Group,
not
under
the
auspices
of
the
kubernetes
project,
but
under
the
auspices
of
the
cncf
I.
Don't
know
that
we'll
be
able
to
do
that
by
June.
If
June
is
the
last
meeting
of
this
group,
but
if
there's
interest,
we
could
perhaps
attempt
to
do
this
on
a
longer
term.
A
So
we
attempted
to
have
discussions
of
this
at
kubecon
in
Detroit
last
year,
but
we
got
a
slot
for
that
discussion
on
Friday
the
last
day
of
the
conference
at
4,
30
pm
and
heart.
Only
five
people
showed
up
so
I,
don't
know
that
we
actually
even
got
a
representation
of
the
effort
of
Kenyans,
particularly
opinions
of
actual
users,
so
Brandon
I
know
you're
here
now.
A
A
A
You
know
no
everybody
in
the
cncf
is
caught
up
with
kubecon
itself
in
Europe.
At
this
point,
so
nothing's
likely
to
move
but
I
know
that
there's
a
person
with
the
cncf
who
is
in
charge
of
community
Taylor,
who
has
expressed
an
interest
in
trying
to
make
this
happen,
but
we
we're
going
to
have
to
get
a
few
people
on
the
user
side
to
you
know
so
that
we
don't
start
holding
meetings
and
nobody
shows
up.
I
know
when
we
started
this
group.
A
It
was
you
and
somebody
from
T-mobile
who
were
initial
participants.
The
person
at
T-Mobile
moved
on
to
a
different
job,
so
he's
kind
of
dropped
off
the
map-
Joe
Cersei,
but
maybe
we'll
see
if
we
can
get
them
involved
with
his
current
employer
and
I,
don't
think
we'll
manage
to
resolve
anything
on
that
topic
during
this
meeting.
A
Moving
on
the
other
thing
I
put
on
the
agenda,
was
the
upcoming
kubecon
event
itself
in
Europe
there
there
is
an
organization
itq
that
has
had
people
show
up
in
to
this
meeting
in
the
past.
They're
they're,
not
here
today,
but
they
are
going
to
be
sponsoring
a
physical
user
meeting
in
Amsterdam
they're,
calling
it
a
v-beers
event.
A
A
B
A
A
A
So
if
you
wanted,
if,
if
any
of
that
in
that
deck
was
of
Interest
I
I
posted
the
link
to
the
notes,
I
can
post
the
direct
link
to
the
shared
deck
as
well.
If
you
want
that,
let
me
see.
Let
me
just
do
it
regardless.
So
it's
in
the
chat
stream
and
then
maybe
we'll
just
close
this
thing
a
little
early.
A
Okay,
well
and
unless
there's
additional
stuff,
what
thanks
for
joining
and
I
do
anticipate
holding
a
meeting
next
month
just
to
announce
the
twilighting,
if
nothing
else,
so,
if
you're,
there
I'll
see
you
there
and
if
there
is
anything
you
want
to
bring
up
there,
go
for
it
if
it.
If
there
is
anything
relevant
to
this,
that
happens
at
kubecon
I'll
give
a
brief
presentation
on
that
as
well.
So
I
guess
we
can
leave
it
at
that,
but
once
again
feel
free.