Do you want your multicloud
deployments to be boring
or like a roller coaster?
I'm Chris Lazzaro from IBM,
and I'm going to talk to you about
GitOps.
for multicloud.
But before I do that, please be sure
to like and subscribe.
The approach we're going to talk
about today is simple.
Consistent.
And secure.
Now, typically, when
customers are building applications,
they start out with an on-prem
environment.
And they have a GUI and a CLI
for managing that environment.
But then they want to move to the
cloud and utilize cloud
environments, so they start using
a cloud.
And it has its own GUI
and its own CLI,
and things get a little bit more
complicated.
And now they have hybrid cloud apps
that are stretching across on-prem
and cloud.
And these different environments
can be difficult to manage.
But the advantages of cloud are
there, and so they continue,
and now they add additional
clouds in
order to have the flexibility
to move their applications
from one cloud to the next or use
multiple clouds for different
purposes.
So now you've had a GUI and CLI
across your on-prem,
your first cloud and any other cloud
that you're using, and things
start to become pretty difficult.
Now, OpenShift helps.
OpenShift provides a secure,
consistent way of managing
your infrastructure and
applications.
No matter whether they're on-prem
or in the cloud.
But we're going to take things a
step further and show how GitOps
can really manage everything
through Git operations.
So you have your Dev team.
And they are used to
doing all of their work inside of
Git. So source code is all managed
within Git.
And you have your Ops team.
And they're in charge of managing
all of your different environments.
So how do we bring Dev and Ops
together?
Well, we can set up repositories
for infrastructure.
For services.
And for the applications.
So when we go and look at your
deployed environments,
your dev,
your test,
and your prod environments,
can all be managed in your
infrastructure repo.
And then when you start deploying
services that your application
depends on things like a messaging
service that can
be managed as well in the
services repo.
And then the application itself,
you've got your application, the
source code continues to be managed
in the application repo.
So when you deploy that,
you've got your front-end and your
back-end.
That, again, is all managed
in Git.
And so rather than using the
different management consoles.
When you check in to Git.
You've got tools that are
automatically ensuring your get
environment manages
and matches your production
environment, so as changes are
made over here, they
get deployed and
mimicked over here so that they
match.
Now, one funny story is when
we were demoing this to
a customer, we started setting up
this whole environment.
And so we had our
Git repo, but get is pretty boring
to demo. No one wants to see a pull
request.
And we started showing OpenShift,
but no matter where we were, whether
we're on-prem in our one
cloud or another, cloud OpenShift
looked exactly the same.
So we started to pull up the
individual management consoles
and we realized we don't even have
access to the third party management
console or the team that was setting
this up was using a shared account
that had been locked down.
So even, even
demoing this stuff, we were
showing the value of GitOps because
it was
very secure in the fact that
we didn't even have access to show
those management consoles.
So GitOps is an approach that's
simple and consistent and secure
for managing your environments.
And you don't have to be like a
roller coaster, you can have boring
deployments across multicloud.
Thank you. If you have any
questions, please drop us a line
below.
And if you want to see more videos
like this in the future, please like
and subscribe.