Chapter 14. Future Considerations
Throughout this book, we have focused on the general operationalization of Argo CD, including deploying, configuring, and managing the application. While we touched on several different technologies and practices, the ecosystem surrounding Argo CD is much broader, and other considerations will need to be taken into account as you progress through your Argo CD journey. This ecosystem is still evolving, and many patterns are emerging, so it is important to know how to engage with the community and investigate new practices, patterns, and common approaches.
This chapter will provide the context and resources you need to get the most out of your Argo CD implementation—both now and in the future.
GitOps Is Still Evolving
While operationalizing Argo CD is an important topic, it is imperative to recognize that Argo CD was built with GitOps at its core. This alignment necessitates that any effort to operationalize Argo CD should inherently incorporate GitOps best practices and strategic pattern planning to maximize the efficiency and effectiveness of any Argo CD implementation. To achieve optimal results, it is essential to consider the broader implications of GitOps to better integrate it with DevOps. This will contribute significantly to the robustness of your Argo CD implementation.
While the GitOps principles have reached v1.0, patterns and implementations are still evolving; best practices are emerging as adoption grows for not only Argo CD, but ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access