fix repo URL and branch refs
This commit is contained in:
18
BOOTSTRAP.md
18
BOOTSTRAP.md
@@ -4,7 +4,7 @@
|
||||
|
||||
- [ ] `kubeconfig` file placed at `~/infra/yandex-prod/kubeconfig`
|
||||
- [ ] `kubectl` context pointing to the new `yc-prod` cluster
|
||||
- [ ] Domain `prod.t01tt.tech` DNS managed (can be updated later in Phase 5)
|
||||
- [ ] Domaster `prod.t01tt.tech` DNS managed (can be updated later in Phase 5)
|
||||
- [ ] `git` and `helm` installed locally
|
||||
|
||||
---
|
||||
@@ -48,11 +48,11 @@ kubectl port-forward svc/gitea 3000:3000 -n gitea
|
||||
2. Fill out the install form:
|
||||
- Database: **SQLite3** (default)
|
||||
- Site Title: **Gitea**
|
||||
- Domain: **git.prod.t01tt.tech**
|
||||
- Domaster: **git.prod.t01tt.tech**
|
||||
- Application URL: **https://git.prod.t01tt.tech**
|
||||
- Create admin account (username/password/email — save these)
|
||||
3. Click "Install Gitea"
|
||||
4. Create a new repository: **`yandex-prod`** (must be **public**, owned by admin)
|
||||
4. Create a new repository: **`master`** (must be **public**, owned by admin)
|
||||
5. Close the port-forward (Ctrl+C)
|
||||
|
||||
---
|
||||
@@ -63,13 +63,13 @@ kubectl port-forward svc/gitea 3000:3000 -n gitea
|
||||
cd ~/infra/yandex-prod
|
||||
|
||||
git init
|
||||
git remote add origin http://localhost:3000/<admin-user>/yandex-prod.git
|
||||
git remote add origin http://localhost:3000/admin/master.git
|
||||
# Or, once Gitea ingress works later, use:
|
||||
# git remote add origin https://git.prod.t01tt.tech/<admin-user>/yandex-prod.git
|
||||
# git remote add origin https://git.prod.t01tt.tech/admin/master.git
|
||||
|
||||
git add -A
|
||||
git commit -m "initial bootstrap: infrastructure manifests"
|
||||
git push -u origin main
|
||||
git push -u origin master
|
||||
# Enter Gitea admin credentials when prompted
|
||||
```
|
||||
|
||||
@@ -93,7 +93,7 @@ sleep 2
|
||||
ARGOCD_PASS=$(kubectl -n argocd get secret argocd-initial-admin-secret -o jsonpath="{.data.password}" | base64 -d)
|
||||
argocd login localhost:8080 --username admin --password "${ARGOCD_PASS}" --insecure
|
||||
|
||||
argocd repo add http://gitea.gitea.svc.cluster.local:3000/<admin-user>/yandex-prod.git \
|
||||
argocd repo add http://gitea.gitea.svc.cluster.local:3000/admin/master.git \
|
||||
--name yandex-prod \
|
||||
--type git
|
||||
```
|
||||
@@ -242,7 +242,7 @@ argocd repo list
|
||||
|
||||
If not connected, re-add via ArgoCD CLI:
|
||||
```bash
|
||||
argocd repo add http://gitea.gitea.svc.cluster.local:3000/<admin-user>/yandex-prod.git \
|
||||
argocd repo add http://gitea.gitea.svc.cluster.local:3000/admin/master.git \
|
||||
--name yandex-prod \
|
||||
--type git
|
||||
```
|
||||
@@ -296,7 +296,7 @@ kubectl logs -n cnpg-system deploy/cnpg-controller-manager
|
||||
Common issue: pods can't schedule due to `podAntiAffinityType: required`. Ensure all 3 nodes exist and PVCs can bind.
|
||||
|
||||
### Gitea UI shows wrong URL after first login
|
||||
Gitea caches the ROOT_URL from the `deployment.yaml` env vars. If you change the domain, update:
|
||||
Gitea caches the ROOT_URL from the `deployment.yaml` env vars. If you change the domaster, update:
|
||||
```bash
|
||||
kubectl set env deploy/gitea -n gitea \
|
||||
GITEA__server__DOMAIN=git.prod.t01tt.tech \
|
||||
|
||||
Reference in New Issue
Block a user