Skip to content

Transition Compose Files to Kubernetes Deployment #151

@arcsector

Description

@arcsector

💡 Summary

Deprecate Docker-compose in favor of an industry standard, Kubernetes, in order to allow for a more open and standardized adoption scale on these projects.

Motivation and context

Docker Compose has no truly standardized production deployment scale, especially on cloud infrastructure like AWS or Azure or GCP: https://docs.docker.com/compose/production/

This is a problem because this repository's whole point is to make tools created by cisagov accessible to the populous, and the repository's framework of choice is not very accessible. For one to create a production-ready version of this repository, one would have to either use Docker's proprietary Swarm technology (which also doesn't have widespread adoption or support among cloud providers), or convert all these files to Kubernetes deployments using something like kompose, which takes away from the whole point of this repository in the first place.

Implementation notes

Create deployments for all running containers, replicasets for those deployments, and services for all listeners. This can be started with the Kompose tool.

Acceptance criteria

A working sample Kubernetes deployment is created with accessible services for each tool.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions