►
From YouTube: Cloud Foundry CAB call recording 14th Oct 2021
Description
Recording from the Cloud Foundry Community Advisory Board call held on 14th October 2021.
Agenda:
1. Update about the CF-for-k8s SIG call ... scope, naming, etc.
2. We will get updates about the latest on the CF community working groups and new governance model.
3. Demo by Peter Wagner of datev.de about Cloud Foundry Sidecars.
A
C
B
The
meeting
to
meet
that
need,
and
so
it'll
be
focused
around
a
broader
set
of
topics
that
are
anything
in
that
space
and
it's
also
going
to
be
a
place
to
talk
about
a
newly
approved
working
group.
That
is
the
cloud
foundry
on
kubernetes
space.
So
that'll
be
anyone
that
wants
to
talk
about
the
new
projects
that
we've
spun
up
the
cfk's
api
and
cf
gates
controllers,
which
are
like
a
new
interpretation
of
the
cloud
foundry
api
on
kubernetes,
as
well
as
any
other
projects
that
people
want
to
bring
up
or
any
other
topics.
B
B
B
B
A
Get
into
the
technicalities
of
what
the
different
models
are,
but
we
need
to
be
aware
against
that.
There
are
six
different
working
groups
and
each
of
whom
are
responsible
for
like
a
particular
area
of
the
cloud
foundry
tool
itself
and
the
six
groups
that
the
six
working
groups
that
we
have
are
the
app
runtime
interfaces.
A
There's
a
pocket,
centric
working
group
there's
something
for
service
management,
there's
a
vulnerable
vulnerability
management,
sorry
and
there's
one
for
community
experiences
as
well.
We
have
stefan
today
on
the
call.
So
stefan
do
you
want
us
to
give
a,
or
do
you
want
to
give
a
few
updates
to
the
team?
Sorry
to
pick
on
you,
but
stefan
is
a
member
of
the
tvoc,
and
I
think
it's
great
if,
if
he
can
share
some
information
about
the
current
status
of
these
working
groups,.
C
Yeah
welcome
from
my
side,
I'm
stefan
I'm
one
of
the
members
of
the
toc,
I'm
work
with
sap
and
there
are
two
more
important
working
groups.
One
is
the
application
runtime
working
group
that
takes
over
diego
and
yeah
everything
for
the
container
management
and
a
foundation
working
group
that
takes
over
of
bosch
uaa
and
a
number
of
other
infrastructure,
closer
components
that
did
not
fit
so
well
somewhere
else.
C
What
we
are
currently
doing
is
that
we
write
down
charters
for
the
different
working
groups.
You
can
see
them
in
the
community
github
project
and
find
the
list
of
all
github
repositories
that
and
assign
them
to
the
different
working
groups
and
collect
the
initial
approvals.
That
means
basically,
the
committees
formally
but
yeah.
That's
the
steps
that
are
currently
running
and
then
each
work
group
will
get
a
workload
bleed
and
that
isn't
responsible
to
run
the
daily
business
within
the
working
group.
C
Once
it
is
established
for
all
the
working
groups,
then
the
hope
is
that
this
new,
let's
say
more
open,
more
pr
driven
process
of
collaboration
can
get
into
action,
and
one
critical
point
is
here
to
get
sufficient
approvals.
The
name
is
chosen
by
intention
because
they
have
the
responsibility
to
review
and
judge
on
incoming
prs
and
to
take
care
that
the
different
projects
are
actually
open
for
everybody.
C
Of
course,
such
a
working
group
is
never
finished
and
it
can
change
over
time
and
it
will
change
over
time.
There
are
still
some
working
groups
in
progress.
For
instance,
the
up
runtime
interfaces
working
group
is
not
yet
finalized,
but
I
assume
that
this
will
happen
within
the
next.
Let's
say
two
weeks.
A
That
meeting
again
is
also
available
on
the
calendar
and
we
receive
some
status
updates
about
the
different
efforts
that
they
are
taking
on.
I
think
the
like
stefan
mentioned,
there's
like
a
bunch
of
working
groups
that
are
kind
of
sort
of
you
know
finalized
for
whatever
that
means,
but
I
think
it
it
checks
the
boxes
for
what
is
like
required
at
a
minimum
to
get
the
working
groups
going
and
getting
some
of
the
work
started,
and
I
guess
there's
like
one
working
group.
A
I
think
the
community
experience
working
group
that
that
is
still
the
one
that
that
needs
to
see
a
little
more
participation
and
obviously
the
toc
is
aware
of
that
and
working
on
it.
So
yeah.
So
just
wanted
to
share
that
information
on
this
call
as
well,
and
you
know
if
folks
have
any
feedback.
You
know
you're
welcome,
to
share
them
to
take
a
look
at
the
repo
I've
posted
it
on
the
chat
and,
if
folks
want
to
interact
directly
or
comment
on
the
repos
and
the
issues
or
the
prs
that
are
there.
A
D
Hello,
everyone
glad
to
be
here,
I'm
peter.
I
work
at
dartf
eg
in
germany,
it's
a
big
software
company,
one
of
the
biggest
in
europe,
and
we
develop
software
for
tax
lawyers,
auditors
and
their
clients,
and
that's
mainly
software
about
text
declarations,
bookkeeping,
accounting
and
so
on,
and
we
have
our
own
data
center
and
we
use
cloud
cloud
foundry
as
our
platform
as
a
service
system.
A
Right
so
I
had
seen
a
tweet
from
one
of
peter's
colleagues
about
them
doing
a
presentation
on
site
cars
and
them
showcasing
internally.
I
guess
about
you
know
some
of
these
nifty
cloud
foundry
features
and
I
reached
out
to
them
asking
them
if
they
wanted
to
demo
some
of
this,
and
you
know
basically
do
a
show
and
tell
get
some
feedback.
A
What
have
you
and
so
here
again
was
kind
enough
to
introduce
me
to
peter
who
actually
gave
the
talk
and
in
turn
peter
was
happy
to
share
some
of
his
work
with
us
and
basically
showcase
what
they're
doing
and
how
they've
been
taking
advantage,
in
particular
about
side,
cars
and
cf
and
stuff
so
yeah
peter?
Why
don't
you
kick
things
off
and
show
us
the
good
stuff.
D
D
D
D
Those
processes
has
to
communicate
so
it's
an
inter-process
communication
between
sitecar
and
your
business
application
cloud.
Foundry
offers
several
opportunities.
How
to
communicate
between
both
one
is.
You
can
use
the
file
system.
Well,
for
example,
the
service
can
write
into
a
file
and
the
sitecar
can
read
this
file
and
do
something
with
the
data
written
in
there.
D
D
D
In
this
example
8083,
and
if
a
request
comes
in
the
cloud,
foundry
will
forward
the
request
to
the
airport
process,
and
then
the
process
can
do
its
business
functionality
and
if
it
needed
the
site
car
features,
it
can
send
a
call,
a
request
to
the
sidecut
process
using
localhost
and
the
port.
The
site
color
is
listening
to.
D
D
Yes,
first
of
all
left,
I
forgot
there
are
two
possibilities:
how
you
can
deploy
a
sidecar
to
cloud
foundry.
The
first
is,
you
can
create
your
own
custom,
build
pack,
and
then
this
build
pack.
You
can
integrate
the
sidecar
so
that
everyone
who
uses
your
build
pack
has
automatically
the
sidecut
deployed
into
this
application.
D
D
The
demo
has
this
example:
that's
of
how
how
we
started.
First,
we
have
our
demo
up
with
our
business
functionality,
that's
running
and
it's
as
on
own
application
in
cloud
foundry.
Then
we
needed
some
security
features
like
an
authentication
and
we
first
decided
to
deploy
another
app
in
cloud
foundry.
A
security
app
and
the
security
app
is
called
by
the
our
external
clients.
D
B
D
D
So,
as
you
can
see
here
in
our
cloud
foundry
space,
there
are
two
apps
running
a
demo:
sidecar
standalone
and
a
cf-cap
security
standalone
that
are
the
these
two
applications
quickly.
Show
you
what
they're
doing
it's
pretty
simple.
The
demo
sidecar
standalone
has
a
greeting
api.
If
you
send
a
request
to
it,
you
can
see
here
it's
returning
hello
world.
D
When
we
use
the
securities
standalone
app
with
the
greeting
api
without
authentication,
it
will
return
fully.
Oh,
yes,
it's
http
status401
on
autoresize.
If
I
add
a
typical
http
authority,
authorization
with
username
and
password
in
this
example,
then
it
will
return
hello
user.
So
it's
called
the
demo
app,
which
returns
the
string
and
in
between
is
the
authentication
that
the
the
user
is
allowed
to
access.
It.
D
D
I
prepared
already
a
new
manifest,
including
a
sidecar,
and
what
you
have
to
do.
There's
several
things.
First
of
all,
there's
a
sidecar
configuration.
So
with
this
you
can
add
one
or
more
sidecars
to
be
deployed
with
the
application.
Sidecast
has
always
a
name
has
some
memory
requirements
and
a
process
type.
In
my
example,
the
process
type
is
web.
There
are
a
few
others
you
can
use
for
my
example
because
of
the
http
endpoint,
it's
a
web
and
that's
some
more.
D
C
D
We
had
some
difficult.
It
was
difficult
to
find
the
correct
path
for
the
java
runtime,
but
we
weren't
able
to
find
any
documentation
what
you
have
to
use.
So
it
was
a
bit
of
research
to
make
to
be
made
to
find
this
right
one
and
to
get
it
work
working
another
tricky
part
of
using
sidecast
was
http
is
are
the
ports
in
this?
In
the
example
you
can
see,
there
are
several
two
part.
D
D
D
D
D
D
Now
the
manifest
will
be
applied
to
the
application,
then.
Finally,
we
have
to
push
the
application
to
cloud
foundry
there's
another
thing
you
have
to
do.
First
before
you
can
push
the
application,
it's
all
one
single
deployment,
so
you
have
to
integrate
all
your
sidecars
into
the
artifact
you're
deploying
for
your
application.
D
D
D
Looks
there
are
two
things
yeah
interesting.
As
I've
mentioned,
there
will
be
two
jvm
processors
running
and
here
you
can
see
I'm
using
spring
boot.
There
are
two
spring
boot
well
icons
and
text,
one
for
the
sidecar
and
one
for
the
application
in
the
locks
you
can
see
which
processor
creates
this
lock
line.
D
D
Well,
my
look
farts
yes
here.
My
look
for
my
two
lock
lines:
one
of
the
security
side,
car
prints
out
the
username
and
one
of
the
process
of
the
app
which
says
hello.
I
I'm
in
the
you're
in
the
hello
world
controller,
so
you
can
see
both
with
the
request.
Both
processes
were
attached.
First,
the
security
sidecar
and
afterwards
the
dim
web.
D
D
It
will
look
into
the
app
folder
there
we
can
see.
The
blue
folders
are
the
artifacts
of
the
demo
app
and
the
security
jar
that's
lying
in
the
upholder
tube.
That's
a
side
car
though,
if,
if
we
deploy
our
other
side,
cars,
for
example,
on
nginx
or
so
there
will
be,
the
nginx
configurations
will
be
also
in
this
add
folder,
and
that's
the
reason
why
we
have
to
integrate
the
sidebars
into
the
the
artifact
of
the
application
now
that
it
will
be-
and
this
pla
be
deployed
in
this
place.
D
We
have
a
look
at
the
parts
like
this,
then
we
can
see
the
process
with
id.
53
is
listening
to
part
8083.
So
that's
our
application,
the
demo
application
and
we
can
see
that
process
id
40
has
a
connection
established
to
this
port.
Now,
that's
the
connection
between
the
sidecar
and
our
applications.
There
you
can.
These
are
really
to
parts
into
process
communication
using
localhost
between
sidecar
and
application.
E
B
D
E
E
D
A
Thanks
peter,
I
think
that
was
a
very
good
demo
quite
informative.
At
least
I
learned
like
a
bunch
of
things.
Thank
you
for
you
know,
taking
the
time
and
making
all
of
the
effort
to
you
know,
share
this
information
with
your
team
and
with
the
larger
cf
community
as
well.
So
I
really
appreciate
you
doing
that,
but
overall,
thank
you.
Everyone,
I
guess
for
attending
the
call.