Skip to content
/ apps Public
forked from operate-first/apps

Operate-first application manifests

License

Notifications You must be signed in to change notification settings

riprasad/apps

This branch is 162 commits behind operate-first/apps:master.

Folders and files

NameName
Last commit message
Last commit date
Nov 17, 2022
Oct 6, 2022
Sep 30, 2022
Sep 19, 2022
Sep 21, 2022
Nov 19, 2022
Oct 4, 2022
Apr 6, 2022
Sep 23, 2022
Nov 28, 2022
Mar 4, 2022
Jul 21, 2022
Sep 20, 2022
Oct 6, 2022
Oct 21, 2022
Sep 30, 2022
Sep 7, 2022
Oct 17, 2022
Nov 3, 2022
Sep 20, 2022
Sep 30, 2022
Sep 30, 2022
Sep 20, 2022
Nov 18, 2022
Sep 20, 2022
Jul 5, 2022
Nov 25, 2022
Sep 1, 2022
Jul 5, 2022
Nov 15, 2022
Jul 18, 2022
Sep 30, 2022
May 31, 2022
Apr 7, 2022
Apr 26, 2022
Nov 24, 2022
Oct 7, 2022
Sep 20, 2022
Nov 18, 2022
Nov 22, 2022
Mar 30, 2022
Nov 9, 2022
Nov 23, 2022
Nov 8, 2022
Sep 19, 2022
Sep 1, 2022
Apr 8, 2022
Sep 19, 2022
Sep 1, 2022
Feb 10, 2022
Jul 26, 2022
Mar 10, 2021
Sep 1, 2022
May 6, 2022
Sep 20, 2022
Feb 22, 2021
Sep 24, 2020
Feb 17, 2022
Aug 31, 2022
Aug 31, 2022
Jul 15, 2021

Repository files navigation

Operate-First Apps

This repository serves as a centralized source of truth for the Operate First Community Cloud Offering.

In this repository you will find various OCP/K8s manifests that define the desired state of all our clusters and different services deployed on these clusters.

All manifests can be generated using kustomize. Though some builds may include encrypted data that require additional credentials (read more about how we encrypt files here).

All manifests found through this repo are deployed by our ArgoCD.

Documentation

All documentation can be found here.

What is an "App"?

Apps or Applications in this context refers to the ArgoCD notion of Application, as described in the ArgoCD docs. In short, you can think of an App as a collection of manifests that have a destination cluster where they should be deployed.

How does it work?

This diagram provides a simple illustration of the structure of a typical Application in this repo. In this illustration you can imagine an Application to be any group of manifests. These manifests belonging to an Application often make up a full deployment of a service which has end users (e.g. Grafana). Though sometimes, an Application may be just be a way to logically group a collection of manifests, like in the case of cluster-scope Application which harbors all cluster wide resources, configurations, and privileged resources.

Once a group of manifests are organized into a directory, they can be deployed using ArgoCD. To do this you simply need to create the application within ArgoCD, docs on how to do this can be found here.

Repo structure

You will also notice each app adheres to a structure made up of bases and overlays. This is a structure commonly found when using Kustomize. base directories contain manifests/configurations that are common to multiple clusters and generally don't harbor any cluster specific details. Within the overlays directory you'll find cluster specific configurations. A cluster specific folder within Overlays will inherit the manifests from base folders as needed, while also making patches/amendments specific to that cluster.

Contributing

We suggest ramping up on the following before attempting to work with the Apps repo:

We encourage you to browse around the following repos for issues you would be interested in tackling:

Beginner friendly issues are marked "Good first issue". Though you are welcome to take on any issue that interests you. If an issue is unclear or requires more information, feel free to reach out to us.

Please be sure to read the contributing docs here before making a PR.

About

Operate-first application manifests

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • Python 61.3%
  • Shell 32.3%
  • HCL 2.8%
  • Jsonnet 2.5%
  • Makefile 1.1%