Kubernetes Environment Management
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github
cmd
docs
example
hack/build
pkg
test
travis
vendor
version
.gitignore
.lgtm
.travis.yml
CHANGELOG.md
Gopkg.lock
Gopkg.toml
LICENSE
README.md
environment.sample

README.md

Environment operator dev

environmentoperatoricon

The purpose of Environment Operator is to provide a seamless application deployment capability for a given environment within Kubernetes. It can easily hook into your existing CI/CD pipeline capabilities by installing our Environment Operator Jenkins plugin to interface with environment operator and deploy your services.

Each environment (development, staging, production) has its own definition and a separate endpoint to perform deployments. Currently, environment operator supports Deployments, Services, Ingresses, MongoDB Statefulsets, and HorizonPodAutoscalers.

In order to begin deploying mircorservices through environment operator, you will need to start with the Operations Guide. The operations guide will provide the details required to get environment-operator itself deployed to a namespace and ready to manage your environment. Once environment operator is ready for use in your Kubernetes namespace, users of Environment Operator should start with our User Guide to deploy their microservices.

Additionally, for those interested in developing against Environment Operator, check out our Builder Guide.


Just Show Me How To Run It...

For those that would rather get an example running and then go back to read the docs on how to further configure environment operator, the quick start guide is for you...


workflow


Other documentation on Environment Operator: