The purpose of Environment Operator is to provide a seamless application deployment capability for a given environment within Kubernetes. It can easily hook into existing CI/CD pipeline capabilities including our CI/CD pipeline as well as a typical Jenkins server through a Jenkins plugin.
Each environment (development, staging, production) has it’s own definition and a separate endpoint to perform deployments.
Currently Environment Operator supports Deployments, Services, Ingress and HorizonPodAutoscaler. We are actively working on Jobs and Stateful sets.
Users of Environment Operator should start with our [User Guide](https://github.com/pearsontechnology/environment-operator/blob/dev/User_Guide.md)
We also provide and [Operations Guide](https://github.com/pearsontechnology/environment-operator/blob/dev/Operatonal_Guide.md) for those deploying and managing Environment Operator itself.
And finally if interested in developing against Environment Operator, check our our [Builder Guide](https://github.com/pearsontechnology/environment-operator/blob/dev/Build.md)
