June 2024 Summaries

Harness CCM has unveiled three new features designed to enhance cloud cost optimization through automated governance, intelligent commitment management, and efficient container orchestration. These innovations are crucial as organizations increasingly rely on cloud services for digital transformation, making cost management a top priority. The new capabilities include Cloud Asset Governance, which uses policy-as-code to automate cost management, security, and compliance tasks across multi-cloud environments; Commitment Orchestrator, which maximizes savings on AWS EC2 compute spend by using machine learning to manage Reserved Instances and Savings Plans; and Cluster Orchestrator for AWS EKS, which offers workload-driven node autoscaling and Spot orchestration for significant cost savings. Together, these tools provide a comprehensive solution for intelligent cloud cost optimization, enhancing Harness's existing offerings and supporting organizations in managing their cloud resources effectively.

LitmusChaos Cloud has transitioned to Harness Enterprise SaaS, offering users a free plan that includes comprehensive enterprise features with a limit on the number of experiment runs per month, thereby enhancing chaos engineering practices. This shift underscores the evolution of chaos engineering, propelled by tools like LitmusChaos, ChaosToolkit, and Chaos Mesh, and highlights LitmusChaos's vital role in setting industry standards. The Harness Chaos Engineering platform integrates with existing tools, providing extensive fault coverage, automated processes, and strong security governance, making it a robust solution for both community and business needs. The free plan encourages users to upgrade their chaos engineering efforts by offering easy access to enterprise functionalities, comprehensive documentation, and integration options with various CI/CD and observability tools. Over the past years, the chaos engineering ecosystem has transformed significantly, with LitmusChaos gaining widespread adoption across industries such as telecom, e-commerce, banking, and automotive, becoming a popular tool for defining chaos engineering principles. As the LitmusChaos team now forms part of Harness's Chaos Engineering group, they aim to create an industry-ready platform that meets business requirements, appeals to a broader audience, and supports automation and resilience. The Harness Chaos Engineering Free Plan serves as a community-driven effort to make chaos engineering accessible, allowing users to simulate failures, optimize recovery, and enhance system reliability, thereby reducing downtime and offering clear financial benefits.

Founded in 2011, Travis CI is a hosted Continuous Integration tool primarily used for projects on GitHub and Bitbucket, initially focused on supporting open source projects with free testing, though it introduced a new pricing strategy in 2020. It is known for its automated testing and notification system, as well as a build matrix that allows testing with different versions of languages and packages. However, alternatives like GitLab CI/CD, CircleCI, and Harness offer competitive features. GitLab provides a comprehensive DevOps lifecycle management within a single application, albeit with a learning curve, while CircleCI is praised for its secure build processes and ease of debugging, though it lacks in security and governance. Harness offers a broad range of features including Continuous Integration, Continuous Delivery, and Cloud Cost Management, with intelligence features that optimize testing and caching. Jenkins, another popular open-source CI tool, offers extensive plugin support but faces challenges due to its reliance on scripts and plugins, potentially introducing security vulnerabilities. When evaluating CI/CD tools, it is crucial to consider long-term needs and the unique features each platform offers to determine the best fit for an organization's software delivery requirements.

Harness GitOps offers a managed solution for scaling GitOps processes, addressing the challenges that large enterprises face when adopting GitOps principles. At the GitOpsCon event, industry leaders discussed the growing pains of scaling GitOps, with Adobe sharing insights from their journey in building an internal GitOps platform using Argo, highlighting common issues such as high load on GitOps engine components and the need for multiple instances. Harness GitOps integrates with existing tools like ArgoCD and Flux, allowing users to manage a vast number of GitOps applications through a centralized interface, thereby simplifying management and reducing the need for multiple ArgoCD instances. The platform's features, such as ApplicationSets and automated PR pipelines, enhance scalability and streamline change processes, helping teams focus on adoption rather than management. Overall, Harness GitOps provides a seamless and efficient path for enterprises to scale their GitOps strategies without the resource-intensive efforts of developing custom solutions.

The text discusses the versatility and utility of CircleCI Orbs, which are reusable scripts that help streamline common tasks in continuous integration pipelines, such as tool installation and testing, without requiring developers to write the underlying logic themselves. Although primarily designed for CircleCI, many Orbs can be run locally or in other environments like Harness CI, allowing developers to avoid the resource-intensive process of rewriting configurations for different platforms. The CircleCI Local CLI enables users to execute jobs locally, while Orbs can also be adapted to run outside of CircleCI by setting appropriate environment variables. The document highlights that Orbs serve as scripts that can be integrated into alternative CI environments, facilitating a smoother transition when migrating from CircleCI to other platforms, and underscores the ease with which developers can begin experimenting with this process.

Harness Delegate is a tool designed to simplify the implementation of chaos engineering within Kubernetes environments by automating resource discovery and chaos experiment creation, which enhances the overall user experience and system resilience. By running as a lightweight, stateless service within a Kubernetes cluster, it seamlessly integrates with the Harness platform and automates the identification of potential chaos test candidates, thereby reducing setup time and ensuring comprehensive and effective chaos experiments. This automation also leverages Kubernetes' Role-Based Access Control (RBAC) to execute experiments securely, thus allowing users to focus on analyzing results and improving system resilience rather than on the complexities of setup and management. The tool's ability to streamline onboarding and enhance security makes chaos engineering more accessible and effective, ultimately contributing to continuous improvements in system stability and reliability.

