UNCLASSIFIED - NO CUI

Skip to content
Snippets Groups Projects
Commit 2c596630 authored by Branden Cobb's avatar Branden Cobb
Browse files

Merge branch '925-links' into 'master'

Docs - 925 - Fix broken links and references in Bigbang documentation

Closes #925

See merge request platform-one/big-bang/bigbang!1087
parents 92f60f43 f319a06e
No related branches found
No related tags found
2 merge requests!1386Master,!1087Docs - 925 - Fix broken links and references in Bigbang documentation
Pipeline #562225 passed with warnings
......@@ -79,14 +79,14 @@ The diagram below shows a typical deployment of Big Bang into a Kubernetes clust
### Configuration
1. The user must [setup an encryption key pair](./3_encryption.md) for SOPS and store the private key securely (e.g. KMS). This should **NOT** be stored in Git.
1. The user should then [configure Big Bang](./4_configuration.md) values and secrets for the targeted Kubernetes cluster.
1. The user must [setup an encryption key pair](./encryption.md) for SOPS and store the private key securely (e.g. KMS). This should **NOT** be stored in Git.
1. The user should then [configure Big Bang](./configuration.md) values and secrets for the targeted Kubernetes cluster.
1. All secrets should be encrypted with SOPS to protect them.
1. Once all of the configuration has been completed, it must be pushed to a Git repository.
### Deployment
1. With everything in Git, the user can [deploy BigBang](./5_deployment.md) using a Kubernetes manifest.
1. With everything in Git, the user can [deploy BigBang](./deployment.md) using a Kubernetes manifest.
1. The manifest holds two Flux resources, one pointing to the Git repository holding the custom environment, and one telling Flux to run Kustomize on a targeted folder within the repo.
1. The repository is reconciled first, pulling the files from Git.
1. Next, Kustomize is run on the environment configuration
......
......@@ -9,7 +9,7 @@
- [Kustomization](#kustomization)
- [Packages](#packages)
Big Bang can take a long time to run. After making changes, it could take 10-15 minutes to take effect. Use the [sync.sh](../hack/sync.sh) script to speed this up.
Big Bang can take a long time to run. After making changes, it could take 10-15 minutes to take effect. Use the [sync.sh](../scripts/sync.sh) script to speed this up.
Big Bang is configured to retry failed package installations and upgrades. Before concluding you have a failure, make sure you allow Big Bang to attempt to resolve dependencies and retry.
......@@ -34,7 +34,7 @@ kubectl get events -n flux-system
| Symptom | Cause | Resolution |
|--|--|--|
| Install script timed and pods are still pulling the image | Slow connection to docker registry | Adjust `--timeout` value in `flux install` to wait longer |
| Pod status is `ImagePullBackOff` or `ErrImagePull` | Bad registry, version, or credentials | Fix the `--registry`, `--version`, or `--image-pull secret` options or use the `hack/flux-install.sh` script for pulling from Iron Bank |
| Pod status is `ImagePullBackOff` or `ErrImagePull` | Bad registry, version, or credentials | Fix the `--registry`, `--version`, or `--image-pull secret` options or use the `./scripts/install_flux.sh` script for pulling from Iron Bank |
## Git Repository
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment