Skip to content

RPaaS operator manages reverse proxy as service instances inside a Kubernetes cluster

License

Notifications You must be signed in to change notification settings

arthurcgc/rpaas-operator

 
 

Repository files navigation

RPaaS Operator

This project has two parts: operator and API

Operator

The operator is responsible for managing RPaaS instances running inside the cluster.

Running locally

make local

Running in Kubernetes

  • build the docker image: make build
  • push the image to a registry accessible from your cluster: docker push ...
  • make deploy

API

The API doesn't need to run inside Kubernetes, but it needs credentials to access Kubernetes API, to manage RPaaS instances, binds and plans.

It follows tsuru service API contract.

Running locally

To run outside the cluster, it needs a KUBECONFIG env var, pointing to your Kubernetes configuration. Start the API with:

make api

Running in Kubernetes

When running inside the cluster, the API knows how to get the required credentials. Follow these steps:

  • build the docker image: docker build . -t my-registry/tsuru/rpaas-api
  • push the image to a registry accessible from your cluster: docker push my-registry/tsuru/rpaas-api
  • start with kubectl apply -f deploy/api.yaml

About

RPaaS operator manages reverse proxy as service instances inside a Kubernetes cluster

Resources

License

Stars

Watchers

Forks

Packages

 
 
 

Languages

  • Go 98.2%
  • Shell 1.4%
  • Other 0.4%