Harness Code Repository offers robust features like branch rules and CODEOWNERS to maintain code quality, enforce best practices, and streamline Git workflows, essential for a stable and high-quality codebase in collaborative development environments. Branch rules help manage permissions, streamline approval processes, and ensure consistent practices, leading to more reliable and maintainable code. Key rules include requiring reviews from code owners, setting a minimum number of reviewers, blocking unauthorized branch creation and deletion, requiring status checks to pass, and mandating re-approval for new changes. These features, combined with best practices such as clearly defining code ownership, setting reasonable reviewer numbers, and integrating continuous integration tools, can enhance repository management and collaboration. Dewan Ahmed, a Principal Developer Advocate at Harness, emphasizes the importance of these tools in delivering reliable and efficient code and shares his extensive experience in DevOps and infrastructure through public speaking and writing, while also advocating for underrepresented groups in tech.

Harness has introduced a series of updates and new features across its product suite to enhance software delivery efficiency and customer experience. The company has acquired Split Software to bolster its Feature Management and Experimentation capabilities, allowing for more robust A/B testing and feature adoption measurement. A new navigation system has been implemented to streamline user access to pipelines, while enhancements in Chaos Engineering and Cloud Cost Management provide improved experimentation speed and financial oversight. The Harness Code Repository now features code suggestions, secrets scanning, and seamless integration with other modules, along with a new tool for migrating Spinnaker pipelines to Harness CI/CD. Continuous Integration now supports self-hosted infrastructure caching, and Infrastructure as Code Management offers automated drift detection to maintain alignment between desired and actual infrastructure states. Additionally, the Internal Developer Portal has been enhanced with new APIs for better customization, and partnerships with Wiz and Semgrep have expanded security testing orchestration capabilities, integrating new scanner technologies into the pipeline.

Retrieval Augmented Generation (RAG) is a technique in Generative AI that enhances model accuracy by incorporating domain-specific information, such as a company's knowledge base or proprietary APIs, into the generative process. This method involves a retrieval system to fetch relevant data and a generative model to integrate it into responses, improving contextual relevance and reducing AI hallucinations. The text outlines a practical implementation using OpenAI's tools, vector databases, and Python to create a RAG pipeline that processes queries by embedding and retrieving text. It also explores the integration of feature flags through the Split platform to experiment with different parameters like text chunk size and model types, allowing developers to optimize AI features without altering code directly. The article provides insights into setting up and using feature flags for controlled experimentation and emphasizes the utility of Split in managing and deploying features efficiently, enabling dynamic adjustments based on contextual data.

Harness AI has significantly advanced the DevOps landscape by introducing various innovative features aimed at optimizing the software delivery lifecycle, enhancing efficiency, and reducing manual efforts. Key enhancements include automated code generation, which accelerates development by automatically generating code, comments, and tests, thereby ensuring consistency and minimizing errors. The Semantic Search feature allows developers to navigate codebases using natural language, simplifying the process of understanding complex systems. Dashboard Intelligence provides customizable reporting tools, enabling quick access to business insights, while ChaosGuard facilitates controlled chaos experiments, enhancing system resilience. These updates collectively streamline DevOps processes, allowing teams to focus more on innovation and less on operational management.

Opentofu, also known as OpenTF, is an open-source Infrastructure as Code (IaC) tool that allows users to define cloud and on-premises resources using human-readable configuration files, which can be versioned, reused, and shared. This blog post provides a step-by-step tutorial on how to create and manage Harness entities by reusing existing Terraform scripts, highlighting the process of installing Opentofu, setting up the environment, and migrating from Terraform to Opentofu. The tutorial guides users through creating various Harness entities such as Organizations, Projects, Services, Environments, Infrastructure Definitions, Kubernetes connectors, GitHub connectors, and Deployment Pipelines using Terraform modules. The integration of Opentofu with Harness allows for automated, consistent, and efficient management of continuous delivery resources, ultimately enhancing deployment processes and enabling teams to focus on innovation and delivery.

A CODEOWNERS file is a configuration tool used in Git repositories to designate specific users or teams as responsible for certain areas of the codebase, which enhances security, accountability, and efficiency in the code review process. It is particularly useful in monorepo settings, where multiple projects reside within a single repository, by ensuring that the appropriate stakeholders review code changes. The file allows for flexible assignment of ownership, using patterns and wildcards to specify files or directories, and can be stored in various locations within the repository. Although CODEOWNERS are linked to pull requests, they are not automatically assigned as reviewers to avoid unnecessary notifications, but their involvement can be requested manually. Best practices for using a CODEOWNERS file include defining ownership with appropriate granularity, maintaining consistency in ownership assignments, documenting the file's purpose and structure, and regularly testing to ensure accuracy. Dewan Ahmed, the author, is a Principal Developer Advocate at Harness and has extensive experience in solving DevOps and infrastructure challenges, with a commitment to fostering collaboration and maintaining code quality.