> Hi there. I'm Brendan Burns,
Co-founder of the Kubernetes open source project
and Corporate Vice President with Microsoft Azure.
We're focused on DevOps and
open source Cloud-native technologies.
I'm excited to share with you today
the future direction of Kubernetes containers,
open source, and DevOps on Azure.
As Kubernetes has moved from early adopter to ubiquitous,
we're seeing that Kubernetes is
really just the beginning.
The foundation for things that are built above.
For most enterprises we work with,
Kubernetes is a necessary but not sufficient element
of building their digital transformation.
It's a useful tool for improving agility
and reliability especially of their operations,
but they find that it's hard to use.
Knowing this, we built
the Azure Kubernetes Service to
be more than just technology.
We know that educating and helping
people to maximize their usage of
Kubernetes is critical to delivering
success in their digital
transformation of their enterprise.
We've embedded best practices via Azure Advisor into
the Azure portal itself so that
as you use the Azure Kubernetes Service,
it understands what you're trying to do,
and gives you personalized best practice recommendations
that are optimized for your deployments.
As we look to the future,
we're always looking to make AKS easier,
so that Kubernetes can be used
from beginners to expert Cloud-natives.
You can learn more about how we're
doing this at aka.ms/aksbaseline.
Another thing that's clear is that Kubernetes is
becoming the application vending machine.
What I mean by that is,
it's a fabric by which other applications can
be delivered anywhere from Cloud to Edge.
But it's clear to us that as Kubernetes moves
from just being in the Cloud to being in ships,
factories, and airports, unified
management of that Kubernetes is key.
There's going to be a hundreds or even thousands of
Kubernetes deployments for any given customer.
You need to be understanding
where those Kubernetes deployments are,
what applications are running them,
ensure that there's a consistent set of
utilities and other services running on that cluster,
understand what versions are running,
and make sure that every single cluster that you
have is up-to-date with the latest security patches,
and the latest compliance
regimes for your particular company.
To meet this customer need,
we've built Azure Arc for Kubernetes.
Arc for Kubernetes allows you to use tools like
Azure Security Center, Azure Monitor,
and Azure Policy to ensure that
your clusters are always healthy, secure, and compliant.
With Azure Arc, you can get a single pane of glass that
gives you the status of your Kubernetes
clusters at a glance.
Arc is actually even for more than just Kubernetes,
you can manage Linux servers, SQL databases,
and much more with a single consistent API,
a single policy framework,
and a single dashboard for visualizing
your digital estate no matter where it's located.
You can learn more at aka.ms/azurearc.
Kubernetes has emerged as
a key bridge between developers and operators,
truly forming the glue that enables DevOps.
New approaches like GitOps,
that enables seamless deployment of Kubernetes from
a simple git push are taking over the market.
We've looked and integrated with the Flux project;
an open source implementation of GitOps,
and brought it into the Azure Kubernetes
Service and Azure Arc.
With GitOps and Azure Kubernetes, and Azure Arc,
you can customize all of your Kubernetes clusters no
matter where they are in one single repo,
in one single location,
and ensure that there is
a consistent environment everywhere.
Git is also the core of
the technology that can bring you from code to Cloud.
Most of the development that people are
doing is out on GitHub these days,
and with GitHub actions you can directly integrate with
Azure container registry the Azure Kubernetes Service.
With these integrations and a simple YAML configuration,
you can achieve rapid,
reliable application roll outs to multiple regions,
manage your containers deployment
to container registries,
and truly achieved safe,
reliable deployments of applications no
matter where they need to go in the Cloud,
on-prem, or spanning from Cloud to Edge.
One constant theme, even in
this new Cloud-native world is
the requirements for security.
But even as the requirements for security,
you get more and more intense.
Thankfully,
Cloud-native and security technologies are weaving
together to provide new capabilities
for securing your workload.
A great example of this is
the integration of Azure Policy with
both the Azure Kubernetes Service as well as Azure Arc.
When you use policy and when you use
the predefined policies that Azure provides,
you can ensure that the only way for developers to deploy
their applications is one that conforms to
your organization's security requirements,
to the regulatory requirements of your industry,
whether it's healthcare, financial services, or more.
If you need to customize your own policy,
you have access to
a rich policy language for expressing all of
the different requirements necessary to deploy
secure applications in your application environments.
Beyond Policy, pod identity in
Azure Kubernetes as well as in Azure Arc
allows for different identities for
different roles within your microservices architectures.
This separation of concern allows for
the implementation of least privilege applications,
which is a security best practice.
Furthermore, when we look at
Azure Kubernetes and Azure Arc,
we've integrated them with all of
the great capabilities in Azure Active Directory.
That lets you use the best-of-breed
security and identity capabilities
in Active Directory,
like two-factor authentication,
just-in-time authorization,
IP restrictions, and more to
harden access to your production clusters.
The same groups that you use to
manage access to Azure resources,
and to the Word documents,
and PowerPoints, and all of your machines,
can be used to manage access to
your Kubernetes cluster as well.
Learn how you can use built-in
Azure Policy and AAD integrations to improve
your security at aka.ms/aks/policy.
The speed of open source adoption in
the enterprise is ever increasing.
Enterprises are realizing that community-driven,
vendor-neutral open source is
a core part of a modern technology strategy.
Rather than focusing their development teams
on undifferentiated heavy lifting,
they're using open solutions that even enable
best-of-breed technologies to be
adopted across the industry.
When we develop best-of-breed solutions
out in the open, everybody wins.
The total quality of software goes up.
We all get to come together
to work on the pieces that were
necessary to build reliable,
scalable Cloud-native applications.
Microsoft Azure is helping lead this revolution.
With projects like Helm,
and Dapr, and KEDA;
the Kubernetes Event-Driven Autoscaler,
we're not just making open source
that runs great on our Cloud.
We're contributing our innovations
back to the broader Cloud-native community.
But it's not just about creating new projects,
it's actually about sustaining the key projects within
the Kubernetes community and
the Cloud-native in ecosystem.
That's why we're doing key contributions
to Kubernetes itself,
to projects like F.lux,
the Linux kernel, and many of
the core open technologies that form
the basis of Cloud-native computing.
In addition to these contributions in the form of code,
we're also involved in leadership in
the special interest groups of Kubernetes.
We're involved in release management or
chopping wood and carrying water that's
necessary to make Kubernetes work.
If you're interested in learning more about
how we contribute to open source and
in particular if you're interested in checking out
some of the open source innovation like Dapr,
please check out how the Dapr open source project
is becoming the standard library for distributed systems.