►
From YouTube: S304 - Creating a CI/CD Pipeline for Kubernetes Using Azure DevOps - Christian Meléndez
Description
Do you want to know how can you do deployments to a k8s cluster within minutes using VSTS? We'll start by simulating a common scenario of creating an app locally and deploy it to k8s. We'll enable CI/CD using VSTS and we'll use the exact same scripts we used locally. We'll connect VSTS with AKS.
A
Next
guest,
our
next
speaker
is
Christian
Melendez.
Let's,
let's
reach
out
to
Christian,
see
if
we
can
get
him
dialed
in
here.
Oh
okay,
here
we
go
gonna
fly
out
from
frog,
we're
gonna
go
see.
If
we
can
find
Christian
hanging
out
Christian.
Can
you
hear
us
yeah
there
we
go
Christian.
You
are
live
here
with
us
here
at
dotnet,
conf,
whoo,.
B
Let
me
start
by
the
decision
is
going
to
start
with,
say
in
a
typical
story,
how
you
will
do
the
the
usual
things
on
when
delivering
software
and
then
I'm
going
to
suggest
some
things
and
how
do
you
can
improve
things
and
later
at
the
end,
I'm
gonna
show
you
how
to
actually
create
a
CID
Palatine.
So,
let's
start
to
with
a
typical
story
on
day
one
typical
story
that
the
Finch
is
coding
and
then
post
changes
to
a
control
repository.
B
Then
someone
or
something
else
builds
the
app
that
is
generated
is
compiled
or,
and
things
like
that,
their
developer
deploy
to
a
non
production
environment
that
that
task
is
mainly
but
by
themselves
they
they
have
to
have
everything
ready.
They
testing
name,
for
example,
in
development
environment,
and
they
make
sure
that
everything
is
working
with.
So
after
that
now
it's
time
to
move
changes
to
another
environment,
so
they're
ready.
They
are
confident
that
everything
will
keep
working.
B
Surprise,
surprise,
you
always
have
difficult
difficulties
and
not
everything
works
as
expected,
stupid
money.
So
the
many
problems
arise
here
and
they
have
to
go
again
and
face
things
and
they
have
to
start
working
on
trying
to
solve
those
problems.
So,
ideally
when
they,
when
they're
trying
to
move
that
to,
for
example,
a
testing
environment,
they
will
run
a
set
of
tests.
There
are
executed,
hopefully
in
an
automatic
fashion,
and
if
everything
is
okay,
they
continue
with
the
next
environment.
If
not,
they,
they
will
start
over
again.
B
So
this
is
a
repeated
cycle,
but
they
have
to
spend
like
a
real
good
time
in
trying
to
move
things
from
other
side
from
from
their
computer
to
opportu
to
productive
environment.
So
this
is
day
2.
Usually
it
takes.
It
is
not
as
easy
as
just
copy-paste
alarm
the
artifacts
to
to
to
the
server's.
So
then
comes
the
day
3.
B
If,
assuming
that
everything
worked
as
expected,
and
then
since
I
mean
daeviation,
security
folks
are
called
they're
cool
because
they
need
to
check
things
and
make
sure
that
we
don't
have
security
holes
in
the
application
that
we
are
compliant
with,
with
the
regulation
of
the
company
that
the
policy
that
the
company
has
and
the
DBAs
has
to
check
that
the
scripts
that
we're
about
to
the
point
are
working
and
they
have.
We
are
not
going
to
truncate
a
table
or
drop
a
table,
so
they
is
always
good
that
they
they
get
involved
developers.
B
They
need
to
change
code
again.
This
is
usually
the
normal
way
there,
especially
if
this
is
a
big
change,
but
it's.
But
if
we're
talking
about
small
changes
this,
usually
it
doesn't
take
too
much
time.
But
let's,
let's
that
we're
talking
about
doing
a
big
big
changes.
Dance
is
a
means
and
Libya
is
deployed,
changes
to
production
and
usually
then,
after
that
season
means
repairs
to
developers,
vessels
everyone
that
fight
starts.
Why?
B
Because
season
means
try
are
trying
to
have
a
stable
environment
developers
are
trying
to
push
the
changes
as
soon
as
possible
because
they
are
being
pressured
by
management
and
so
on.
So
the
the
thing
is
that
you,
you
will
have
a
lot
of
problems
when
there
are
silos,
and
you
don't
have
a
good
communication
with
the
things.
So
there
has
to
be
a
better
way
right.
B
Actually
there
is
so.
Let
me
let
me
share
with
you
some
of
the
things
that
I've
been
reading
about
on
my
blog
on
how
to
make
the
appointment
smoother.
This
is
based
on
a
book
that
I
read
a
few
years
ago
from
just
humble,
called
continued
delivery,
which
I
will
recommend
you
to
to
be
retracted
to
that
to
that
book,
and
basically,
in
that
book,
the
things
that
you
will
get
as
a
recommendation
is
that
you
should
outta
mate
as
much
as
possible.
B
There
are
trade
offs,
as
always
as
with
everything,
but
try
to
automate
all
those
repetitive
tasks
that
are
there.
They
are
boring,
basically
build
one
pack,
your
application
only
once
this
is
great
stuff,
because
you
don't
have
to
worry
about
building
and
compiling
again
in
another
environment
that
doesn't
give
you
enough
confidence
that
you
are
I
mean
that
you
are
pretty
sure
that
you're
testing
that
the
code
that
it
worked
on
the
previous
environment
right.
B
So
the
idea
of
building
and
packing
your
application
only
once
gives
you
that
confidence
deploy
in
the
same
way
all
the
time
will,
let
you
feel
the
the
will
that
you
feel
more
confident.
It
will
increase
your
confidence
on
deploying
things,
because,
once
you
work
in
development,
it
should
be
the
same.
It
should
be
working
on
a
prediction
moment
and
I
mean
I
really
mean
with
this,
because
I've
seen
many
prominence
with
workshops
that
are
not
doing
the
darn,
our
client
is
rule.
B
Basically
they
are
treating
a
production
environment
really
special
and
they
think
well
development.
We
can
do
whatever
we
want.
We
can
install
whatever
you
want.
Let
give
access
to
everyone,
so
they
can
play
around
without
environment.
That's
the
developer,
Meyer
and
I
agree
with
them.
It
is
not
always
a
good
thing
that
you
don't
have
a
way
to
practice
your
deployments
to
production.
So
as
long
as
you
have
an
on
production
environment
in
previous
environment,
you
you'll
be
able
to
this
deployment
small
batches
and
do
it.
B
Often
this
is
sounds
like
really
easy,
and
actually
it
is.
But
what
if
I
haven't
finished
a
feature
or
if
I
haven't,
if
my
working
or
in
mind
or
if
my
code
is
having
problems?
Well,
there
are
some
strategies
that
you
can
implement
in
your
code
are
called
feature
flags.
So
if
you
need
to
deploy
something
because
you
need
to
fix
something,
you
don't
want
to
revert
the
code
create
patches
and
things
like
that.
B
You
can
always
turn
off
the
flag
and
you
will
be
practicing
that
deployment
I've
been
experiencing
that
in
in
other
prayers,
where
we
are
claiming
the
the
changes
to
a
big
changing
in
the
architecture
little
by
little,
and
it
has
worked
for
me.
So
that
is
a
recommendation
that
I
can
give.
You
today
choose
a
zero
tolerance
tragedy,
so
the
customers,
your
clients,
will
notice
that
you
have
a
that.
You
are
changing
something.
Some
of
those
tragedies
are
called
looting,
deployments,
canna
releases,
etcetera.
B
B
B
So,
as
I
was
saying
for
the
term,
peace
development
is
not
usually
a
common
practice.
There
I
mean
I,
didn't
know
until
I.
Rather
article
about
this
topic,
I
receive
a
lot
of
comments
there
that
why?
Why
should
be?
Why
should
be
doing
trumpet
development
branches
are
good?
They
they
work
as
I
agree
with
them,
but
I
don't
agree
with
with
the
approach
of
humming
branches
that
you
would
keep
practice
for
for
a
long
time.
You
should
keep.
B
You
are
good
to
to
go
with
branches
as
long
as
you
keep
them
short
lifetime
of
that
branches
is
short
that
that
way,
it
is
easy
and
it
is
more
more
smooth
to
implement
continuous
integration.
Basically,
and
that's
basically,
the
idea
notice
I'm
saying
that
you
shouldn't
be
using
branches.
Never
it's
just
that
for
continuous
integration
from
base
development
is
really
good
practice.
Finally,
work
with
the
environment
variables,
meaning
that
as
I
was
saying
before
you
will
build
impact
your
application
only
once
so.
How
are
you
going
to
test
that?
In
other
environments,
the.
B
B
B
Quick
recap:
I'm
not
going
to
spend
too
much
time
here,
because
I
really
want
to
show
you
the
how
to
create
a
CH
TD
pipeline
and
that
you
can
see
whoa
what
I'm,
what
a
meeting
with
all
the
points
that
I've
dialed
I
previously
was
talking
in
in
practice
right,
so
listen.
Why
kubernetes
with
kubernetes
is
really
easy
to
have
a
mutable
infrastructure?
You
will
you
won't
be
occurring
too
much
about
this?
Is
chamber
server
a
several
bees
ever
see,
even
because
what
will
matter
is
that
you
can
turn
out.
B
C
B
With
with
with
with
containers
and
product
and
pots,
you
can,
if
you're
having
problems,
you
can
easily
terminate
that
or
remove
them
from
the
load
balancer
and
investigate
there.
But
the
idea
is
that
you
don't
spend
time
trying
to
face
things
you
normally
or
traditionally
will
do
just
spin
a
new
server
or
a
new
container,
and
that's
it.
It's
came
out
very
easily.
B
B
You
can,
for
example,
say
that
for
this
application,
I
want
three
replicas
and
I
want
these
three
replicas
to
be
exposed
at
the
service,
and
that
service
should
be
a
load
balancer,
for
example,
and
coronaries
will
make
sure
that
you
all
the
time
the
application
has
three
replicas
that
is
exposed
as
service
and
is
a
load
button
and
is
public
or
is
eternal
and
so
on.
On
its
own,
you
can
run
local,
and
that
means
that
if
you
can
run
local
with
kubernetes,
you
can
run
anywhere
now.
B
B
Hopefully
a
man
on
my
machine
and
then
I'm
going
to
create
a
pipeline
to
push
that
to
another
mark
robots
are
very
easy
because
you
just
need
to
say:
ok,
let's
update
the
service,
let's
update
the
deployment
with
the
previous
version
and
torinese
will
make
sure
that
you
can
that
do
you
want
have
a
downtime
there,
because
the
default
policy
that
uber
natives
will
update
your
containers
in
a
in
a
reliable
manner,
meaning
that
it
will
be
doing
running
updates.
Not
everything
will
drop
everything
and
will
come
we'll
bring
everything
up
again.
B
It
is
pretty
same.
You
will
have
high
availability,
because
I
was
a
before
kubernetes.
Pay
is
mainly
based
on
state.
How
Koreans
does
that?
Currently,
this
has
a
Chile
where
it's
had
no
sequel
database,
where
kubernetes
stores
the
state
of
the
cluster.
You
will
find
there.
How
many
knows
the
worker,
how
many
workers
the
cluster,
has
how
many
containers,
how
many
parts?
How
are
the
computer
access
data?
B
You
can
easily
configure
security
controls
for
your
for
your
applications
and
you
can
do
a
lot
of
see
a
lot
of
more
things
so,
but
this
is
just
a
quick
recap:
I'm
gonna
I'm
gonna
stop
there.
The
good
ladies
architecture
is
as
follows:
you
will
have
to
burn
a
disaster
nodes
which
this
is
usually
called
control
nodes.
The
idea
ideal
is
an
area
that
you
have
three
servers
here.
B
Then
this
control
control
plane
with
expose
an
API
where
our
user
interface,
command-line
interface,
will
interact
with
kubernetes
and
on
the
right
side,
you
will
find
that
you
will.
You
have
work
your
nodes
where
all
the
containers
or
the
pods
will
be
hosted
and
it
should
have
access
to
image
registry
or
a
doctor
repository.
It
could
be
something
private.
It
could
be
something
public
like,
as
we
were
speaking
for
digital
career.
Ladies
capabilities-
and
this
is
this-
is
really
the
powerful
thing
from
kubernetes,
because
you
can
implement
something
like
that.
B
Then,
if
everything
keeps
working
as
expected,
you
will
promote
your
changes
to
our
country
for
your
paid
users,
but
you're
not
going
to
do
it
for
other
users.
You
can
do
the
proper
configurations
to
promote
those
changes
to
a
service
that
only
receives
five
percent
of
the
traffic
from,
although
from
from
your
site,
then,
if
you
have
tested
everything
in
three
different
ways,
everything
should
be
working
right,
so
you
can
promote
those
changes
to
production
environment
and
that
will
be
there
100%
of
the
traffic.
You
can
wait
as
long
as
you
want
between
these
steps.
A
B
So
basically,
as
I
was
saying
before,
you
need
to
spin
up
three
masters,
and
things
like
that,
you
will
actually
I
will
recommend
you
to
to
play
around
with
kubernetes
the
hard
way.
It's
a
it's
a
tutorial.
That's
out
there
in
need
of
a
queue.
Remember
well,
I
didn't
put
a
link
here,
production
surety
later,
where
you
can
spin
up
kubernetes
the
hard
way
at
your
at
your
way,
by
setting
up
the
instances
by
your
own
configuring
things,
computing
certificates
and
things
like
that,
and
you
will
notice
that
you
want
that.
B
That's
something
you
don't
you
don't
want
to
have!
So
that's
why
you
would
use
services
like
this.
I
should
coordinated
services,
but
I
should
will
take
care
of
all
the
master
nodes
for
you
and
the
good
thing
is
that
you
don't
pay
for
them.
You
only
pay
for
the
worker
and
that's
a
really
good
thing.
It
integrates
with
other
assured
services
very
easily.
B
You
can
create
a
cluster
in
minutes
and
actually
I'm
gonna
demonstrate
that,
for
you
put
it
because
I
don't
have
too
much
time,
I'm
not
going
to
wait
for
the
cluster
to
be
overrun.
It
supports
every
bug
for
security
purposes
and
it
has
integrated
logging
and
monitoring
and
many
other
things
that
are
out
of
scope
of
distance.
So,
let's,
let's
keep
moving.
How
would
you
do
DevOps
with
Usher?
Well
now
you
have
DevOps
assure
product
which
previously
was
named
as
bsts
they
will
seem
for
cornetist
is
that
you
have
agents
anywhere
and
I'm
gonna.
B
Explain
that
why
that
is
good
in
the
demo
you
have
native
doctrine
support
integrates
easily
with
any
cloud.
It
is
easy
with
kubernetes,
even
if
you
install
for
some
reason,
kubernetes
the
hard
way
you
can
build
once
and
pull
it
anywhere,
and
it
has
extensions
for
for
common
technologies.
Like
terraform
answer
all
that
things
like
that,
so
in
a
devops
world
you
will
have
pretty
much
everything
you
need
to
implement
your
CHD
pipeline
and
we're
going
to
practice
what
we
will
I
just
told
you
before
how
to
make
deployments
smaller.
B
So,
finally,
how
would
you
do
this
is
like
improved
version
of
a
typical
story
with
now
that
you
are
implementing
the
box?
This
is
like
the
fact
that,
like
the
end
goal,
it
doesn't
mean
that
you
will
have
this
from
the
very
first
day,
although
it
would
be
good
for
new
prayers,
but
the
idea
with
the
opposite
that
you
could
start
working
in
small
batches
as
I
was
saying
before
and
don't
get
stressed.
If
you
don't
have
a
pipeline
from
day
one,
although
is
very
easily
to
create
one.
B
You
put
your
code
changes
to
version
control
integrated
in
an
isolated
environment
like
I,
should
telex
you
build
portable
docker
image
you
deploy
in
a
production
like
environment,
you
run
automated
test
and
repeat
the
plant
test
again
in
other
environments
and
when
you
deploy
in
another
environment
steps
1,
2,
3,
3,
2
3
are
not
going
to
be
needed
anymore,
because
you
don't
really
have
everything
that
you
need
packed
in
a
doctor
image
and
it
is
summer
just
of
pushing
the
changes
to
the
environment.
So
that's
enough
talking
for
me
it's
demo
time.
B
So,
let's
jump
back
to
the
to
the
to
the
console.
If
you're
not
seeing
my
screen,
please
let
me
know
I'm
going
to
create
out.
This
is
I'm
going
to
show
you
how
easy
is
to
create
a
cluster.
You
can
have
here
service
community
service
and
it's
pretty
easy.
I'm
gonna
create
here
new
one
and
let's
say
if
red
demo
and
say
it
is
going
to
use
an
existing.
Let's
use
an
existing
resource
pool
it's
going
to
dotnet
demo
right
here,
dotnet!
No,
we
have
to
be.
A
B
Region,
you
choose
the
coronaries
version.
This
is
the
latest
version.
You
can
choose
the
node
sides,
the
worker
node.
By
default.
It
has
d
s,
2,
p,
2
and
by
default
has
three
nodes
you
can
set
up
outside
vacation
here
you
will
create
for
your
surface
principle.
This
is
the
do
need
this
to
interact
with
other
assure
services
I'm
gonna
leave.
B
These
are
people,
but
this
is
where
you
can
able
air
back
next,
you
can
enable
or
work
with
pretty
custom
configurations
for
your
network,
but
I'm
gonna
leave
that
as
default
monitoring,
you
have
as
I
was
saying
before
you
have
doing
and
monitoring
enabled
by
people
in
tax.
If
you
like
to
have
text
to
for
center
cost
or
things
like
that,
to
wait
a
little
bit
as
the
pre-service
principal
is
created,
it
will
run
the
final
validation
and
that's
it.
You
will
have
your
after.
B
This
is
great
I'm,
gonna
click
here
and
I'm
gonna
have
my
coordinators
environment
in
just
minutes.
So
let's
create
this,
that's
it!
That's
that's.
How
easy
is
to
create
a
cluster
with
Usher.
So,
let's
jump
back
to
the
one
I
previously
created
for
for
demo
purposes,
I'm
gonna
create
this
is
the
the
crowd.
The
cluster
that
they're
happening
there
are
did
I
spin
up
for
further
demo.
So
you
can
see
here
that
you
will
have
things
like.
B
What
is
important
for
us
now
is
that
you
have
the
access
to
that
cluster
and
let
me
show
you
how
you
can
do
it.
You
can
say
here
like
view
current
edit
dashboard
and
you
will
need
to
install
the
Usher,
see
light
you
will
need
to
login.
If
you
don't
have
Q
controller
in
start,
you
will
need
to
install
it.
Then
you
need
to
download
the
credentials
which
is
which
I'm
going
to
do
right
now.
B
You
will
have
the
service
here
services
here,
let's
zoom
back
to
the
service
that
I
just
polished
and
application
that
I
choose
for
demo
purposes,
which
is
which
here
you
can
see
that
says
that
calm
does
not
come
online.
The
the
way
that
I'm
going
to
do
is
that
to
do
this
right
now
is
that
I
will
create
a
view
change
here
and
I'm
gonna
change.
This
and
I'm
gonna
push
that.
But
let's
start
first
by
going
to
to
to
a
sure
DevOps,
and
this
is
how
it
will
create
a
CH
cd-5.
B
Let's
start
by
creating
a
new
project,
I'm
gonna
create
here
any
frame,
and
it's
call
it
aside.
For
example,
I'm
gonna
leave
it
as
private,
but
you
can
have
it
like
a
public
and
you
came
here.
You
can
choose
if
you
would
like
to
use
git
or
TFS,
or
if
you
like,
to
have
a
dash
for
work
with
a
chalice.
B
If
you
were
working
with
it,
though
so
wrap
us
I'm
gonna
click
here
with
to
trap
us
I'm
gonna
import
the
cold,
so
I'm
gonna
here
copy
this,
and
because
it's
public
I
don't
require
any
authentication
and
can
import
it.
Its
way
a
little
bit
it
doesn't,
it
won't
take
too
much
time.
It
is
basically
cloning,
the
the
code
to
to
the
repository
here
then.
The
next
thing
that
I'm
going
to
do
is
that
I
will
clone
the
repository
to
my
local
file.
B
And
it's
though,
here
you
can
see
here,
clone
already
computer
an
SSH
key
on
my
computer.
So
I
can
easily
do
things
like
the
things
here
where
I
can
I'm
gonna
close
the
the
proxy
here,
because
I'm
gonna
come
back
to
this
there.
So
let's
go
here,
it
only
will
download
the
the
code
that
I
just
make
my
gradient,
and
you
can
see
that
the
code
here
and
it
is
pretty
standard
code
I'll.
Let
me
open
that
lets
here
open.
B
B
A
B
B
To
profile
here,
let's
see
dr.,
it
was
missing
at
the
docker
build
so
evil,
as
I
already
had
these
images.
These
base
images
downloaded
to
my
computer.
It
will
skip
that
and
it
will
start
to
compile
it
to
compile
the
application
and
while
this
finishes,
let
me
show
you
something
here.
This
is
the
docker,
the
format
that
I
that
I
have
running.
You
can
see
that
you
can
have.
Your
name
is
Peter
here
installed.
You
can
just
click
here.
Click
here
and
dr.
B
Let's
see,
for
example,
let's
run
this
CTO
get
box,
for
example,
as
you
can
see,
there's
there's
there's
nothing
there,
the
the!
If,
if
I'll
run
this
command
previously
I
will
see
the
pots
that
we're
running
in
in
Azure.
So,
let's
jump
back
here,
let's
create,
for
example,
for
some
reason
my
environment
is
not
working
with
local.
The
cruelities
cluster
is
not
working
when,
when
it's
proving
the
local
images,
I'm
gonna
push
this
this
image
to
my
repository
as
I
said
before,
this
is
not
necessary.
B
It
shouldn't
be
necessary
because
you,
you
would
use
your
local
environment,
but
for
demo
purposes,
I'm
gonna
leave
this,
but
without
warning.
So
let's
wait
a
little
bit
and
you
can
see
that
it
is
already
pushed
and
I'm
gonna
go
back
to
them
console
here,
and
you
will
see
that
the
latest
version
is
there.
B
So
now
what
I'm
going
to
do
is
usually
what
I
would
do
to
test
everything
is
that
I
will
run
the
command
here,
but
because
I
don't
have
too
much
time
right
now,
let's
go
back
to
the
to
the
deployment
jam
out
here,
for
that
I
would
use
for
kubernetes.
As
I
was
saying
before
you
will.
You
will
declare
here
a
deployment.
You
will
say
here
that
you
want
three
replicas,
and
this
is
the
image
that
you're
going
to
use,
and
this
image
is
this.
B
This
file
is
because
it
is
in
version
control,
I'm,
gonna
change
latest
with
the
person
that
that
the
pipeline
is
created.
This
is
going
to
make
sense
when
I'm
to
it,
but
for
because
I
don't
want
to
change
too
much
things
to
test.
Luckily,
I'm
gonna
leave
that
as
that,
so
let's
see
how
would
you
run
that
I'm
gonna
deploy
that
lovely
sweet,
a
command,
keep
CTL
get
box?
You
will
see
that
is
creating
the
the
the
path
and
you
will
see
that
it
has
created
a
service.
B
B
If
I
don't
have
anything
else
running
on
port
80
issue
work
and
it
works
right,
so
I
am
I'm
running
this
version
of
the
application
on
my
machine
locally.
So,
let's
jump
back
on.
How
would
you
create
something
for
the,
because
I
was
saying
before
that
someone
or
something
will
build
the
application?
So
this
is.
How
would
you
do
this?
This
is.
How
would
you
create
a
Python?
B
You
will
go
to
a
DevOps,
you
will
click
here
in
pipelines,
builds
and
create
a
new
pipeline
and
because
I
don't
want
a
jumbo
description
right
now
to
have
this
infrastructure,
so
I'm
gonna
use
a
pixel
designer
so
that
everything
that
I'm
doing
make
sense
for
you,
and
it
is
easy
to
understand
so.
I'm
gonna
choose
the
repository
here,
but,
as
you
can
see,
I
can
integrate
it
with
any
other
cool
repository
when
I
click
here
on
empty
job
and
I'm
gonna.
Leave
that
way.
B
I'm
gonna
choose
here:
I'm
gonna
change
here
the
agent
to
a
hosted
upon
to
because
I'm
compiling
containers
in
in
in
the
in
early
notes
in
dr.
Lynn,
so
I'm
gonna
choose
that
this
is
how
it
will
you
will
see
which
break
is
pulling
from.
This
is
going
to
be
the
pool
of
agents,
I'm
gonna
leave
data
people
and
us
as
well
as
I,
did
locally
I'm
gonna
build
the
this
is.
B
This
is
the
extension
that
I
was
talking
about
the
shooters
I'm
gonna,
be
on
the
image
and
I'm
gonna
choose
this
and
I'm
gonna
here
create
I'm
gonna
start
creating
the
the
connection
to
the
registry
that
I
have
created
here.
It
doesn't
mean
that
you
cannot
integrate
imperiously
with
assured
container
registry
in
a
private
way,
but
I
wanted
to
do
it
this
way,
so
that
you
can
see
that
it
is
pretty
easy
to
do
that
next,
you're
gonna
do
here
on
manage
sorry.
If
I'm
doing
this
to
us,
gonna
create
here.
B
B
Very
fine,
okay,
so
the
the
connection
has
been
created
and
I'm
gonna
jump
back
to
the
screen
here.
I'm
gonna
click
here
to
update
the
connection,
and
you
can
see
that
the
connection
is
there.
I'm
gonna
run
the
command
bill
and
if
you
don't,
if
you're
not
sure
about,
where
is
the
file,
you
can
click
here
and
you
will
see
what
the
files
you
have
for
for
the
repository.
You
choose
doctor
power
and
you
will
hear
put
an
image
name
so
I'm.
B
My
user
name
here
and
I'm
gonna
go
here,
simple,
app
and
I'm
gonna
remove
this
and
I'm
going
to
change
this.
Let's,
let's
copy
this,
you
will
understand
why,
in
a
minute,
why
why
I'm
doing
this
Jing
is
here
too
variable
that
I
will
create
and
that's
it.
This
is
how
you
will
build
image.
The
next
step
is
that
you
will
push
the
image
right.
So
let's
do
this
and
let's
choose
here
the
connection.
This
is
where
it
is
going
to
be
very
useful.
B
It
will
here
push
it
will
change
the
text
to
push
command
and
it
should
be
the
same
image
that
you
just
feel.
You
should
change
this
here.
Let's
go
change
this,
so
the
next
step
is
that
remember
the
write
that
I
mentioned
that
I'm
going
to
change
this,
the
latest
to
the
to
the
person
that
is
getting
built.
So
that's
why
I
need
to
create
an
environment
that
is
version
for
example,
and
I'm.
B
B
It
is
pretty
standard
set,
I'll
replace
it
will
replace
what
is
latest
the
the
value
latest
with
a
person
to
the
the
file
the
the.net
deployment
camel.
Next.
The
way
that
this
process
will
communicate
with
the
release
is
that
it
will
publish
the
artifacts
because
I'm
gonna
do
the
deployment
the
deployment
gamma
that
I
have
here
to
to
run
the
same
command
that
are
run
locally
in
usher.
I
need
that
file,
so
I'm
gonna
put
a
name
here,
I
wanna
say
her
latest
gamma.
For
example.
B
Let's
see,
let's
say
that
we
only
need
to
including
that
artifact
the
camel
to
make
it
not
to
leave
it
as
light
as
possible.
That's
here
demo,
for
example,
and
let's
keep
them
so
I'm
gonna
save
it
cube.
You
can
save
it
in
hue.
Gonna
keep
using
the
default
configuration
that
I
had
previously-
and
this
is
this-
is
going
to
start
creating
the
the
the
build.
B
As
you
can
see,
it
says
version
20,
but
that's
because
I
already
have
other
pipelines
created
here
in
the
project,
and
the
cool
thing
here
is
that
you
will
be
able
to
see
the
logs
in
the
in
life
and
you
can
see
every
every
face.
What
what
is
doing-
and
you
can
see
this
later
also-
and
it
will
initialize
the
agent
it
will
initialize
the
job.
It
will
do
check
out
the
the
code.
B
It
will
start
building
the
image,
but
there's
something
that
I'm
that
I'm
missing
here
as
this
is
going
to
take
a
while,
because
the
agent
doesn't
have
the
images
I
already
had
in
my
computer.
That's
why
you
would
like
to
choose
to
have
a
hosted
agent
in
your
environment
for,
for
example,
in
action,
so
that
this
process
is
going
to
be
more
quick,
more
quicker,
so
quicker.
Sorry.
So
let's
go
back
to
the
to
the
to
the
pipeline
because
I'm
missing
something
here
and
when
we
finish
we're
going
to
review
that.
That
is
not.
B
That
is
working.
So
let's
go
edit
the
pipeline,
and
what
I'm
going
to
do
is
that
after
I
push
the
changes
in
my
code,
this
will
trigger
a
new
bill.
So
we
will.
It
is
as
easy
as
going
here
triggers
and
you
will
click
here
enable
continuous
integration
and
I'm
gonna,
save
it
and
I'm
just
gonna
save
it.
B
Let's
see
if
it
already
finished
now,
but
let's,
let's
go
quickly
to
create
this
is
the
the
CI
pipeline.
Let's
create
a
CD
part
of
the
process,
let's
create
the
CD.
The
pipeline
continue
delivery
pipeline,
I'm
gonna
choose
as
well
empty
job,
and
this
is
where
I'm
going
to
collect
everything.
Gonna
close
this
year
and
I'm
gonna
choose
the
artifact
that
I
already
built.
It
is
going
to
be
the
demo
site
that
I
just
created.
B
It
was
oh,
it
is
going
to
be
all
week
using
the
latest
version.
It
would
use
these
aliens
uncourteous
leave
a
doctor,
and
this
is
how
you
could
enable
continuous
deployment
trigger,
meaning
that
after
the
build
is
finished,
this
release
will
be
triggered
so
I'm
gonna
leave
that
here
and
here
just
let
me
show
you
this
you
can.
You
can
have
here
pre
deployment
conditions
like
meaning
that
someone
needs
to
approve
this
deployment
these
release,
and
you
can
do
that
for
other
stages.
So
let's
call
it
here
development.
B
You
could
have
here
the
extension
that
is
or
integrates
very
easily
with
a
sure,
coordinated
service,
or
you
can
integrate
this
with
other
cluster
that
you
have
some
girls.
Luckily,
for
us
this
is
the
this
extension
is
already
here
and
I'm
gonna
integrate
this
with
Usher,
so
I'm
gonna
right
here,
gonna
say
subscriptions
that
I
already
have,
if
I
wouldn't
it
by
giving
up
this
I
will
go
back
to
the
same
screen
as
I
was
doing
before
for
for
the
doctor
registry.
B
B
B
After
this
finishes,
you
will
be
able
to
see
here
a
resource
group.
You
will
be
able
to
see
the
cluster
that
that
I
that
I
created
before
and
what
I
really
like
here
is
that
you
can
specify
the
nine
space
of
the
of
the
cluster
where
you
would
like
to
deploy
this
change,
but
if
this
is
empty
is
going
to
do
it
in
the
default.
So
let's
choose
the
resource
group:
let's
choose
the
cluster,
the
simple
app:
let's
do
it
to
the
simple
app
that
we
already
have.
B
That's
everything
leave
everything
as
default.
Choose
configuration
files.
You
will
then
here
get
to
choose
the
artifact
that
it
finished,
creating,
as
you
can
see
here,
the
deployment
demo
so
I'm
doing
that,
because
you
don't
have
to
worry
about
what
to
put
here.
It
is
pretty
easy
to
do
that
so
I'm
going
to
save
this
here.
I'm
gonna
click
that
and
that's
it.
If
you
would
like
to
create
a
new
release,
you
will
manually,
for
example,
you
will
create
here,
click
create
release.
You
will
choose
the
stage.
B
You
will
choose
the
version.
As
you
can
see,
it
is
a
22
version,
20
and
let's
create-
and
you
can
go
here
to
the
release
and
it
is
going
to
be
the
same
screen,
but
the
missing
step
is
that
you
need
to
click
here.
Deploy.
You
will
hear
here
demo
purposes,
for
example
on
deploy
and
that's
it
that's
how
you
will
create
a
pipeline.
B
The
next
thing,
if
but
I,
don't
I,
don't
think
I
have
too
much
time
is
that
I
will
do
something
here
like,
for
example,
if
I
remember
it
is
going
to
be
here.
Let's
change
something
here,
demo,
that's
it!
Let's
save
it,
let's
say
demo
and
commit
that
change.
Let's
push
it.
It
doesn't
have
a
graphic
way
here,
but
you
will
see
here
the
code
that
it
has
a
new
change.
It
has
the
demo
change.
You
will
see
that
a
new
trigger
is
going
to
be
a
new
build
is
going
to
be
triggered
there.
B
Change,
let
me
show
you
just
once
in
here:
you
will
see
that
in
at
my
repo
you
will
have
the
latest
version
and
the
version
that
it
just
built.
So
basically
this
is
the
same.
It
is
going
to
happen.
The
same
thing
I
already
see.
We
already
see
that
the
build
is
working.
Let's
see
if
the
the
release
is
working
good,
it
is
working.
So,
let's
jump
back
to
to
the
to
the
cluster
for
simple
app
that
I
have
in
Asscher
and
let's
clear
the
screen
keeps
it
a
little
bit.
B
You
will
see
here
that
is
creating
the
new
container
and
it
is
adding
a
new
container
image
and
a
new
a
new
pod
I'm,
sorry,
but
it
is
keeping
the
other
three
that
we
already
have.
This
is,
it
is
running,
update,
see
it
is
terminating
the
other
pot
and
it
is
doing
the
deployment
in
that
safely
manner.
B
You
can
see
here
that
the
service
and
I
have
the
external
P
as
well
here
as
I
was
seen
before
in
the
console
and
the
released
one
finished,
but
because
the
film
hasn't
finished
yet
it
is
working
I
will
I
will
keep
seeing
the
same
screen
without
the
change,
but
I'm
gonna
leave
this
here.
If
you
have
any
other
question,
if
you
have
questions
I
think
it's
the
time
now
and
some
cycling
is
answering
the
questions.
I'm
gonna
go
here
and
update
and
you
will
see
that
the
new
church
will
be
here.
A
B
A
So
we've
got
some
folks
that
are
in
the
Chad
room
that
are
saying
they
really
like
this
content
that
can't
wait
to
see
it
on
on
a
replay,
so
they
can
go
out
and
check
out
videos
on
demand.
Of
course,
there
will
be
video
on-demand
available
here
on
Twitch.
We're
gonna
also
cut
this
video
put
it
together
on
our
YouTube
channel,
so
folks
can
see
that
as
well
and
there's
our
asp
net
core
website.
Let's.
C
B
C
On
the
sidebar,
I
think
I
think
what
he's
asking
is
on
the
sidebar.
You
see
how
you've
got
the
releases
star
tab
when
I
look
at
that
in
my
own
I
see
releases
with
no
star
and
then
releases
with
a
star.
Do
you
know
if
that's
something
that
is
like
a
VST
s,
to
add
your
DevOps
migration
thing
or
do
you
do
you
have
any
insight
as
to
why
some
of
the
c2
releases
tabs
yeah.
C
B
A
Awesome
and
let's
put
up
your
information,
real
quick
there
we
go
so
there's
your
Twitter,
so
folks
can
can
connect
with
you
and
there's
your
there's,
your
blog
up
top
great
stuff,
I
think
we're
I!
Think
we're
good
here.
Thank
you!
So
much
Christian.
We
really
appreciate
you
joining
us
here
for
dotnet
confidence
here.
This
has
been
great
cool.