►
Description
Join Christian Hernandez, GitOps Extraordinaire, for a journey through how to achieve GitOps in any number of ways. The occasional Red Hatters and special guest will join us too.
A
Good
morning,
good
afternoon,
good
evening,
wherever
you're
hailing
from
welcome
to
another
episode
of
the
get
ops
happy
hour
here
on
openshift
tv,
I
am
chris
short.
I
am
the
executive
producer
host
with
the
most
here
on
openshift
tv,
I'm
joined
by
two
of
my
favorite
red
hatters,
shubik,
bose
and
christian
hernandez
christian.
You
want
to
tell
us
what
we're
get
opting
today.
B
A
D
B
E
C
B
Yeah,
so
I'm
very
excited
today
today
today
we
have
a
special
guest,
shubik
bose
right,
so
we're
talking
about
the
openshift
get
ops
operator
right.
So
it's
kind
of
something
we've
been
teasing
a
little
bit
something
we've
been
working
on
in
the
background
we've.
You
know,
we've
we've
done
a
lot
in
this
conversation
in
this
channel
conversations
about
like
cd,
really
like
a
lot
about
cd
right.
We
touched
a
little
bit
about
ci.
B
You
know
I
actually
plan
to
do
a
show
about
tecton
and
you
know
ci
in
general,
but
we've
been
kind
of
focusing
on
cd,
but
you
know
how
how
does
red
hat
and
how
are
we
going
to
bring
like
the
story
together
right
because
it's
like
it's
ci
cd
devops
is
ci
cd
driven,
and
so
so
we
have
red
hat
right.
We've
we've
we've
developed
this
operator
right.
That
kind
of
just,
I
think,
tells
the
story
completely
right
kind
of
like
from
the
developer's
perspective.
It's
like
okay.
B
Well,
like
you
know
me
as
a
developer.
How
do
I,
you
know,
get
started
with
ci
cd
in
a
get
ops
fashion
right
and
so
I'm
very
happy
to
introduce
shubik
bose
here
shubik
can
do
like
a
little
introduction
and
then
maybe
we'll
kind
of
get
rolling
into.
What
is
this
openshift
get
ops
right,
so
it's
kind
of
like
it's
analogous?
Is
it
techton?
Is
it
argo?
Is
it
something
else
so
anyways
I'll?
Let
you
take
it
away.
Shubik.
E
B
E
Yeah,
so
I
kind
of
helped
with
that,
and
I
think
today
the
plan
is
to
show
you
the
opportunity
operator
and,
as
christian
mentioned,
we're
trying
to
bring
the
whole
story
together,
because
nobody
does
cd,
only
there's
ci
as
well
and
well.
We
all
need
something
to
manage
cluster
configurations,
something
to
manage
app
delivery
configuration.
So
I'm
going
to
quickly
jump
in
share
my
screen
and
show
you
some
of
the
things
that
we've
been
doing
with
the
openshift
get
ops
operator.
E
E
B
E
B
E
E
Your
getup
story
includes
openshift
pipelines,
argo
cd
and
a
bunch
of
these
tools,
and
I
want
to
ensure
that
they
are
all
installed
out
of
the
box.
So
when
you
install
openshift
get
ops,
you
had
an
instance
of
argo
siri
installed
for
you
and
we're
going
to
go
deeper
into
it,
but
outside
that
it
actually
brings
you
automatically
your
openshift
pipelines
operator
as
well.
Why?
Because
reasons
if
you're
storing
stuff
in
git,
you
need
to
have
ci
for
them,
there's
no
way
you
can
get
away
with
that.
E
B
E
B
E
While
we
do
that,
there
are
a
few
things
from
the
command
line
tools.
Also
you'll
see
when
you
go
to
this
ui
you'll
see
something
called
the
groups
application
manager.
That,
basically,
is
it's
gonna
show
up.
So
let's
install
the
operator
and
it's
gonna,
let
you
download
a
cli
to
bootstrap
and
we're
gonna
get
to
that
shortly,
but
what
I
told
you
all
the
things
that
quickly
happened.
Let
me
quickly
get
to
the
screen.
E
E
Well,
I'm
not
going
to
bore
you
with
bill
configures,
but
you
all
know
that
the
build
convex
is
the
concept
and
openshift
that
lets
you
build
images
and
there's
a
global
configuration,
that's
present,
which
only
cluster
admins
are
supposed
to
mess
with.
So
let's
say
I
need
a
specific
build
configuration
to
be
applied.
E
Like
let's
say
this
is.
If
you
see
this
is
a
configure
openshift.io
build
object,
this
is
a
clusterscope
object
which
needs
to
which,
which
configures
your
build-
config
proxy
and
a
bunch
of
different
things.
That's
definitely
not
something
which
your
developers
would
put
your
hands
on,
but
your
cluster
admin
would
love
to
go
and
modify
this.
B
E
Yeah,
so
so
so
what
I
just
did
here
is.
Let
me
is
that
I
ensure
that
I
could
apply
this
cluster
configuration
of
using
rbo
cd,
I'm
going
to
try
something
else.
Now.
Let's
say
I
go
in
and
just
pick
up
an
example.
That's
been
created
by
the
nice
folks
of
from
hive.
There
is
a
global
res
there's
a
global
configuration
for
modifying
your
registry
details
also-
and
this
is
kind
of
interesting-
this
makes
sure
that
you
can
only
pull
from
kuwait.
E
E
E
D
E
B
E
Yeah,
so
you
could
see
that
you
know
you,
you
could
potentially
use
this
instance
for
configuring.
Your
you
know
build
config
your
image
registries,
but
then
you
may
not
want
to
use
this
instance
for
applications,
because
hey
really
good,
but
if
I'm
just
trying
to
deploy
a
quarkus
application,
you
may
want
to
do
it
differently,
not
with
this
one,
so
yeah,
but
before
we
jump
from
there,
let's,
let's
quickly
see
a
few,
our
back
things
that
have
been
done
for
you
behind
the
scenes.
E
Now,
if
I
had
to
peel
the
layers
and
show
you
where
it
is
to
install
I'm
sure
you
would
be
interested,
it's
basically
a
new
namespace
for
openshift
getups,
where
this
cluster
config
rw
cd
goes
in
and
sets,
and
you
might
find
it
interesting
to
know
hey.
You
know,
I've
heard
a
lot
about.
You
know
argo
cd
needing
cluster
admin
to
do
faster,
config
things
which
I'm
kind
of
want
to
highlight
today
that
hey.
We
know
that
if
you
give
cluster,
I
mean
it
can
do
everything.
E
E
Yeah
scope
it
down,
so
you
can
break
your
cluster
to
only
such
an
extent
and
not
to
a
large
extent.
So,
let's,
let's
see
what
are
the
you
know,
roughly
the
cluster
rules
that
have
come
with
this,
and
this
is
where
things
will
go
a
bit
interesting.
So
I'm
gonna
go
here
and
see
hey,
you
know
what?
Typically,
if
you
go
to
openshift
docs
here
are
the
things
that
they
say.
E
You
know:
you're
gonna
have
to
modify
your
cvo
operators,
you're
gonna,
do
user
management,
you're
gonna
do
console
customization
as
an
admin
you're
going
to
set
up
cluster
roles
and
you're
going
to
modify
storage.
So
what
this
cluster
config
argo
city
does
is
out
of
the
box.
It
says:
hey
you're
allowed
to
do
these
things,
because
that's
what
cluster
admins
do
all
the
time
and
that's
why?
I
think
a
good
point
to
not
question
here
is
it's
kind
of
important
to
highlight
it
to
users
that
you
know
this
is
a
cluster
config.
E
If
you're
handing
on,
if
you're
handing
the
keys
to
somebody
you've
got
to
be
careful
because
yeah
yeah
exactly
this
is
a
powerful
one,
so
yeah!
So
in
chart,
yes,
we
are
going
to
ensure
that
there
is
a
cluster
config
out
of
the
box
and
that's
because
almost
everyone
wants
an
argo
cd
to
configure
the
clusters
initially.
So
that's
the
first
step,
while
we've
done
that
now,
for
obvious
reasons,
let's
say
chris
says:
hey,
you
know
what
I've
got
a
team
of
node.js
developers
who
want
to
deploy
other
applications.
E
B
E
E
So
what
I'm
gonna
do
is
I'm
gonna
say
hey.
You
know,
of
course.
This
is
an
important
point
to
make.
Now
is
that
you're,
using
the
argo
cd
controller,
argo
city
operator,
controller,
the
upstream
one
which
you've
been
seeing
for
a
while
in
community
operators
in
the
openshift
crops
operator
as
well,
which
means
we
we
we
haven't
cloned
code,
we
haven't
split
out
code.
E
If
this
argument
operator
is
an
open
shift
and
the
same
maxi
operator
may
be
for
kubernetes
as
well
for
non-approach
kubernetes,
it's
some.
If
it's
an
open
shift,
it
should
tap
into
the
openshift
niceness
and
it
should
feel
like
it's
well
integrated
so
that
we're
gonna
do
apart
from
just
the
upstream
operator,
yeah.
A
B
D
E
Yeah
totally,
I
think,
did
so
in
general.
The
idea
is,
you
know,
I'm
pretty
sure,
no
matter
what
knobs
you
have
on
argo
cd
people
are
gonna,
say,
hey
just
get
me
my
own
article
cd
and
I'm
gonna
mess
with
it.
I'm
gonna
do
whatever
I
want
with
it
before
I'm
ready
to
actually
jump
into
something
more
serious.
So
this
is
probably
where
you
could
say:
hey.
You
know,
chris,
you
have
a
team
of
five
people.
Why
don't
you
go
ahead
and
you
know
get
your
own
rpc,
so
I'm
going
to
log
in
here.
E
E
Totally
so,
let's,
let's
take
a
sample
app
from
the
upstream
community.
Try
to
let
me
first
create
a
project
for
christian,
so
christian.
This
is
where
you
know
applications
relevant
to
you
are
supposed
to
live.
So
let
me
try
to
go
and
deploy
there
from
the
argo
city
which
chris
just
got
for
himself.
Sorry,
christian,
krishna,
pretty
confusing
names,
but
that
sounds
similar.
But
yes,.
E
E
D
B
E
It's
namespace
yeah,
exactly
right,
so
so
now,
let's
see
how
does
christian
allow
chris
to
deploy
things
into
christian's
namespace?
So
let
me
take
a
quick
look
at
so
this
is
the
service
account.
Don't
worry,
this
will
all
start
making
sense.
I
go
to
all
bindings
and
christians,
so
christian
is
not
going
to
say
hey.
You
know,
I'm
hereby
going
to
allow
chris
to
deploy.
E
E
E
E
B
E
Yeah,
I
think
that's
right,
I
think
in
general.
We
want
to
ensure
that
you
know
there
are
these
clear
roles
in
the
industry.
Somebody
could
be
a
kubernetes
administrator,
but
that
same
person
may
not
be
your
argusidia
administrator
right
right,
yeah
same
person
may
not
be
your
git
ops
administrator.
So
chris
is
the
get
ups
administrator,
but
not
the
kubernetes
administrator
in
this
case,
and
therefore
we
want
to
ensure
that
we
do
not.
E
A
B
B
A
B
B
B
True
right
and
that's
actually
not
necessarily,
you
know
kind
of
peeking
behind
the
curtain
a
little
bit
I'll
I'll,
give
you
kind
of
our
even
our
own
sres
right,
our
sres
for
openshift
dedicated
they're,
broken
up
into
teams.
They're,
it's
not!
You
know
yeah
each.
You
know,
there's
not
one
team
that
does
the
whole
stack.
It's
each
team
does
an
individual
piece
and
they
work
together
and
I
think
that's
just
basically
shows
you
the
power
of
of
having
something
like
a
feature
rich
our
back
to
allow
certain
this,
this
communication
right.
B
E
Going
to
do
is,
let's
say
you
know
chris
comes
and
says:
hey,
you
know,
you
know,
I'm
all
good
with
the
cluster
now.
Can
you
get
me
cluster
config
powers,
I
said
hey.
I
could
give
you
that.
Can
you
still
get
your
own
cluster
for
that?
I
said
sure
we
could
do
that,
but
then
I
could
kind
of
show
you
here.
That
here
is
my.
E
Let
me
kind
of
check
here,
so
I'm
going
to
create
a
new
application
here
and
I'm
going
to
try
some
of
the
old
stuff
which
I
was
trying
here.
Let's
say
I
want
to
try
and
go
and
do
some
console
customization
and
when
I
say
I
and
chris
is
doing
this-
let's
say
chris
wants
to
do
some
console
customization.
E
B
E
E
Yeah,
so
I
think
here's
the
thing
rachel:
I
try
to
go
and
modify
your
classes.
A
cluster
scope
object
here
and
it
fails
and
that's
the
point
trying
to
make
is
you
know
the
same
operator
is
giving
you
two
different
rpc
instances,
one
that
lets
you.
Do
it
the
one
in
the
openshift
layer
of
namespace
and
one
that
does
not
let
you
do
it
so
where's
the
magic.
So
where
do
you
turn
those
knobs?
E
You
would
either
turn
these
knobs
in
the
cr,
but
well,
if
you
can
turn
the
knobs
and
see
how
everybody
can
do
that.
So
the
idea
is
that
we
kind
of
add
to
a
global,
allow
list
that
which
namespaces
are
allowed
to
have
clustered
config,
argo,
cds
and
again,
I
don't
know
why
somebody
would
need
10
cluster
common,
big
advertisers.
But
let's
say
you
need
it
just
so
you
need
it.
Yeah.
E
E
E
E
E
Right
so
there
you
go.
I
added
that
to
the
list
of
namespaces
allowed
to
have
cluster
config
and,
like
I
said
this
is
not
something
that
you
should
be
able
to
do
through
the
argo
cdcr,
especially
because
yeah,
then
anybody
would
be
able
to
get
a
clustered
biography.
That's
totally
wrong.
This
is
something
that
is
highly
privileged
and
should
be
done
by
the
administrator.
Only.
C
B
E
D
E
If
it's
a
namespace
like
if
I'm
trying
to
annotate
the
you
know
chris's
space,
when
chris
would
be
able
to
do
it,
and
I
need
to
figure
out
how
to
how
that
shouldn't
happen,
yeah,
I
think
in
general.
We
want
to
ensure
that
and
again
yes,
christian,
I'm
totally
taking
feature
requests
on
live
tv,
okay,.
E
Yeah
yeah,
so
I
think
one
one
feature
request
which
we
off,
which
which
we
often
get
is
that
hey?
You
know
you
just
made
me,
you
know,
show
me
cool
things
on
the
ui
and
then
finally,
you
throw
me
down
some
yaml
to
update
this.
That's
so
uncool,
but
then
I
think
in
in
short,
we're
gonna
have
this
config
options
displayed
in
the
ui
as
well,
so
which
means
yeah
yeah.
You
should
be
able
to
go
here,
go
to
subscription
and
edit
that
in
here
that
should
be
possible.
E
That's
the
next
couple
of
releases!
So
now
that's
done
and
again
this
is
a
little
admin
stuff
here,
but
I'm
still
going
to
show
you.
If
you
see
this
is
my
graphs
operator
pod,
which
is
running
and
if
you
go
in
here
and
just
to
show
you
why
this
one
yeah.
So
this
is
a
good
ops
operator
for
that,
I'm
just
doing
and
I'm
an
admin,
so
I'm
allowed
to
do
end.
So
this
is
where
you
might
see
a
boring
stuff.
I'll
show
you
so.
E
Did
that
you
could
see
it
got
into
the
environment?
This
is
probably
a
cool
olm
feature
that
you
should
probably
learn
about
in
case
you're.
Not
aware
of
that,
you
would
actually
have
your
subscription
object
hold
somewhere
for
environment
variables.
It
really
helps
with
the
fact
that
the
one
who
wrote
the
operator
may
not
be
the
one
who
is
running
that
operator.
Of
course,
yeah
the
customers
and
customers
should
be
able
to
pass
environment
variables
to
your
operator
if
needed,
and
that's
something
that
we
took
you
know
made
use
of
here.
E
D
E
B
A
B
E
E
Chris
told
me,
oh
chris
told
me
about
the
phone
that
he's
just
going
to
other
he's
just
going
to
allow
only
io
images
on
the
cluster,
but
now
I
see
he's
also
allowing
docker
hub
images,
which
is
fine,
but
he
didn't
say
that
at
that
time
saying
hey,
you
know
what
that
doesn't
match
with
what
you
asked
for,
and
I'm
going
to
take
this
part.
Take
these
powers
away
from
you,
which
means
you
still
get
an
argo
cd
because,
like
you
said,
there's
no.
C
E
Don't
get
to
do
cluster
configuration
with
it,
you
can
apply
things
in
that
namespace
right
yeah.
I
think
with
that,
I'm
going
to
quickly
jump
over
a
few
areas
around
ci
and
cd,
I'm
going
to
show
you
some
of
the
cam
cli,
the
graphs
application
manager
cli,
I'm
going
to
walk
you
through
some
of
the
directory
structure,
guidances
that
we've
been
coming
up,
but
before
I
get
to
that,
it's
slightly
different
topic
question:
is
there
something
that
you
want
to
add?
Are
you.
B
D
B
E
D
E
B
E
Think
to
to
quickly
add
to
that,
since
you
brought
the
topic
up,
I'm
going
to
get
to
it
before
I
jump
to
the
next
topic
on
this
is.
It
is
important
for
you
know,
from
from
from
an
openshift
perspective,
and
even
and
even
from
a
you
know,
get
ops
user
perspective,
it
is
probably
important
to
be
granular
as
much
as
possible.
Yes,
which
means
I
would
rather
be
happy
if
I
saw
a
list
of
hundred
different
permissions
here
than
one
permission
saying,
that
cluster
admin
right
yeah.
A
E
E
So,
which
means
and
again
I'm
taking
fiji
I'm
taking
feature,
I'm
taking
feature
requests
here,
which
means,
if
you
put
on,
if
you're,
an
admin
out
there,
and
if
you
think
that
there
is
a
very
common
cluster
configuration
task
you
do,
which
is
not
represented
by
the
permissions
here.
Yes,
you
could
definitely
go
and
create
your
own
cluster
role
and
create
a
binding
to
ensure
it
works.
E
But
the
idea
is
that
we
want
to
ensure
that
we
optimize
for
the
80
percent
case
in
a
way
that,
yes,
if
there's
something
that
people
are
doing
out
there,
we
need
to
take
we
need.
We
need
to
be
cognizant
of
that
and
ensure
that
the
cluster
configuration
rules
that
we
ship
out
of
the
box
should
be
aware
of
it.
So
I
still
remember,
I
think
I
think
gerald
had
told
me.
You
know
what
I
do.
E
You
know
it's
not
just
him
like,
like
we've
invested,
I
think
in
the
openshift
project
a
ton
to
ensure
that
you
should
be
able
to
customize
the
console
and
that's
a
very
you
know,
cluster
admin
thing,
and
that's
where
you
know
we
need
the
feedback
from
you
folks
who
are
watching
this
is
that
what
are
the
other
things
other
than
you
know?
Storage,
our
back
console,
config
users,
oil
operators,
that
that
you
do
on
a
day-to-day
basis
on
your
cluster
that
you
think
should
be
shipped
out
of
the
box.
B
E
And
and
then
we're
going
to
ensure
that
you
know
in
the
future
releases,
you
should
be
able
to
take
stuff
out
of
here
as
well.
Not
only
add
things
to
this
list,
so
just
just
to
ensure
that
if
you
want
to
do
our
you
know
cluster
config,
you
should
not
be
left
with
a
huge
list
of
things,
even
though
this
is
still
better
than
star
star.
E
Right,
so
with
that,
I
think
I'm
going
to
quickly
summarize
what
we
did
here
today
before
I
show
some
of
the
getups
application
manager.
What
we've
been
doing
a
quick
summary.
You
know
if
you're
joined
late
or
you
know
if
you've
not
been
following,
because
there's
a
lot
of
information
out
here,
yeah.
B
B
E
Installed
openshift
get
ops,
you
get
a
free
argo
cd
for
cluster
config,
which
your
cube
batman
has
access
to
out
of
the
box.
Everyone
on
the
cluster
can
get
their
own
rv
series,
not
that
we
recommend
that,
but
we
know
people
want
it.
You
can
get
your
own
argo
cd,
but
you
can
only
play
within
your
name
space.
That's
all
you
can
do
there
unless
you,
unless
somebody
allows
you
to
mess
with
their
name
space.
E
E
Yeah
and
then
yes,
if
somebody
else
wants
to
cluster
quantity,
argo
city
call
up
your
cube
admin,
cluster
admin
and
your
cluster
admin
is
going
to
ensure
that
you
know
you're
set
for
a
new
cluster
configuration
because
that's
serious
business
and
we
don't
want
to
ensure
everybody
on
the
cluster-
has
that
with
that,
I'm
quickly
going
to
jump
into
some
of
the
two
limiting
that
we've
been
building.
So
all
good.
E
E
B
Well,
it's
it's
funny!
I'm
a
big
fan
of
customized.
We
talked
about
customize
on
the
show
right,
oh
yeah,
all
the
time
I
love
customized,
but
yeah.
So
there's
there's
this
like
you,
can
kind
of
get
yourself
into
a
loop
right
with
customize
a
little
bit
right
because
it's
like
you
go
okay
like
because
you
want
to
kind
of
unravel.
What's
going
on
here
right
so,
like
you
follow,
you
know,
someone's
you
know
base
to
another
base
to
another
base
to
another
right
like
and
you.
E
D
B
D
E
E
But
then
I
I
think,
there's
one
other
aspect
which
I'd
like
to
address,
which
is
that
a
lot
of
engineers
are
probably
not
going
to
be
great
with
customized,
and
that's
that's
for
obvious
reasons.
They
spend
the
time,
writing
quarkx
applications.
They
spend
their
time,
writing
node.js
applications
and
I
do
not
want
to
burden
them
with
writing
customize,
for
example,
yeah.
Oh.
B
E
E
B
Yeah
well-
and
you
know
I
I
think
everyone
has
the
same
opinion.
I
did
at
first
when
first
working
with
customize,
it's
like
the
direction
structure
should
be
com
completely
simple,
but
then,
as
you
work
with
it
and
as
your
deployments
get
like
more
complex,
your
director
structure
gets
more
complex
and
all
of
a
sudden
you're
like
how
did
I
get
here?
B
I
wanted
this
to
be
simple
right,
but,
like
there's
it's
you
know
you're
right,
like
you
want
to
strike
a
balance
between
simplicity,
but
at
the
same
time
you
want
to
be
like
flexible
and
powerful,
and
that's
just
essentially
just
translates
to
you
know
directory
trees.
It
just
does
it's
just
the
nature
of
how
customize
works.
B
E
E
Right,
so
something
on
that,
you
know
we
we
want
to
ensure
that
you
don't
have
something:
that's
simple,
not
powerful,
rather
simple,
yet
powerful,
so
which
means
that
it.
It
typically
gets
pretty
hard
for
a
lot
of
team
members
for
a
lot
of
engineers
who
are
probably
node.js
engineers
quarters
engineers
who
don't
want
to
spend
time
writing
a
bunch
of
family.
They
can,
but
that's
not
what
this
should
be
doing.
E
So
do
you
want
to
ensure
that
we
provide
a
directory
structure
out
of
the
box
that
you
can
put
in
your
stuff
in
and
you're
good
to
go.
So
this
is
one
such
sample
directory
structure,
I'll,
show
you
the
cli
and
shortly
but
in
general.
The
idea
is
that
you
want
to
ensure
everything
should
be
get
optified,
sorry
for
using
that
term,
but
in
general
I.
C
E
Right
so
so
someone
said
hey,
you
know
what
I
have.
This
cool
thing
called
techtown
and
I
want
to
ensure
that
should
also
live
on
my
git.
So
I
got
all
my
you
know,
tecton
objects,
and
they
can
also
be
pretty
complex
on
my
kid
repo
managed
by
someone
we
can
come
to
it,
who
that
someone
is
but
the
goal
is
that
it
has
to
be
managed
from
get
as
well
simpler,
complex,
doesn't
matter
in
the
get
ops
world.
E
What
we're
saying
is
that
if
there's
any
ammo
that's
going
to
be
applied
to
the
cluster
and
be
turned
into
a
resource
on
openshift
that
should
be
living
on
git.
So
in
this
case
we
have
your
ci
pipeline
configuration
living
on
git
and
being
driven
off
gate.
You
have
your
argo
cd
living
of
kit
and
you
have
your
environments,
which
I
just
showed
you
now.
How
do
you
get
to
this?
I
think
that's
the
bigger
question
that
we
typically
have
that.
Where
do
we
start?
E
B
Well,
yeah,
so
I
think,
and
then
also
it's
very
it's
very
important
to
distract
that
balance
right,
because
we
have
our
opinionated
approaches,
but
also
when
you're
starting
from
zero,
like
I
want
to
start
with
at
least
a
you
know,
plausible
good
practice
right
like
so.
It's
like
what
is
the
best
practice,
because
I
don't
want
to
start
from
zero.
So,
like
you
gotta
find
you
know
you
gotta.
In
order
to
form
your
opinion,
you
gotta
see
others
opinions
first
right,
so
I
think
so.
B
So
I
think
you
know,
although
being
opinionated
is
good,
because
you
know
it
comes
from
the
the
fact
of
of
experience,
also
like
when
you're,
when
you're
starting
from
zero,
you
need
to
start
somewhere,
so
that
and
I
think
that's
what
the
cli
tool
attempts
is
like
having
some
sort
of
same
best,
best
practice,
totally
yeah.
I.
E
D
E
Don't
want
to
do
that
yeah,
so
I
think,
with
that,
I'm
going
to
quickly
give
you
an
overview
of
the
cam
cli
that
we've
been
building
and
which
you
saw
you
could
actually
go
and
download.
After
installing
the
operator
from
your
command
line
tools,
you
could
download
the
get
ops
application
manager.
In
short,
it's
called
cam
from
the
console
itself.
E
So
what
this
potentially
does
is
it?
It
basically
has
a
bunch
of
options
and
a
cool
interactive
mode
as
well.
To
take
some
basic
things
hey,
you
know.
I
want
this
source
code.
I
want
to
push
it
to
this
repository
and
I
want
to
ensure
they're
encrypted.
You
know
taking
five
or
six
pieces
of
information
and
basically
gives
you
this
repository,
which
everything's
set
up
so
which
means
within
minutes.
E
You
are
good
to
go
with
respect
to
getting
your
customized
setup,
getting
your
tecton
object
set
up
and
ensuring
that
you
know
all
your
rbo
cd
configuration
is
also
in
github
it's
in
gate
itself.
So
that's
what
the
get
ops
application
manager
does.
It's
under
heavy
development
at
this
point.
So
if
you're
watching
this,
I
request
you
to
go
and
try
it
out.
E
So
with
that,
I'm
gonna
probably
just
point
out
one
last
thing,
and
I
don't
have
a
demo
for
that
right
now.
Set
up
is
that
we're
gonna
ensure
an
open
shift,
console
that
if
you
have
a
github
application
manager,
bootstrap
repository
connected
to
your
openshift
cluster,
we're
gonna,
give
you
a
nice
visualization
of
the
different
environments
on
your
openshift
console
itself
and
that's
going
to
show
up
in
a
so.
We
had
that
for
a
while,
but
then
we
are
rebuilding
it
for
ga,
so
stay
tuned.
E
D
B
B
Yeah
yeah,
no,
I
think
I
think
it's
pretty
cool
and
I
think
what
what
what
I,
what
I
think
the
potential
for
the
for
for
cam
is,
is
really
cool.
So
someone
like
me
who
struggled
with
I
don't
know
shubik
if
you
you're,
probably
too
busy,
but
I
was
kind
of
ranting
on
some
of
these
channels
here
that
we
have
on
slack
about
how
hard
techton
is
to
wrap
your
your
mind
around
it
right.
B
Just
the
paradigm
of
tech
talk
but
pecton
tick-tock,
whatever
what
one
of
them's
popular
one's,
not
so,
but
but
I
think
the
the
tool
is
really
cool
because
it
kind
of
you
know
for
someone
like
me,
who
was
just
learning
you
know,
can
give
you
like
a
sane.
You
know
starting
point
right,
and
so
I
think
it's
it's
really
cool
has
a
lot
of
potential
like
I
can
bootstrap
and
have
techton.
I
can
have
argo.
B
I
can
have
my
applications,
you
know,
I
know
we
just
scratched
the
surface
of
this
operator.
You
know
you
can
incorporate
sealed
secrets
with
it.
You
know
you
kind
of
have
like
this
whole
workflow
built
around
the
the
the
get
ops
application
manager
right.
Cam
is
what
we
call
it.
I
guess
for
kubernetes
application
manager,
but
for
copyright
reasons
we
have
to
call
it
something
else,
but
but.
E
B
B
A
E
E
D
B
D
E
Other
thing,
oh
good,
we
are
good
to
try
to
ensure.
So
I
think,
while
we
are
on
this
topic,
I
think
between
tech
preview
and
ga,
there
are
a
few
things
that
we
want
to
ensure
you
know,
which
are
probably
not
super
visible
to
our
user,
but
we
still
want
to
have
in
this
whole
thing
that
we're
shipping
we
want
to
ensure.
E
Like
I
said,
we
have
a
very
solid
support
for
monitoring
on
openshift
with
the
clustering
module
stack,
that's
something
we're
going
to
try
doing
better
than
what
we
have
now
same
thing
with
cluster
logging
and
yes,
we're
gonna
ensure
that
you
know
you
have
a
streamlined
experience.
Why
you
know
you
use
openshift
get
offs
it
like.
E
I
said
it
should
not
look
like
you
need
to
read
a
book
after
installing
the
object,
yeah
yeah,
and
I
think
those
are
some
of
the
experience
improvements
like
you
mentioned
around,
ensuring
that
you,
you
get
to
see
more
in
the
openshift
console
as
well,
apart
from
thing
on
them
on
the
august
3
ui
in
the
native
view,
we're
going
to
have
that
yeah
and
in
general,
if
you're
watching
this,
I
think
the
interesting
bit
about
ga
would
be
they're
also
going
to
bring
in
application
sets
with
openshift
getups.
If
you
know.
B
That's
right,
yeah,
so
actually
yeah.
So,
let's,
let's,
let's
actually
put
that
in
the
chat,
and
I
can
actually.
I
actually
have
a
a
show
planned
just
right
talking
about
application
set.
It's
actually
the
the
topic
where
I'm
going
to
be
talking
about
app
of
apps,
but
then
it'll.
Obviously,
transition
to
application
sets,
but
application
says
is
actually
really
cool.
So
I
put
that
put
that
link
in
in
the
chat.
So
you
guys
could
take
a
look
so.
B
B
B
B
B
Is
being
deprecated
in
a
future
release
by
the
way
yeah?
So
so,
don't
even
don't
even
count
on
it.
So
a
few
things
here
I
actually
spent.
I
started
a
a
get
repo
here
called
argo
cd,
getting
started
right
so
a
lot
of
the
times,
especially
on
the
show,
and
especially
like
on
some
videos,
you
kind
of
see
things
that
are
like
magic,
so
I'm
kind
of
starting
this
kind
of
getting
started
with
argo
cd.
Just
so
you
can
kind
of
get
the
fundamentals
started.
B
There's
one
module
right
now,
I'm
planning
on
adding
more
modules,
but
please
make
sure
to
star
that
repo
follow
that
repo.
If
you
want
to
basically
get
started
with
argo
and
get
kind
of
familiar
before
you
kind
of
just,
you
know
jump
into
these
more
advanced
topics.
Right
about,
like
you
know,
doing
application
deployment
right,
you
kind
of
want
to
get
started
there.
So
that's
one
thing
there,
but
other
than
that
yeah
anything
else
fellas.
I
think
this
has
been
great.
It's
been
a
good
intro.