►
From YouTube: Deploying vSphere Integrated Containers Appliance v1.4.0
Description
This video tutorial demonstrates the deployment of the vSphere Integrated Containers (VIC) appliance version 1.4.0 with a user provided TLS certificate.
For more information please visit the vSphere Integrated Containers product page:
https://www.vmware.com/products/vsphere/integrated-containers.html
A
A
While
this
demo
will
be
similar
to
the
previous
release
version,
131
I
will
highlight
some
of
the
new
features
during
the
deployment.
A
separate
video
will
highlight
the
improved
upgrade
process
to
version
1
for
zero
version.
One
four
zero
is
the
first
version
of
the
Vic
appliance
that
adds
support
for
vSphere
six
seven
I
have
downloaded
the
OVA
for
the
Vic
appliance
and
will
start
its
deployment
using
the
Flex
based
vSphere
web
client,
the
html5
client
and
the
legacy
Windows
client
are
not
supported
for
initial
installation.
A
A
Provide
a
VM
name
and
data
center
or
folder
and
select
the
computer
resource
where
the
appliance
will
be
run,
accept
the
license
and
select
a
datastore.
The
VIC
appliance
requires
a
minimum
of
80
gigabytes
of
storage
with
20
gigabytes
each
for
the
system,
disk
logs
database
and
application
storage.
The
biggest
consumer
of
storage
on
the
Vic
appliance
is
the
container
registry.
If
you
plan
to
store
more
than
20
gigabytes
of
container
images,
the
size
of
this
disk
can
be
increased.
The
other
disks
can
also
be
resized.
A
According
to
your
usage,
another
consideration
when
selecting
the
datastore
is
for
future
upgrades
to
the
Vic
appliance.
The
upgrade
process
requires
deployment
of
the
new
vet
compliance.
A
datastore
in
the
same
cluster
needs
to
be
able
to
accommodate
the
new
appliance
while
the
old
appliance
is
still
present
during
the
upgrade
process.
A
Next
select
a
network,
the
Vic
appliance,
has
one
network
interface.
This
interface
is
used
for
both
management
and
client
traffic
for
management
traffic.
The
appliance
needs
to
be
able
to
communicate
with
the
vCenter
server
and
the
PSC.
The
administrator
also
initializes
the
Vic
appliance
through
a
web
interface
on
the
appliance
for
client
traffic
users
of
the
container
registry
and
container
management
portal
access
these
services
running
on
the
appliance.
A
A
A
Next
I
will
provide
a
custom
TLS
certificate
by
providing
the
certificate
key
and
CA
cert.
A
change
from
previous
versions
is
that
you
only
need
to
provide
the
TLS
certificate
once
it
will
then
be
used
for
all
services
running
on
the
appliance.
I
have
generated
a
CA
private
key
and
certificate
here,
paste
the
PEM
encoded
values
into
the
appropriate
fields.
A
Note
that
the
value
you
paste
for
the
certificate
in
section
1.3
will
be
presented
to
clients,
as
is
if
your
TLS
certificate
requires
an
intermediate
CA.
You
should
concatenate
be
one
or
more
CA
certs
with
the
server
certificate
to
create
the
certificate
chain
before
entering
it.
In
section,
1.3
note
that,
while
previous
versions
required
a
pkcs,
8
format,
private
key,
you
may
paste
an
unencrypted
pem,
encoded
private
key,
either
pkcs1
or
pkcs
8
format
and
the
appliance
will
automatically
convert
it
to
the
correct
format.
A
A
To
use
a
static
IP
address,
provide
the
IP
address,
subnet,
mask
default,
gateway,
DNS
servers,
domain
search
path
and
fully
qualified
domain
name
of
the
appliance
here.
If
these
fields
are
left,
blank
DHCP
will
be
used
for
the
container
registry.
You
may
configure
the
port
that
the
registry
and
notary
listen
on
for
the
management
portal.
You
may
configure
the
port
that
the
management
portal
listens
on.
A
Finally,
example:
users
are
created
in
the
platform
services
controller
after
the
appliance
is
initialized.
This
allows
for
testing
of
the
different
personas
that
can
access
the
container
management
portal
and
the
container
registry
you
may
uncheck
the
box
to
skip
creation
of
these
example.
Users
review
the
configuration
and
click
finish
to
start
to
limit.
A
A
The
services
on
the
Vic
appliance
will
take
several
minutes
to
start
since
I
generated
my
own
CA
and
TLS
certificate,
a
certificate
error
will
appear.
This
will
also
appear
when
using
certificates
auto-generated
by
The,
Vic
appliance.
Add
the
root
CA
certificate
to
your
operating
system
to
eliminate
these
warnings.
As
we
can
see,
the
appliance
is
using
the
certificate
provided
during
deployment
and
shows
the
full
certificate
chain
for
users
who
wish
to
verify
their
connection
to
the
Vic
appliance.
A
When
a
certificate
warning
is
displayed,
the
sha-1
fingerprint
of
the
TLS
certificate
is
displayed
on
the
appliance
console
once
appliance
services
are
started,
the
appliance
must
be
initialized
through
this
model
on
the
getting
started
page
enter
the
vCenter,
server,
location
and
administrator
credentials.
If
using
an
external
PSC
provide
those
details
as
well
when
a
green
bar
is
displayed
at
the
top
of
the
getting
started
page,
the
appliance
is
successfully
initialized.
If
a
red
bar
is
displayed,
appliance
initialization
has
failed.
If
the
page
is
refreshed,
the
red
bar
will
go
away,
but
the
appliance
remains
uninitialized.
A
On
the
getting
started
page,
there
is
a
link
to
the
victimization.
You
may
also
download
the
files
needed
to
deploy
a
VCH
contained
in
the
vSphere
integrated
containers
engine
bundle.
Finally,
there
is
a
link
to
the
container
management
portal
after
logging
in
we
can
see
that
the
management
portal
is
running,
but
this
is
a
fresh
install,
so
there
isn't
anything
populated.
Yet
I
will
review
some
of
the
things
you
can
do
in
the
management
portal.
In
this
screen
you
can
create
a
project.
A
Under
registries,
by
default,
docker
hub
and
the
registry
running
on
the
appliance
are
added
under
configuration.
You
can
download
the
registry
root
certificate.
This
is
needed
by
docker
clients
to
be
able
to
connect
to
the
registry
if
using
auto-generated,
self-signed
certificates
or
using
other
certificates
that
are
not
yet
trusted
by
the
clients
operating
system
under
Identity,
Management
users
and
groups.
You
can
manage
users
roles
and
see
the
default
users
that
were
created
during
deployment
once
you
have
a
virtual
container
host
deployed.
A
You
can
add
that
here
this
will
enable
deployment
of
containers
to
that
VCH
through
the
container
screen
on
the
container
screen.
You
can
deploy
containers
by
specifying
the
container
image
container
name
and
the
command
to
run
thanks
for
watching,
and
you
can
find
out
more
about
vSphere
integrated
containers
at
github,
comm,
slash,
VMware,
/,
Vic
product.