Fleet GitOps

The future of device management is declarative

Declarative device management

Most device management solutions have an API, but most do not provide comprehensive control over the admin console with configuration-as-code like Fleet.

Managing the Fleet UI console with GitOps means you have total declarative control over your devices.

Using GitOps with Fleet unlocks powerful automations that allow you to:

• Ensure every change is peer-reviewed
• Ensure every setting is version-controlled
• Easily roll back to a previous state
• Declare the state of the Fleet UI in code, continuously

Observable, reversible, and repeatable workflows

Nothing builds knowledge, trust and fosters engineering teamwork like peer-reviewed changes made in the open.

Collaboration on Fleet GitOps workflows helps to prevent problems before they occur. Version control means it is straight-forward to fix problems that do make it into production (nobody’s perfect...)

Another powerful technical benefit: less effort on long-term maintenance. Controlling the Fleet UI with code effectively means creating a library of stable, known-good configurations. They can be copied and modified for easily adding new management objects like device profiles and software installations without the endless sprawl of manually re-creating automations and scoping.

Rethink change managment

Replacing change management forms and risk assessments with asynchronous GitOps workflows and approvals can dramatically increase operational speed.

Stay the course

Changes made in the console or to devices directly can cause device state to “drift” - away from compliance, security posture and an organization’s intended user experience.

Choose automation over repetition

Applications build muscle memory. But, what could you do with the time gained back from manual tasks and visual scans in your current device management solution?

Cancel the CAB

How much does it cost organizations in time and money to get senior engineers and their bosses on an advisory board call to discuss information that could be in a pull request?

Make end users happy

Mired in engineering details, it’s easy to lose sight of an important, oft-stated goal that should be part of any device strategy aimed at operational excellence: enabling work.

Your culture matters, and so does ours

For some organizations, GitOps is a natural fit to the engineering culture even if IT teams lack experience or the practice is new.

If DevOps or GitOps is already used by an organization, device management engineers may be aware of the concepts and tooling. Having an internal example to follow can result in an easier path to adoption.

But, GitOps adoption is not always simple. Admins may resist unfamiliar workflows or solutions. They may also have concerns about losing the value of certifications or specialized training.

By meeting potential challenges with phased implementation and thought leadership, any team can successfully adopt Fleet GitOps. We’ve seen it and we’ve helped our customers do it.

Making GitOps benefits real

At Fleet, we believe that showing organizations how to migrate to GitOps workflows represents an enormous opportunity for them to increase engineering efficiency and operational speed. This ultimately improves both end user experience and enterprise compliance. We design the product around these goals. We want to help you achieve them.

One way we can help is by improving the product itself, which we’re doing everyday.

Another way we can help is through training. To learn more about GitOps, you can attend one of our free, hands-on, in-person GitOps workshops, or, you can request that one be delivered in your area.

Dan Jackson

Sr Manager Systems Engineering, Fastly