►
From YouTube: Kubernetes: Developing on Windows, Deploying on Linux [B] - Rodrigue Cloutier, Ubisoft
Description
Kubernetes: Developing on Windows, Deploying on Linux [B] - Rodrigue Cloutier, Ubisoft
The Kubernetes community and tooling is currently oriented towards POSIX systems.
For various reasons, many developers still need to run a development environment on Windows, while deploying actual services in a Linux environment.
This talk is based on what we've learned while developing the next online platform for Ubisoft's flagship games.
It will cover the current state of tooling when working in a mixed environment, and some of the practices we've developed to work effectively with the current generation of tools such as minikube and Helm.
We will also explore what can be learned about how these and future tools can be better adapted to support developers working in these mixed environments.
Topics covered include:
- Current state of the Kubernetes tooling in mixed environments
- Using POSIX tooling within "native" Windows shells
- Current virtualization technologies caveats and proper usage
- Best practices for developing mixed-environment aware tools
About Rodrigue Cloutier
Rodrigue's unusual career path, starting in marine biology and progressing into game programming, allowed him build a solid experience in complex systems. As a senior technical lead at Ubisoft, he is now heading up the implementation of a new online platform, backed by Kubernetes, for future games. He is also involved in the community as a contributor on Kubernetes, minikube and Helm. Proud father of 3, Rodrigue lives in Montreal.
Join us for KubeCon + CloudNativeCon in Barcelona May 20 - 23, Shanghai June 24 - 26, and San Diego November 18 - 21! Learn more at https://kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy and all of the other CNCF-hosted projects.
A
Hi
welcome
to
my
talk
about
developing
on
Windows
but
deploying
on
Linux,
mostly
kubernetes.
My
name
is
Rudd
Tootsie
rather
gig.
If
you
want
to
say
it
in
French,
but
it's
harder
for
people
most
the
time.
I
work
for
Ibiza
I'm,
an
online
technical
lead,
I
lead
a
team
working
on
the
next
generation
platform
for
all
our
new
games.
A
Well
then,
contribute
to
that
world,
and
but
the
main
crux
and
our
main
problem
for
us
is
that
we're
working
on
Windows
games
just
like
it
was
said
in
the
keynote
yesterday,
linker
D,
flew
and
D
said:
well,
they
want
to
have
Windows
Parton's,
basically
because
of
us
game
developers.
All
of
our
games
are
running
on
Windows
and
we're
developing
on
Windows.
Hence
this
talk.
We
want
to
present
what
we've
been
doing
so
far,
a
bridge
between
developers,
working
Windows
but
actually
deploying
kubernetes.
A
The
goal
of
this
talk
is
to
share
our
experience
that
we
had
so
far.
We've
been
working
for
about
a
year
and
a
half
now,
with
this,
give
some
exposure
what
the
issues
that
we
have,
how
we
could
make
it
work.
What
what
were
the
problems
and
how
can
we
solve
those
problems
and
maybe
foster
discussion,
awareness
about
the
windows
developers
we're
out
there
there's
a
lot
of
people,
so
we
want
to
make
sure
that
the
kubernetes
community
is
aware
of
a
few
windows
developers.
A
A
But
if
you
look
at
it-
and
if
you
take
this
in
account
well
Windows
is
a
second-class
citizen.
Most
of
the
time,
if
you
take
a
tool
that
is
open-source,
you
try
to
run
Windows
either
it
doesn't
run
at
all
or
it's
sort
of
a
well.
Let's
try
to
run
it
over
there,
but
you
might
have
to
do
this
or
that
so
we're
not
treated
as
first-class
citizen,
and
we
want
to
try
to
make
it
so
that
we're
becoming
closer
and
closer
and
why
well,
some
people
have
to
give
work
in
Windows.
A
A
Also,
if
you
look
at
the
Stack
Overflow
survey,
which
is
not
the
picture,
a
real
picture,
but
it's
a
good
indication.
Well,
lots
of
people
are
using
Windows.
It's
not
only
that
people
are
all
happy
saying
all
that
Linux
is
the
best
OS
or
whatever
the
opinions
of
people
are
is
that
we
do
have
lots
of
people
that
are
working
on
Windows.
Now,
it's
the
trend
is
sort
of
changing
right
now.
The
next
survey
that
just
came
out
a
few
days
ago
is
actually
stating
that
people
are
using
Windows
and
Linux
and
Mac.
A
So
people
are
switching
between
the
two,
but
most
of
time
you
need
to
go
back
to
Windows
if
you're
working
in
a
corporate
world.
So
what
I
propose
is
to
have
a
look
at
the
challenge
that
we
had
by
trying
to
address
this,
then
all
maybe
the
bridges
that
we've
developed
to
actually
make
it
work
now
using
those
bridges.
A
What
are
the
tools
in
the
communities
community
that
we
can
actually
use
and
make
it
work
properly,
and
maybe
some
of
the
action
we
can
take
eventually
to
make
it
even
easier
for
the
next
people
so
our
challenges
in
our
case,
if
yourself
is
a
big
company,
we
have
29
studios
worldwide.
We
have
open
over
10,000
people
working
for
Ubisoft
out
of
these
10,000
people.
We
have
more
than
300
online
developers,
so
we
have
people
that
are
writing.
Online
services
are
consuming
online
services
in
their
games
and
stuff
like
that.
A
So
all
of
these
peoples
are
basically
working
essentially
in
Visual.
Studio
visual
studio
is
the
first-class
IDE
for
game
development.
There's
no
I,
don't
know
any
big
triple-a
targeting
companies
are
not
working
with
Visual
Studio
Visual
Studio
is
actually
fully
supported
by
Nintendo
by
Sony,
so
it
makes
it
a
lot
easier
for
us
actually
just
work
there.
So
we've
been
working
with
that
we've
been
working
for
a
long
time.
If
you
want
to
develop
on
the
Microsoft
Xbox,
while
you
can't
work
outside
of
Visual
Studio.
A
So
we
need
to
work
with
that
and
it's
really
convenient
for
us,
because
if
we
have
everything
at
one
place,
we
can
actually
write
tools.
We
can
write
automate
and
we've
invested
a
lot
in
that.
So
we
need
to
keep
working
with
this
and
we
have
a
really
really
strong
expertise
inside
yourself.
We
have
lots
and
lots
of
tools
that
are
written
internally,
that
we
can
make
it
and
people
can
use.
So
we
want
to
keep
using
those
tools
and
maybe
it'll
rip
them
inside
the
online
workflow.
A
So
obviously,
for
us,
it's
really
hard
to
do
a
math
switch
to
Linux.
We
can't
just
go
and
say:
oh
guys,
let's
go
pick
up
a
new
box.
You
get
your
on
Linux
right
now
is
just
gonna
work
better.
So
that's
the
solution
that
some
people
would
say
well
just
work
on
Linux.
It
could
work,
it
doesn't
work
for
us
also
a
time.
So
the
next
step
would
say.
Well,
let's
try
to
have
something
that
is
basically
oops.
A
Let's
try
to
bring
it
back
and
maybe
have
two
boxes.
Maybe
have
people
working
on
Windows
on
one
box
and
then
have
a
second
box
on
the
side
and
say
well.
Do
all
your
online
stuff
on
the
Linux
box,
we've
tried
that
not
exactly
for
Linux
but
for
our
stuff,
but
people
are
not
really
happy
with
two
boxes.
You
need
to
manage
both
of
the
boxes
in
any
net.
You
have
context
switch
if
you
have
different
OSes,
it's
even
worse.
A
Now
your
emails
are
not
on
one
they're
on
the
other
one,
and
then
it
gets
a
lot
harder
people
and
then
I
used
to
that,
and
also
we
can't
really
leverage
the
tools
that
we
have
on
one
side
on
the
other
side.
So
that's
that
wasn't
no-go
for
us.
The
next
one
would
be
to
say:
oh
well,
let's
try
to
run
virtual
machines
inside
a
Windows
box.
So
that's
something
that
could
be
done.
It's
done
by
some
people,
but
most
of
the
developers
that
are
working
on
Windows.
A
Actually,
it's
hard
for
them
to
just
go
back
and
say:
well,
let's
try
to
run
and
us
just
for
the
online.
So
that's
something
that
we
can't
just
make
it
work
all
the
time,
although
it's
a
target
that
we're
trying
to
move
forward.
But
it's
still
too
hard
for
us
too
hard
for
the
programmers
now
the
next
step
to
say
well,
can
we
have
a
bridge
or
something
that
it
will
actually
be
inside?
A
Your
windows
could
use
all
the
technologies
that
we
know
in
kubernetes
and
just
go
ahead
and
say:
let's
use
that
and
go
forward
of
that.
So
that's
the
main
topic
that
we're
going
to
look
at
is
say:
VMs
talked
about
a
bit
above
the
MS
and
then
talk
about
the
bridge
that
we've
developed
because
we're
working
on
something
where
you
still
on
you're
still
on
Windows
but
you're,
using
all
the
tools
internally
to
talk
to
kubernetes
and
our
online
stuff.
A
So
the
thing
that
we
need
to
be
aware
of
it:
it
can
work,
it
needs
some
help
and
maybe
sometime
you
might
want
to
have
a
look
at
what
you're
actually
trying
to
propose
and
make
sure
it
doesn't
fail.
In
that
case,
I
think
somebody
missed
something,
but
it
can
work
so
we're
gonna
make
it
work.
So
what
are
the
bridges
that
we
can
actually
try
to
target?
A
Virtualization
I
just
talked
about
it
a
bit,
so
there
are
several
technologies
that
we
can
use
a
virtual
books,
I
Purvi
VMware.
That's
still
something
that
wasn't
tight
enough
for
us.
So,
like
I
said
it's
a
bit
too
far,
we
might
want
to
use
it,
but
eventually
not
right
now
and
the
other
problem
that
we
had
is
that
the
tools
that
we're
using
we're
using
docker
we're
using
mini
cube
for
kubernetes.
There
are
already
running
in
its
side
a
VM,
so
you
can't
run
docker
and
natively,
even
though
it
says
dr.
Sewell
windows.
A
It
actually
runs
inside
the
VM,
nine
Ivy
same
thing
for
a
Mac,
so
we
have
a
VM.
Then
if
you
have
multiple
VM,
then
it
starts
to
manage
multiple
VMs
and
people
get
confused
to.
Where
is
my
code
living?
How
do
I
bridge
to
vm
together
and
then
your
system
becomes
more
and
more
complex
and
then
we
don't
want
to
impose
that
on
people
we
want
to
make
it
as
easy,
as
can
be
for
the
game
developers.
Our
team
is
responsible
for
the
complexity,
but
they're,
not
the
people
paying
for
complexity.
A
So
what
we
ended
up
is
saying:
well,
how
can
we
make
a
command
shell
that
would
run
on
Windows
to
run
with
the
tools
first,
candidate,
the
command
shell,
PowerShell
and
side
windows?
Obviously
it's
there,
but
it's
not
a
good
fit
for
us.
It's
not
a
real
bridge.
It
actually
doesn't
help
you
doing
lots
of
things
that
you
want
to
do
like
your
to
complete
or
do
stuff
like
using
the
default
tools,
we're
still
keeping
the
dot
bat
files
support,
so
that
some
people's
are
actually
not
using
console
and
they
don't
want.
A
The
other
part
that
some
people
who
actually
just
jump
on
it
and
say,
go
let's
go
ahead.
Let's
go
use
the
Ubuntu
shell
inside
Windows
10,
that's
a
nice
option.
We've
tried,
we
looked
at
it
our
problem
right
now,
but
it's
trying
it's
moving
forward
is
that
we
were
not
on
very
on
Windows
10
on
the
whole
company.
Obviously
10,000
people
we're
not
just
moving
as
the
version
comes
out
there.
Let's
go.
It
takes
a
long
time
to
roll
so
rolling
production
by
production.
So
it
takes
a
bit
of
time.
A
The
next
this
seems
to
be
solved
with
the
next
edition
of
Windows.
That's
coming
up
in
April,
we'll
see
we'll
have
a
look,
but
still
that's
the
step
where
maybe
it's
still
a
bit
too
complex
for
us,
because
it's
still
an
OS
inside
it's
not
only
a
shell.
You
need
to
fully
manage
an
OS
I
need
to
know
that
it
is
Linux.
A
You
need
to
be
aware
how
the
next
works
now
it
might
be
in
the
future
something
we'll
address,
but
right
now
it's
not
a
short-term
game
that
we
can
have
the
next
one's
for
people
that
are
bit
aware
of.
What's
going
on
in
the
Windows
community,
try
to
bridge
the
UNIX
tool,
there's
cygwin
cygwin
we've
been
using
it
for
10
years
or
so.
But
now
we've
came
up
with
some
issues
like
the
setup
is
really
hard
to
automate.
It's
something.
A
I
know
there
are
some
project
working
on
that,
but
it's
not
natively
easy
to
do
it's
a
really
self
centric
view.
Cygwin
actually
doesn't
actually
say:
I
want
to
be
a
good
window
citizen.
It
just
says:
I
want
to
run
with
new
tools
on
Windows,
and
then
it's
done
so
sometime.
It
just
doesn't
operate
properly
with
the
windows
tools
it
doesn't
bridge
properly.
You
need
to
go
and
do
a
lot
of
manipulation
for
the
path
to
send
to
an
application.
A
Your
proper
Windows
path,
because
it's
sending
UNIX
bethenny,
assumes
that
everybody
will
consume
you
next
path,
so
that
led
us
to
the
friendly
Fork
of
cygwin,
which
is
called
Ensis,
and
this
actually
has
a
really
tight
integration,
the
focus
of
emesis.
It's
actually
have
a
tight
integration
between
Windows
and
the
new
tools.
A
It's
a
it's
used
by
git
for
Windows,
so
git
for
windows
actually
builds
on
top
of
insist
to
substitute
just
use
all
the
Linux
tooling
internally,
and
also
another
big
gain
for
us
is
that
it
there's
a
package
manager
because
the
older
version
of
m-systems
this
one
didn't
have
well.
No,
it
had
a
fracture.
Sorry,
it's
the
gate
for
Windows.
You
could
actually
use
the
bash
for
beautiful
for
Windows
internally,
and
it
will
actually
give
you
a
insist
subsystem.
A
The
problem
is:
there's
no
package
manager,
so
you
can't
install
new
packages,
so
I'm
sis,
the
the
native
version,
will
actually
allow
you
to
use
pac-man
as
a
package
manager
and
we'll
come
back
to
why
it's
important,
because
there's
a
really
key
issue
that
we
needed
to
have
that
it's
good
news.
It
works
so
we've
been
using
that
it
works
and
works
fine,
so
there's
some
tweaks
need
to
do
to
actually
set
it
up,
but
it's
fairly
straightforward.
A
Now,
once
we
have
a
bridge
that
actually
says
well,
we
can
use
the
native
tools
and
it
can
use
and
be
closer
to
linux.
Let's
look
at
the
tools
that
we're
using
and
what
are
the
issues
that
are
being
encountered
while
we're
trying
to
run
on
Windows
first
one
get.
Obviously
we
came
up
from
the
windows
world,
so
we're
using
perforce
we've
been
using
other
stuff
beforehand
and
now
we're
using
git
and
get
for
Windows
works
superbly.
That's
no
problem!
It
works
fine,
it
does
provide
an
emphasis
to
shell.
A
Like
I
was
telling
you
so
you
can
actually
use
git
bash
up
to
a
certain
point.
The
issue
that
we
have
is
that
there's
an
issue
being
open
right
now
and
get
four
windows
that
it
cannot
clone
while
it
can't
clone,
but
it
cannot
check
out
files
that
have
illegal
windows
characters.
So
the
column
is
an
illegal
Windows
character
for
a
file.
You
can't,
you
know
not
to
use
it
for
enough
filing.
Now.
A
We
have
something
called
a
go:
Client
SDK
that
we're
using
the
cube
root
is
go
client
and
it
has
a
small
vendor
called
docker
inside
there.
That
has
a
file
that
has
a
column,
so
we
couldn't
use
actually
go
SDK
on
Windows
if
we're
not
using
for
using
get
for
Windows.
Now,
if
you
use
the
m62
package
manager,
you
can
install
the
mcs
to
get
client
and,
if
used,
that
client
that
client,
because
it's
pausing
base
actually
will
allow
you
to
use
column
files
with
column
inside
Windows.
A
So
if
we
were
not
to
use
the
m62,
we
can
actually
build
the
go
client
on
Windows
right
now.
So
that's
why,
for
us,
the
package
manager
was
really
important.
Now
next
step,
once
we
have
get,
we
can
actually
start
using
docker
we've
been
using
docker
for
more
than
a
year.
It
works
pretty
good.
There's,
no
big
problem,
we're
using
the
VirtualBox
version.
Obviously
we're
not
using
the
Windows
10
with
hyper-v,
because
we
don't
have
Windows
10
everywhere
we're
starting
moving
forward.
We
have
it
working,
but
people
are
not
using
it
right
now.
A
A
It
might
be
to
to
our
infrastructure
it's
something
that
we
noticed,
and
the
other
thing
is
that
whenever
you
take
snippets
from
the
web
well,
nobody
actually
assumes
that
you're
gonna
be
running
on
Windows,
so
everybody's
going
to
say
well,
I'll
use
this
and
it's
gonna
work,
notably
the
mount
version
from
darker
run
or
stuff
like
that.
You
want
to
do
Mouse
local
mount,
something
like
this,
which
actually
just
mounts
your
working
directory.
A
So
you
can
do
something
on
your
local
directory
inside
a
container
will
not
work
at
all
if
you're
actually
not
doing
the
proper
amounts
and
inside
the
virtual
machine.
Now
people
are
get
someone
confused,
sometimes
that
the
darker
demon
runs
inside
a
VM.
It
will
actually
try
to
mount
the
directories
inside
the
VM,
not
your
local
directory,
so
you
need
to
mount
between
a
VM
and
nura
local
directory.
Do
a
mount
a
proper
amount.
A
I,
don't
expect
you
to
look
at
that
code
and
pick
it
up
right
now,
but
we're
doing
that
so
we're
doing
something
on
top
saying
by
the
way,
just
don't
only
mount,
because
docker
for
Windows
only
mounts
the
C
users,
but
if
you
say
I'm
working
on
the
D
Drive
or
AF
Drive
or
whatever
it
should
actually
be
there
and
be
available.
So
we
did
something
for
that.
A
That's
something
to
be
aware
of,
because
if
you
take
snippet
from
the
web
it
actually
will
never
work
and
people
get
confused
and
they
eventually
start
working
in
places
where
they're
not
quite
sure
why
it
works.
Sometimes
because
you
even
see
users,
but
if
you're
outside
doesn't
work,
and
you
don't
know
why.
Well
that's
why
you're
you
have
to
mount
your
drives.
A
The
other
thing
with
VirtualBox
in
India.
Where
is
it
suppose,
X
like
file
system
and
the
like
part,
is
really
important.
It
actually
doesn't
enforce
the
the
the
case
sensitivities,
so
you
can
actually
write
some
father.
We've
been
we've
been
bitten
by
that,
and
sometimes
is
you
can
write
some
files
that
are
not
compliant
with
POSIX,
so
you
have
uppercase
and
lowercase
that
are
mixed
and
then
you're
not
using
the
proper
ones,
and
it
would
work
fine
on
your
VirtualBox
and
once
you
push
it
on
communities,
then
start
not
to
work
anymore.
Then
you
get.
A
You
start
to
figure
out
exactly
what's
happening
and
then
you
find
out
well
I
didn't
help
me.
There
sometimes
is
also
shadows
file.
So
I've
noticed
that
sometimes-
and
we
don't
know
exactly
we're-
still
investigating.
Why
does
that?
But
sometimes
I
would
change
the
files
on
my
file
system
and
then
run
it
on.
A
The
container
container
doesn't
pick
it
up
because
the
virtual
machine
actually
sort
of
shadowed
the
file
and
it
caches
for
some
reason,
and
we
had
some
several
issues
with
containers
that
were
built
on
Windows,
because
we're
building
the
containers
directly
on
Windows
doing
that
Windows
does
have.
It
doesn't
have
any
notion
of
permission
file
permissions,
so
the
permission
get
spewed
some
time
and
in
sometimes
well
actually
not
run.
So
all
the
executable
flags
are
not
transferred
automatically.
It
could
actually
make
some
issues
also.
We
had
some
issues
where
we're
using
scratch
containers.
A
Now
this
is
nice,
four
go
whenever
you
do
go
tooling
to
use
a
scratch
container,
which
makes
it
really
small.
If
you
want
to
know
about
that,
you
can
actually
ask
me
afterward
or
just
read
it
on
the
net,
but
the
problem
is
that
we
found
out
that
gold
does
cross
cross
compiling
and
using
a
scratch
container
actually
works.
Fine
if
you
build
the
image
on
Windows,
but
if
you
run
it
on
Linux,
it
actually
doesn't
work.
A
So
we're
still
in
this
investigating
that
we
found
out
that
pretty
recently
now
next
step
once
we
have
docker
well,
we
want
to
get
closer
to
me
to
a
quarantine,
so
you
were
using
mini
cube,
we're
really
heavy
a
user
of
mini
cube.
We
haven't
worked
for.
We
wanted
to
rate
really
fast,
so
we
do
all
our
work
locally
and
then
eventually
we
push
on
the
cluster
to
us.
That's
really
interesting,
because
the
Windows
version
is
still
experimental,
but
we've
been
using
it
for
a
year
now.
A
So
we
would
like
to
get
it
out
of
experimental
and
say
well.
We
want
to
have
full
support.
We
did
some
contribution
to
the
mini
cube
project
to
help
fix
some
issues
with
the
hyper-v
I
did
part
of
the
build
system
for
able
to
make
file
for
Windows
and
we're
still
working
and
we're
keeping
this
on
track.
A
There's
not
an
installer
and
that's
a
tiny
issue,
but
the
thing
is
that
on
Windows,
the
old
sudo
curl
do
something:
it's
not
something
that
people
are
aware
of,
that
they
can
actually
use,
and
they
they
will
jump
on
the
Installer
most
of
times
just
really
and
say:
oh,
when
I
start
I'm
going
to
try
this
and
installer
is
more
safe
for
people
and
more
in
their
world,
but
meaning
cube
other
than
that
works.
Fine.
We
don't
have
any
issues
that
we're
still
using
it
on
a
daily
basis.
A
A
That's
part
of
my
job,
so
we
did
contribute
some
issues
and
then
we
fixed
them
this
some
contribution
to
make
sure
that
we
actually
can
create
archives
on
Windows
and
consume
them
on
Linux,
because
it
wasn't
the
case
the
tests
weren't
running
properly
on,
so
we
fix
all
of
that
it
works
now.
The
big
big
point
was
that
it
was
assuming
Linux
pad
for
everything
so
on
Windows,
the
archives
that
are
created
could
have
patent
that
are
not
linux,
based,
so
the
backslash
versus
for
a
slash.
A
So
the
key
point
about
this
is
to
make
sure
you
join
the
right
path.
So
you
use
the
proper
path
and
go
so
that's
go
code.
If
you
do
path
join
that
will
actually
lead
you
for
the
first
answer,
using
a
URL
base
forward,
slash
slash
and
if
you
use
file
path
join
while
that
use
the
OS
file
path,
which
actually
leads
you
to
the
second
answer.
A
So
you
need
to
make
sure
they
use
the
proper
one
at
the
proper
place
and
not
assume
that
everything
will
be
always
forward
facing
because
on
Windows
it
is
not
so
be
aware
of
that
cube,
control,
cube
cattle
because
we
call
it
cube
control.
So
that's
the
issue
community
we're
using
that
obviously
has
good
support
for
Windows.
It
works.
Fine.
We
didn't
have
any
big
problem,
obviously
we're
in
the
corporate
world.
So
we
have
a
proxy.
A
A
Well,
it
does
exist
and
we
make
it
there
and
we
want
to
use
it
so
make
sure
that
we
can
actually
use
that
so
cute
control
will
actually
use
that
now.
All
the
tools
that
are
built
on
side
on
top
of
the
go
client
will
actually
be
able
to
use
that,
so
make
sure
that
we
can
actually
knowledge
that,
because
we
had
some
issues
sometimes
and
now,
fidgeting
with
the
home
drive
on
Pat
on
Windows,
it's
a
bit
hard,
the
go
programming,
language,
that's
only
a
slide
to
say
it
works
superbly
nice
for
tooling.
A
We
were
really
surprised
that
cross
compiling
just
works
out
of
the
box
working
our
tools
on
Windows,
we're
building
most
of
our
controllers
or
any
tools
that
runs
on
currencies.
Actually,
we
make
it
run
with
the
go
client
on
Windows,
the
honor,
our
machines
talking
to
the
cluster,
so
it's
all
set
it
faster.
We
can
actually
debug
and
do
all
our
stuff
and
then
once
it's
ready,
we
just
sort
of
cross,
compile
it
and
make
it
run
on
the
containers
and
it
run
exactly
the
same.
It
runs
fine.
So
that's
really
really
nice.
A
So
that's
a
really
good
thing
from
the
go
tool.
So
again
it
works.
It's
not
like
everything
is
not
working,
it
all
works.
We
fix
a
lot
of
the
issues,
but
it's
still
out
there.
So
we
need
to
be
make
sure
that
people
are
aware
that
it
will
be
there
now
the
action
that
we
can
take.
So
what
can
we
do
with
the
current
community
to
make
it
so
that
we
don't
have
next
to
next
generation
of
tool
to
have
everybody
go
through
the
same
process
that
we're
doing
right
now?
So
how
can
we
help?
A
Let's
take
two
sides
of
the
equation
here.
The
first
one
would
be
has
two
consumers.
So
if
you
are
working
on
Windows,
you
want
to
work
and
say
well:
I
have
to
work
on.
Windows
I
have
to
make
my
tool
chain
work
properly.
Well,
the
first
thing
is
obviously:
if
there
are
new
tools
coming
up
well,
just
ask
for
Windows
support
and
just
say
be
vocal
about
it.
Be
there
and
say:
oh
I'm
I'm
working
on
Windows
could
could
we
make
it
work
and
you
cross
compile
it?
A
Please
you
do
something
then,
once
it's
there
give
some
feedback,
if
you
just
say
well,
it
doesn't
work
and
then
I've
asked
and
I'm
done.
Well,
that's
probably
not
good
enough.
It's
not
gonna
make
everything
go
forward,
so
give
some
feedback,
and
if
you
can
just
go
ahead,
currently
contribute
I've
done
that
and
then
people
are
really
welcoming
for
any
contribution,
mostly
on
Windows,
because
people
actually
most
of
the
programmers,
are
working
on
Linux
on
Mac
OS
and
they
sometimes
don't
even
have
a
box
to
actually
test
it.
A
A
Next,
if
we
say
well,
you
consider
the
other
part
of
the
equation
is
the
actually
tool
builders
so
tool.
Builders,
if
you
actually
build
some
tools
and
you
want
to
open-source
some
tools
and
you're
not
familiar
with
Windows
or
you'd,
say
well,
I'm,
not
I.
Don't
have
any
resources
to
do
that.
Well,
try
to
find
contributors
find
people
that
are
actually
active
in
your
community
active
in
your
issue,
tracker
and
say:
oh
I've
tested
this
and
that
and
try
to
fetch
them
and
say
well.
Do
you
want
to
become
a
contributor?
A
That's
always
a
nice
pirate
to
say
well
here
it
is
maybe
a
prize.
You
can
become
a
contributor
if
you
just
push
a
bit
forward,
build
and
test
on
Windows.
If
you
write
tools
using
go
or
pythons
fairly,
is
it
actually
build
on
Windows
and
testing
windows
also
for
open
source
projects,
there's
something
that
people
might
not
be
aware
of.
There's
something
akin
to
Travis
or
Circle
C
I
call
advair,
which
is
a
Windows
open
source
free
tool
chain
that
you
can
actually
make
your
stuff
run
on
Windows
and
test
on
a
Windows
machine.
A
So
that's
something
that
might
be
more
taking
your
taken
account.
The
other
part
that
I've
touched
briefly
is
the
right
installer.
If
you
have
time
you
can
actually
write
installer,
we
did
that
I
fixed
the
Installer
for
mini
cube,
so
that
if
you
people
just
come
in
and
they're
really
windows
centric
and
they
say
well,
I
want
to
try
to
do
this
and
try
to
test
it.
Having
an
installer
is
really
in
a
good
entry
point,
it's
easy
for
people
to
go
back
there.
A
Also,
if
you
want
to
go
even
further
than
that
and
say
well,
I
think
the
windows
community
is
really
important
and
I
want
to
cater
to
that
community.
You
might
want
to
start
writing
PowerShell
script,
that's
something
that
we're
working
somewhat
internally,
not
a
lot,
but
that's
something
that
people
actually
consume
really
readily,
because
that's
something
where
they
live
in
that
world
and
using
bash
good
for
them
is
something
alien
in
Alien
a
bit.
A
A
So
eventually,
we'll
have
actually
people
working
in
Windows,
running
Windows
containers
inside
kubernetes
or
communities.
The
community
needs
to
be
aware
of
that
and
be
open,
say
well.
Yeah
we're
gonna
have
some
different
people
coming
up,
but
they're
they're,
nice
I'm.
Actually.
So
this
concludes
my
talk.
If
you
have
any
experience
or
people,
you
want
to
share
some
stuff
that
you've
done
on
your
side
or
maybe
some
stuff
that
I've
talked
about.
If
you
have
any
question,
I'm
open
for
a
question
right
now.
Obviously
this
is
our
experience
with
our
need,
our
constraint.
A
A
A
A
We
haven't
actually,
while
the
question
is
that
sometimes
the
emphasis,
even
though
you're
using
emphasis
emphasis,
actually
has
some
different
terminals
and
if
you're,
using
some
terminals
that
connect
to
a
container
or
do
remote
execution,
let's
say
you
attach
to
the
using
the
minus
T
Y
terminal,
interactive
command
on
docker
or
kubernetes.
Actually
it
doesn't
render
properly.
So
sometimes,
when
we
notice
is
that
the
backspace
doesn't
work
or
the
shell,
the
higher
completion
doesn't
work,
actually
the
rendering.
Sometimes
it
actually
doesn't
work
at
all
you
just
you,
don't
see
anything
so
to
us.
A
What
we've
been
doing
so
far
is
that
we've
been
trying
different
terminals.
I
know
that
some
terminals
are
better
than
the
other
one.
So
we
need
to
go
and
finish
the
fiddle
with
those
we
haven't
actually
solved
it,
and
then
we
didn't
say
well
is
right.
Now
it's
just
good
enough
for
what
we're
doing,
but
we're
pushing
them
toward
production
and
we'll
see
actually
if
the
developers
are
actually
asking
or
more
for
that.
But
obviously
that's
an
issue
that
if
you
really
want
to
have
a
tight
integration
with
the
terminal
and
your
your
piping.
B
A
A
So
if
you
want
to
use
I,
don't
know
I,
don't
remember
them
and
on
top
of
my
head,
but
there
are
different
ones
and
then
some
of
them
are
better
than
others
like
I
want
to
use
tea
mugs
on
side
windows,
but
I
can't
use
the
native
terminal
from
em.
Sis
I
need
to
use
another
one
to
make
it
work
properly.
Otherwise
the
rendering
doesn't
work.
So
you
need
to
play
around
with
that
and
try
to
figure
out
which
one
is
good
or
not.
B
B
A
So
the
remark
was
that
Diaz
code,
the
product
for
Microsoft,
is
actually
a
cross-platform
ID
ID
editor
with
Brandon
burns.
Moving
over
to
Azure.
He
actually
came
back
and
said:
how
can
we
make
it?
So
Brendon
is
working
a
lot
on.
How
can
we
make
it
easier
for
people
to
work
and
he
did
some
integration
side
vs
code,
so
you
have
some
commands
that
are
directly
run,
so
you
don't
need
to
go
and
run
queue
control
from
the
shell.
You
can
actually
run
it
from
your
IDE.
A
The
reason
why
I
didn't
mention
it
right
now
is
that
we
actually
have
don't
have
anybody
using
that
right
now
in
the
company
we
have
lots
of
vim
users
and
other
stuff
like
that,
but
obviously
that's
a
good
point.
You
can
actually
go
there
and
then
maybe
you
don't
even
need
to
go
to
the
shell
and
you
have
the
tight
integration
that
is
just
there.
In
our
case,
we
we
still
using,
go
and
go.
We
use
the
make
files
and
everything
so
we
need
to
have
a
make
that
is
native.
A
C
A
A
Well,
I
can't
obviously
go
into
details
with
that,
because
I'm
not
allowed
to
right
now
we're
still
in
flux
so
entirely
in
the
UV
stuff.
We
do
have
an
internal
cloud,
so
we
have
a
team
at
UB
sub
dedicated
to
do
internal
cloud,
what
we
we've
been
using
OpenStack
and
we
have
VMware
and
we
have
a
lot
of
stuff,
so
we're
actually
pretty
solid
with
that.
Now
we're
actually
going
to
the
public
cloud
to
solve
the
scalability
issue,
because
on
our
side
we're
really
good
at
racking
and
doing
all
our
stuff.
A
Now,
obviously,
we
can
track
as
fast
as
the
users
are
growing
inside
a
better
lunch
or
something
like
that.
So
we're
not
there.
So
we
started
doing
a
hybrid
stuff
internally.
What
I
can
say
is
that
we're
working
on
a
cube,
cube,
ception
sort
of
solution,
so
we
want
to
have
multiple
clouds,
so
we're
not
gonna
have
one
community
cloud
for
the
whole
company.
Obviously
each
production
has
different
needs,
so
we're
probably
gonna
cater
for
each
different
games
and
have
different
clouds
and
we're
working
a
solution
to
have
a
on
demand.
A
Clouds
demand
clusters
for
each
of
our
games
if
they
want
to
have
it
so
we're
working
using
kubernetes
the
cube
section
so
actually
using
communities
to
create
to
to
Burnet
these
clusters.
That's
something
that
we're
working
so
we're
starting
fully
committed
to
say
where
you're
using
communities.
Now
we
will
check
or
not
that
doesn't
a
different
issue
and
that's
where
we're
working
right
now
to
make
it
move
forward.
So
we're
trying.
We
have
a
lot
of
legacy
code
that
we
have
legacies
platform
and
then
we
ended
up
saying
well
we're
up
to
a
point.
A
A
A
Yeah,
okay,
the
question
is:
if
we
what's
our
CI
CD
pipeline,
obviously
in
the
first
source
do
you
have
travis
circle
CI
and
everything
right
now,
we're
actually
using
get
lab.
So
we
have
an
internal
gate,
lab
instance
and
we're
working
try
to
solve
and
try
to
see
if
we
get
labs
a
proper
fit
for
us
to
make
sure
that
we
can
use
the
gate
lab,
see
ICD
solution
in
there.
So
far
it's
working
pretty
good.
We
don't
have
lots
of
issues.
A
The
the
way
that
we're
working
with
our
team
right
now
is
that
we
would
develop
on
Windows,
but
we
deploy
on
Linux.
So
basically
our
CI
is
all
in
Linux,
so
we
don't
have
anything
working
in
a
window,
so
we're
not
provisioning
Windows
machine
to
develop
our
tools.
So
that's
why
we
found
out
some
issues
that
running
our
container
is
local
in
our
machine
works
fine
on
Windows,
and
then
we
push
it
on
the
CI
and
it
sort
of
breaks,
and
you
know
why:
okay!
Well,
that's
because
we're
using
a
full-blown
Linux,
CI
solution.
A
A
A
Yeah
yeah:
this
is
it's
not
because
it
wasn't
working
with
Windows,
because
we
have
other
people
actually
have.
They
have
a
CI
on
Windows
on
gate
lab,
but
right
now
the
what
this
might
let
us
come
to
that
I
did
just
before
coming
over.
Here
is
I'm
actually
using
the
kubernetes
runners
inside
the
gate
lab
to
make
it
work
so
that
our
runners
are
actually
running
on
kubernetes
inside
our
stuff,
so
that
we
have
a
full-blown
we're
using
communities
as
a
tool
and
also
developing
communities
so
sort
of
make
it
the
full
circle.
A
Well,
right
now
we're
still
developing
our
pipeline
and
working
our
stuff.
What
I
presented
so
far
is
that
the
tools
that
we're
using
on
a
daily
basis
so
to
us
the
the
mini
cube.
That's
why
I
was
saying
mini
cube
is
experimental
in
Windows,
but
obviously
to
us.
It's
not
experimental
this
production
great
because
we
were
using
it
so
that
our
developers
we
want
to
make
sure
that
it
still
works
helm
to
us
is
part
of
our
pipeline
delivery.
A
Well,
that's
running
on
the
cluster,
so
it
doesn't
make
any
difference
for
us,
so
we're
not
involved
in
there,
but
we're
contributing
right
now
to
Elm
and
Mini
Q.
So
these
are
the
two
things
we've
contributed
to
the
add-on
for
the
local
registry,
so
the
registry
credential
mini
cube
as
well.
Community
works
with
a
set
of
credential
that
needs
to
be
set
properly,
to
actually
fetch
from
local
registries
and
docker.
It
used
to
work
in
a
certain
way
with
the
old
boot
boot
to
docker
image.
Now
they've
changed
the
image.
Now
it
wasn't
working.
A
Somebody
did
the
contribution,
but
it
was
only
for
Amazon
and
Jiki.
We
did
the
contribution
to
make
it
work
properly
inside
a
local
registry.
For
so
again,
that's
another
place
where
people
need
to
be
aware
that
inside
a
company
we
were
not
exposing
all
of
our
image
outside
all
the
time
and
there's
another
issue
that
we're
working
closely
with
Google
right
now
and
giving
feedback.
Is
that,
basically,
if
you
run
a
cluster
and
you
have
a
local
registry-
that's
fine!
Now,
if
you
want
to
start
pushing
on
they
say
Google,
registry
or
Amazon.
A
Now
your
images
are
sort
of
built
with
the
the
darker
darker
uses,
an
URL
well
well,
the
URL
is
actually
local
to
my
machine
or
local
to
my
system,
which
doesn't
scale
out
to
the
Google
cloud.
So
how
can
we
solve
that
to
make
it
so
that
it's
only
a
convenience
that
we
change
on
the
cluster?
Saying
oh
by
the
way,
could
you
change
this
to
that
environment
variable
something
like
that,
so
we're
working
with
them
to
make
sure
that
this
works,
but
that's
a
different
issue.