October 2018 Summaries

The text outlines a method for deploying a Docker application across multiple cloud providers using Kubernetes and Cloudflare's services. Following an initial post on Dockerizing Java apps with Google’s Jib project, this guide delves into multi-cloud deployment, emphasizing the importance of credential management for Docker Hub, Google Cloud Platform (GCP), and Cloudflare. The process involves deploying containerized applications to GCP's Kubernetes cluster, using Cloudflare's DNS and proxy services for global access, and integrating CircleCI for continuous integration and delivery. It highlights configuring command line tools, managing credentials, and setting up a global load balancer with Cloudflare to route traffic to different cloud environments, ensuring seamless user experience. Additionally, the guide references a sample project on GitHub for practical implementation and further explores AWS deployments using kops and Elastic Load Balancers, ultimately achieving a transparent multi-cloud deployment.

The text discusses the utility of the Go programming language, particularly its simplicity in running tests, highlighting enhancements introduced in version 1.11. It introduces "gotestsum," a command-line tool written in Go, which improves the output of "go test" by making it more readable and useful for local development and continuous integration environments like CircleCI. The tool can convert test results into the JUnit format, which is compatible with CircleCI, allowing for the storage and analysis of test metadata. The text provides installation instructions for "gotestsum" both locally and on CircleCI, noting that it is pre-installed in the Golang CircleCI Docker image. Additionally, it mentions that "gotestsum" is maintained by Daniel Nephin from CircleCI and offers guidance on compiling a custom binary for various system architectures.

CircleCI has become the first continuous integration and continuous deployment (CI/CD) tool to receive authorization from FedRAMP, meeting stringent security and privacy standards essential for U.S. government agencies. This development allows federal developers to move beyond outdated CI tools and access the advantages long enjoyed by the private sector, such as reduced overhead and improved productivity. FedRAMP, established to streamline the security assessment and authorization processes for cloud technologies, uses NIST security controls to ensure compliance, enabling agencies to select vetted tools from a marketplace and manage risk effectively. The authorization process for CircleCI involved a comprehensive assessment, including audits and reviews by a third-party auditor, ultimately leading to its inclusion in the FedRAMP marketplace. This transition signifies a shift toward integrating security measures early in the development process, enhancing efficiency and effectiveness for federal IT systems.

The blog post introduces Jib, an open-source project from Google designed to simplify the process of building Docker and OCI images for Java applications, specifically highlighting its integration with Maven and Gradle. It explains how Jib reduces complexity and time by setting reasonable defaults and inferring entry points for Java applications, using a sample Spring Boot application to demonstrate its functionality. The post emphasizes the importance of credential management, especially when pushing images to registries like Docker Hub, and provides guidance on encrypting Maven credentials using Maven Encryption and CircleCI environment variables. Additionally, it details the setup of CircleCI for automating builds, including the configuration of settings and master passwords, to ensure deterministic and traceable builds. The blog encourages users to explore further deployment options in subsequent posts, offering insights into taking CircleCI workflows to advanced levels such as deploying to ECS or Kubernetes.