Repository directory structure

DataONEorg / api-entrypoint

The DataONE Kubernetes cluster's API ingress controller component that is shared between microservices

0 stars 1 forks source link

Repository directory structure #3

Closed gothub closed 2 years ago

gothub commented 3 years ago

@csjx Possible contents of this repo are:

files needed to deploy the k8s NGINX Ingress Controller and Virtual Server resources
files needed to deploy a HAProxy or other load balancer / reverse proxy

Here is a proposed directory layout for the repo:

- deployments
  - haproxy?
  - nginx-ingress-controller
      - virtual-server
        - helm-chart
        - manifests
          - common
          - deployment
          - rbac
          - service
- docs

How does this look to you? Is there anything else that might be in this repo?

csjx commented 3 years ago

Heya @gothub - Yup, that looks good. We can adjust as needed, but it seems like everything of significance will be a deployment, and if we use something other than haproxy we can adjust. Thanks!

gothub commented 2 years ago

k8s control plane, networking, RBAC, etc is described in the k8s-cluster repo.

Individual k8s app deployments are maintained in their own repos: