Skip to content

Commit

Permalink
dev guide reorg
Browse files Browse the repository at this point in the history
Signed-off-by: JENNIFER RONDEAU <[email protected]>
  • Loading branch information
JENNIFER RONDEAU committed Dec 18, 2018
1 parent c0ebdf3 commit 6e4faca
Show file tree
Hide file tree
Showing 11 changed files with 253 additions and 243 deletions.
225 changes: 0 additions & 225 deletions docs/build-from-scratch.md

This file was deleted.

81 changes: 81 additions & 0 deletions docs/developing/build.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,81 @@
# Build from source

## Build

You can build your Ark image locally on the machine where you run your cluster, or you can push it to a private registry. This section covers both workflows.

Set the `$REGISTRY` environment variable (used in the `Makefile`) to push the Heptio Ark images to your own registry. This allows any node in your cluster to pull your locally built image.

In the Ark root directory, to build your container with the tag `$REGISTRY/ark:$VERSION`, run:

```
make container
```

To push your image to a registry, use `make push`.

### Update generated files

The following files are automatically generated from the source code:

* The clientset
* Listers
* Shared informers
* Documentation
* Protobuf/gRPC types

Run `make update` to regenerate files if you make the following changes:

* Add/edit/remove command line flags and/or their help text
* Add/edit/remove commands or subcommands
* Add new API types

Run [generate-proto.sh][13] to regenerate files if you make the following changes:

* Add/edit/remove protobuf message or service definitions. These changes require the [proto compiler][14].

### Cross compiling

By default, `make build` builds an `ark` binary for `linux-amd64`.
To build for another platform, run `make build-<GOOS>-<GOARCH>`.
For example, to build for the Mac, run `make build-darwin-amd64`.
All binaries are placed in `_output/bin/<GOOS>/<GOARCH>`-- for example, `_output/bin/darwin/amd64/ark`.

Ark's `Makefile` has a convenience target, `all-build`, that builds the following platforms:

* linux-amd64
* linux-arm
* linux-arm64
* darwin-amd64
* windows-amd64

## 3. Test

To run unit tests, use `make test`. You can also run `make verify` to ensure that all generated
files (clientset, listers, shared informers, docs) are up to date.

## 5. Vendoring dependencies

If you need to add or update the vendored dependencies, see [Vendoring dependencies][11].

[0]: ../README.md
[1]: #prerequisites
[2]: #download
[3]: #build
[4]: https://blog.golang.org/organizing-go-code
[5]: https://golang.org/doc/install
[6]: https://github.com/heptio/ark/tree/master/examples
[7]: #run
[8]: config-definition.md
[10]: #vendoring-dependencies
[11]: vendoring-dependencies.md
[12]: #test
[13]: https://github.com/heptio/ark/blob/master/hack/generate-proto.sh
[14]: https://grpc.io/docs/quickstart/go.html#install-protocol-buffers-v3
[15]: https://docs.aws.amazon.com/cli/latest/topic/config-vars.html#the-shared-credentials-file
[16]: https://cloud.google.com/docs/authentication/getting-started#setting_the_environment_variable
[17]: https://aws.amazon.com/quickstart/architecture/heptio-kubernetes/
[18]: https://eksctl.io/
[19]: ../examples/README.md
[20]: api-types/backupstoragelocation.md
[21]: api-types/volumesnapshotlocation.md
17 changes: 17 additions & 0 deletions docs/developing/dev-intro.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
# Developing with Ark

Ark is an [open source project][1], so you can extend or develop it for yourself. We also welcome contributions to the code base! See [our contributing guidelines][2] for the formal requirements and our communication channels.

This guide provides more details about how to get started extending Ark or contributing directly to the original project.

- [Before you start developing][3]
- [Build][4]
- [Run][5]
- [Test][6]

[1]: https://github.com/heptio/ark/LICENSE
[2]: https://github.com/heptio/ark/CONTRIBUTING.md
[3]: dev-prereq.md
[4]: build.md
[5]: dev-run.md
[6]: dev-test.md
34 changes: 34 additions & 0 deletions docs/developing/dev-prereq.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,34 @@


## Prerequisites

* Access to a Kubernetes cluster, version 1.7 or later. Version 1.7.5 or later is required to run `ark backup delete`.
* A DNS server on the cluster
* kubectl installed
* [Go][5] installed (minimum version 1.8)

### Prerequisites

When running Heptio Ark, you will need to account for the following (all of which are handled in the [`/examples`][6] manifests):

* Appropriate RBAC permissions in the cluster
* Read access for all data from the source cluster and namespaces
* Write access to the target cluster and namespaces
* Cloud provider credentials
* Read/write access to volumes
* Read/write access to object storage for backup data
* A [BackupStorageLocation][20] object definition for the Ark server
* (Optional) A [VolumeSnapshotLocation][21] object definition for the Ark server, to take PV snapshots

## Getting the source

```bash
mkdir $HOME/go
export GOPATH=$HOME/go
go get github.com/heptio/ark
```

Where `go` is your [import path][4] for Go.

For Go development, it is recommended to add the Go import path (`$HOME/go` in this example) to your path.

Empty file added docs/developing/dev-run.md
Empty file.
Loading

0 comments on commit 6e4faca

Please sign in to comment.