►
From YouTube: Community Standup: 5/12/20
Description
These community standups are open to all interested in participating in the NRE Labs project. Information on the schedule for these standups as well as how to join can be found here:
https://discuss.nrelabs.io/t/about-nre-labs-weekly-standups/84
A
Anyway,
should
we
start
the
meeting.
A
B
Cool
well
same
say,
you
know
for
me,
I,
like
I
said
the
was,
was.
Let
me
look
back
actually
a
week
and
see
what
was
going
on
last
week
may
5th.
B
Yeah,
okay,
so
yeah.
A
Apart
from
me,
taking
a
kind
of
break
but
the
rest
yeah,
it
was
about
the
curriculum
and
a
new
stage
and
a
bit
of
yeah.
B
Yeah,
the
the
last
the
last
version
of
antidote
that
I
published
was
a
minor
fixes
and,
and
I've
been
I've,
been
sort
of
watching
production
since
then,
just
to
make
sure
that
it's,
you
know
more
stable
than
oda,
6.0
was,
and
it
looks,
looks
pretty
good,
so
I'll.
Let
this
bake
for
a
little
bit
see
see
what
what
kind
of
stuff
I
can
gather
more
than
more
than
likely.
B
B
B
You
can't
use
that
if
you
need
to
contribute
an
image
like
if
you,
if
your
lesson
needs
a
new
image
like
you've,
got
to
contribute
that
first
and
that's
in
the
docs,
but
never.
Nevertheless,
it's
still
a
slightly,
not
ideal
way
of
doing
things
and
I'd
like
to
make
it
so
that
you
can
contribute
an
image
as
part
of
that
pipeline
and
get
it
automatically
built.
The
problem
is
how
to
do
that
in
a
secure
way.
A
B
But
I
haven't
made
any
progress
on
that
and
probably
won't
for
at
least
another
week.
I'm
I've
just
got
some
other
things
I
need
to
take
care
of,
but
so
yeah
next
next
week
next
week
or
two,
I'm
probably
just
in
unblocking
mode
so
like
if
somebody
needs
to
you
know,
do
something
and-
and
I
I
need
to-
I
need
to
provide
guidance
or
or
some
assistance,
if
I'm
able
to
anyway,
then
that's
kind
of
what
I'll
be
prioritizing
in
terms
of
working
on
anything.
B
A
So
in
between,
maybe
I
hope
that
my
student
and
me
we
can
make
some
progress
and
propose
a
pr
on
self-medicate
to
make
it
easier
to
address
those
ingress
configuration
issues
that
we
are
struggling
with.
Yeah.
B
Sure
one
thing
one
thing
that
I
I
may
actually
do
if,
if,
if
you,
I
think,
I
think
so,
there's
there's
actually
a
bunch
of
reasons
why
I
think
it
would
be
a
good
idea
to
host
self-medicate
on
the
native
ports
so
instead
of
doing
the
30
000
so
on
and
so
forth.
I
know
you
ran
into
some
issues
with
that.
There's
also
issues
with
that
in
terms
of
routing
routing
ingress
requests
in
general.
B
So
I,
if
you,
if
you
try
to
load
in
self-medicate,
if
you
try
to
load
any
lessons
that
have
an
http
presentation,
they
don't
work
at
all
and
the
reason
the
reason
for
that
is
the
shoot.
I
have
an
issue
I
have.
I
think
I
have
an
issue
opened
on
this.
Maybe
I
don't.
I
can't
remember,
but
anyway
the
ingress
the
way
that
ingresses
work,
they
don't
respect
ports
like
you
can't:
okay,
yeah.
C
B
Have
to
do
you
have
to
include
port
because
that's
part
of
it,
but
the
ingress
definition
won't.
Let
you
do
it
so
like
ngenx,
I
believe,
will
do
it
like
it's
built
into
the
software
of
ingenex
that
you
can
but
of
course,
the
ingress
control
the
end.
The
enginex
ingress
controller
needs
you
to
pass
that
via
the
you
know,
the
ingress
definition
and
then
the
kubernetes
api
server
won't
accept
port
in
the
in
the
route
as
you
define
the
ingress.
So
it's
sort
of
a
catch-22.
B
Me
as
though
the
underlying
load
balancer
will
support
it,
but
the
ingress
definition
won't
won't
support
it
and
so
you'll
never
be
able
to
get
that
rule
in
which
means
that
the
only
way
that
we
could
possibly
fix
this
is
by
hosting
the
ingress
controller
on
a
standard
port
and
the
way
that
you
would
do
that
is
you
would
you
would
basically
tell
the
when
you
for
the
deployment
of
the
ingress
controller
itself?
B
You
would
say:
hey
use
the
host
network.
You
know
for
this
pod,
basically
at
which
point
any
any
any
port
that's
listed
in
the
in
the
deployment
or
really
in
the
pod
template
for
that
deployment
you
it
would.
It
would
just
simply
use
those
ports
as
long
as
they're
available.
If
they're
not
available,
then
it
would
break,
but
it
would
be
the
only
thing
running
on
those
ports
and
then
and
then,
of
course,
you
would
not
need
a
service.
B
You
wouldn't
need
a
service
at
that
point,
because
the
pods
just
listening
directly
on
the
on
the
hosts
networks
and
there
would
be
no
service
needed,
so
you
wouldn't
do
anything
with
like
node
ports
or
anything
like
that.
It
would
just
be
that
the
pod
is
listening
directly
on
the
host
network.
Anyway,
I
I've
been
mulling
around
things
to
improve
the
the
load
balancing
configuration.
B
Clearly,
one
of
the
things
that's
necessary
is
is:
is
that
is
that
host
network?
You
know
basically
setting
host
network
to
true
and
then
making
that
the
way
forward.
I
think
it's
a
lot
easier
now
that
we're
standardizing
on
top
of
vagrant.
So
instead
of
you
know,
you
can
always
run
self-medicate
locally
if
you're
running
linux,
but
that's
not
really
something
that
I
want
to
support.
B
I
mean
self-medicate
in
general,
isn't
really
something
I
want
to
support
going
forward,
but
but
certainly
certainly,
if
we
do,
if
we
do
support
it,
it's
in
a
very
constrained
sort
of
like
this
is
the
way
that
we
intend
for
it
to
work
and
and
clearly
that
that
that
option
is
is
in
a
vagrant
machine
which
makes
it
a
little
easier.
B
I
think
to
say
you
know,
listen
on
the
host
network,
because
we
can
control
that
network
and
say
like
this
is
this
is
basically
the
you
know
the
only
service
that
needs
port,
80
and
port
443
on
the
on
the
figure
machine
anyway,
I
think
a
pr
to
make
that
change
should
be
pretty
straightforward.
I
could
take
a
stab
at
it
or,
if
you'd
like
I
can,
I
can
you
know
you
if
you.
A
I
I
I
must
say
that
you,
you
kind
of
lost
me
in
the
explanation
that
you
just
gave
about
the
topology,
because
I'm
still
yeah,
I
I.
B
A
Mean
I'm
not
so
good
at
networking,
that's
okay,
the
base
and
then
there's
the
terminology
of
of
kubernetes.
That
is
not
always
obvious
to
sure
yeah.
B
B
Yeah
yeah
it,
I
think
I
think
it
would
be.
It
would
be
simpler
for
a
lot
of
reasons.
Yeah
anyway,
we
can.
We
can
continue
this
conversation.
A
I
think
it's
it's
interesting
to
to
be
able
to
compare
what,
how
the
guys
at
the
eclipse
chair,
setting
up
things
and
and
and
what's
in
on
our
platform
because
well
there
was
already
the
authentication
and
the
persistent
storage
and
stuff
like
that.
But
beyond
that,
I
see
some
really.
A
That
could
be
an
interesting
aliens
somehow
if
the
two
could
be
deployed
on
the
same
platform,
so.
B
Yeah
yeah,
I
think
I
think
you're
right,
the
I
don't
know
if
you
saw
there
was
a
recent
announcement
last
week.
I
think
github
had
their.
B
Where
they
did
where
they
did
yet
another
web
browser
based
ide,
so
clearly,
clearly
it's
it's
the
it's
clearly,
it's
the
it's
a
common
thread
that
people
are
pulling
on
these
days.
A
So
I
I
guess
there
is
also
some
interest
there.
So
I
don't
know
if
you
have
contacts
with
them,
because
nc
ball
and
stuff
seem
to
be
some
joint.
B
Sure
yeah,
I
don't
know
anything
about
it.
I
will
but
I'll
start
poking
around.
A
Anyway,
would
she.
B
Well,
the
current
video
series
is
totally
caught
up
with
what's
published
in
the
curriculum.
So
probably
my
next
step
is
to
finish
the
git
lesson.
I
have
one
more
stage.
I
want
to
build
that
that
takes
the.
I
didn't
really
get
into
any
practical
like
like
here's,
how
we
you
would
use,
get
remotes,
I
kind
of
just
set
the
stage
for
it,
because
there's
there's
a
lot.
B
You
got
to
learn
about
like
setting
up
authentication
and
whatnot,
so
I
want
to
make
sure
that
was
covered,
but
in
terms
the
end
game,
for
this
lesson
frankly,
has
always
been
helping.
People
understand
the
I
mean
it's,
it's
not
really
a
deep
dive.
To
be
honest,
there
are
plenty
of
other
courses
that
like
go
into
like
crazy
detail
and
like
what
the
anatomy
is
of
the
dot
get
directory,
and
all
that-
and
I
I
didn't
want
to
do
any
of
that.
B
And
so
the
end
game
for
me,
for
this
lesson
is,
is
basically
like
okay,
so
you
keep
hearing
about
github
and
you
see
that
all
these
projects
are
on
on
on
github
and
you
and
you
you
want
to
know
more
about
it
and
maybe
how
to
get
involved
here
are
the
things
that
you
need
to
do
to
get
to
to
get
to
that
point.
So
obviously,
90
of
that
is
like
the
basics
of
git,
but
the
end
point
there
is,
you
know,
understanding
the
flow
of
like
contra.
B
You
know
opening
a
pull
request
or
forking
a
repository,
opening
a
pull
request
and
then
pushing
to
your
fork
and
then
opening
a
pull
request
from
there.
How
do
I
keep
a
pull
request
up
to
date,
so
you
know
basically
adding
two
remotes
pulling
from
the
upstream
one
and
then
pushing
to
your.
C
B
Things
like
all
that
stuff
all
that
workflow.
That
is
not
obvious.
If
you
don't
have
tangible
practical
experience,
that's
the
last
sort
of
stage
I
want
to
build.
I
don't
know
if
you've
looked
at
it,
but
that
that
that
that
github,
clone
that
I'm
using
in
the
lesson
now
is,
is
dope.
That
thing
is
cool,
it's
so
small,
so
I've
actually
been
wanting
to
build
this
lesson
for
a
long
time.
B
Probably
since
the
beginning
of
the
project,
the
problem
was
well
two
problems,
one
of
which
was,
I
didn't,
have
http
presentations
at
the
beginning
of
the
project,
so
so
believe
it
or
not.
The
get
lesson
is
one
of
the
reasons
I,
where
I
worked
on,
adding
http
presentations
nice.
B
What
I
wanted
to
do
was
add
a
github
or
a
git
lab
rather
get
lab
container,
which
is
the
only
the
only
the
only
piece
of
software
that
I
knew
of
at
the
time
that
that
I
could
package
into
the
project
and
into
a
lesson,
and
so
I
kind
of
always
just
assumed
it
was
going
to
be
git
lab
for
a
long
time
and
it
sat
it
sat
in
a
pr
like
you
know,
dead
basically
for
a
year,
because
I
was
trying
to
figure
out
how
to
get
get
lab
running
and
it
took
a
long
time.
B
Gitlab
is
very
like
heavy-handed.
It's
like
a
it's,
not
a
it's,
not
a
very
light
piece
of
software
and
anyway
I
as
I
was
as
I
was
re
as
I
was
effectively
adding
all
of
these
additional
stages.
To
the
get
lesson
I
got
closer
and
closer
to
the
end
where
I
was
like.
Okay,
I'm
going
to
have
to
fix
this
get
lab
lesson,
and
I
got
to
that
point.
C
B
I
came
across
get
tea
and
then
I
get
tea
is
a
hard
fork
of
some
other
project
that
I
don't
remember,
but
they're
similar
you.
A
Know
10
years
ago
or
yeah,
probably
those
days
I
was
very
active
in
the
forges
community.
You
know
I
was
a
maintainer
for
fusion
forge,
which
was
a
fork
of
g-forge
and
stuff
like
that.
So
oh.
B
A
I've
been
away
for
for
some
time,
but
it's
nice
that
it
has
evolved
and
there
are
a
few
opportunities
for
self-hosting
and.
B
A
It's
like
what
you
could
have
used,
but
without
the
web
interface,
so
for
the
initial
creation
it
would
have
been
command
line.
B
A
Like
filling.
C
A
Form
and
submitting
interesting
so
no
project
and
it
works
with
public
keys
anyway,
so
it
helps
generating
a
new
key
and
and
copying
and
all
the
rest
is
the
same.
It's
a
nice
tool,
but
maybe
gt,
integrates
key
to
light
somehow.
B
B
What's
you
know
behind
the
scenes
they
mostly
care
that
they
can
then
reuse
that
learning
to
apply
themselves,
which
is
probably
going
to
be
github.
B
Okay,
well
anything
else.
This
week.
B
Yeah
I
was
looking
earlier.
Yeah
seems
to
be
the
two
of
us.
I
will
I'll
ping
I'll
ping,
those
folks
that
joined
not
last
week
but
the
week
before,
because
we
had
a
flurry
of
folks
join
I'll,
just
ask
if
they
have
any
questions
if
they
want
to
go
through.