Skip to content

Commit

Permalink
docs
Browse files Browse the repository at this point in the history
  • Loading branch information
ilackarms committed Nov 13, 2019
1 parent 8bedbce commit f1d63eb
Show file tree
Hide file tree
Showing 4 changed files with 17 additions and 3 deletions.
17 changes: 14 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,7 @@
# AutoPilot - The Service Mesh Automator

![](docs/img/logo.png)

**AutoPilot** is an SDK and toolkit for developing and deploying [service mesh operators]().

**AutoPilot** generates scaffolding, builds, and deploys Operators which run against a local or remote Kubernetes cluster installed with a Service Mesh.
Expand All @@ -12,7 +14,7 @@ Developers define an `autopilot.yaml` and `autopilot-operator.yaml` which specif

AutoPilot makes use of these files to (re-)generate the project skeleton, build, deploy, and manage the lifecycle of the operator via the `ap` CLI.

The `ap` CLI is designed to manage the full lifecycle of the operator, but this can be done with standard tooling (`go`, `docker`, `kubectl`, `helm`, etc.).
Users place their API in a generated `spec.go` file, and business logic in generated `worker.go` files. Once these files have been modified, they will not be overwritten by `ap generate`.

# How is it different from SDKs like Operator Framework and Kubebuilder?

Expand Down Expand Up @@ -54,11 +56,9 @@ AutoPilot is composed of 3 components:
# cleanup
- example
- docs
- code generated headers in the right places
- improve docs generation template
- bake templates into cli
- clean up CLI messages
- generate CLI docs

- idempotent generation of rbac yaml (rule ordering not idempotent)

Expand Down Expand Up @@ -87,9 +87,20 @@ AutoPilot is composed of 3 components:
- interactive cli
- automatic metrics for worker syncs
- automatic traces for worker syncs
- option to make workers persistent






# docs todos:
- architecture description. how does my AutoPilot operator work?
- how does autopilot generate code? when do i regenerate? when do i redeploy?
- user-project directory structure
- autopilot libraries/pkg directory structure
- e2e hello world guide
- tour-through-your-hello-world package-by-package



Expand Down
2 changes: 2 additions & 0 deletions doc.go
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
// Autopilot
package autopilot
Binary file added docs/img/logo.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
1 change: 1 addition & 0 deletions test/e2e/run_test_project.sh
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,7 @@ source ./assert.sh

echo "########## Init Canary project"
ap init canary --skip-gomod && pushd canary

echo "########## note: set \$LOCAL to scale operator pods to 0"

function k {
Expand Down

0 comments on commit f1d63eb

Please sign in to comment.