dnoulet/go-guess
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

fix: use local Rancher kubeconfig

Browse source 
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This commit is contained in:
Daniel Noulet 2026-09-20 15:18:00 +02:00
parent 76db5bf7a1
commit 88e911d05f
2 changed files with 26 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

19
Makefile
View file

@ -8,6 +8,7 @@ HELM ?= helm
HELM_CHART := deploy/helm/go-guess HELM_CHART := deploy/helm/go-guess
HELM_RELEASE ?= go-guess HELM_RELEASE ?= go-guess
HELM_NAMESPACE ?= go-guess HELM_NAMESPACE ?= go-guess
KUBECONFIG ?= $(HOME)/.config/kubectl/rancher.urpi.local.yaml
.PHONY: help dev db-up db-down migrate migrate-down seed backend frontend frontend-install test test-backend test-frontend test-integration test-bdd test-bdd-down test-env test-env-down lint build helm-lint helm-deploy-development helm-deploy-production .PHONY: help dev db-up db-down migrate migrate-down seed backend frontend frontend-install test test-backend test-frontend test-integration test-bdd test-bdd-down test-env test-env-down lint build helm-lint helm-deploy-development helm-deploy-production
@ -98,19 +99,21 @@ build:
cd frontend && npm run build cd frontend && npm run build
helm-lint: helm-lint:
$(HELM) lint $(HELM_CHART) -f $(HELM_CHART)/values-development.yaml KUBECONFIG="$(KUBECONFIG)" $(HELM) lint $(HELM_CHART) -f $(HELM_CHART)/values-development.yaml
$(HELM) lint $(HELM_CHART) -f $(HELM_CHART)/values-production.yaml KUBECONFIG="$(KUBECONFIG)" $(HELM) lint $(HELM_CHART) -f $(HELM_CHART)/values-production.yaml
$(HELM) template $(HELM_RELEASE) $(HELM_CHART) \ KUBECONFIG="$(KUBECONFIG)" $(HELM) template $(HELM_RELEASE) $(HELM_CHART) \
-f $(HELM_CHART)/values-development.yaml >/dev/null -f $(HELM_CHART)/values-development.yaml >/dev/null
$(HELM) template $(HELM_RELEASE) $(HELM_CHART) \ KUBECONFIG="$(KUBECONFIG)" $(HELM) template $(HELM_RELEASE) $(HELM_CHART) \
-f $(HELM_CHART)/values-production.yaml >/dev/null -f $(HELM_CHART)/values-production.yaml >/dev/null
helm-deploy-development: helm-deploy-development:
$(HELM) upgrade --install $(HELM_RELEASE) $(HELM_CHART) \ KUBECONFIG="$(KUBECONFIG)" $(HELM) upgrade --install $(HELM_RELEASE) $(HELM_CHART) \
--namespace $(HELM_NAMESPACE)-development --create-namespace \ --namespace $(HELM_NAMESPACE)-development --create-namespace \
-f $(HELM_CHART)/values-development.yaml -f $(HELM_CHART)/values-development.yaml \
--rollback-on-failure --wait --timeout 10m
helm-deploy-production: helm-deploy-production:
$(HELM) upgrade --install $(HELM_RELEASE) $(HELM_CHART) \ KUBECONFIG="$(KUBECONFIG)" $(HELM) upgrade --install $(HELM_RELEASE) $(HELM_CHART) \
--namespace $(HELM_NAMESPACE)-production --create-namespace \ --namespace $(HELM_NAMESPACE)-production --create-namespace \
-f $(HELM_CHART)/values-production.yaml -f $(HELM_CHART)/values-production.yaml \
--rollback-on-failure --wait --timeout 10m

19
rancher-install.txt
View file

@ -18,6 +18,8 @@ Kubernetes cluster instead of copying this single-container topology.
- Registry configuration: `~/.config/kubectl/registries.yaml` - Registry configuration: `~/.config/kubectl/registries.yaml`
- Local HTTP: `http://127.0.0.1:8000` - Local HTTP: `http://127.0.0.1:8000`
- Local HTTPS: `https://127.0.0.1:8443` - Local HTTPS: `https://127.0.0.1:8443`
- Development application NodePort: `http://127.0.0.1:30080`
- Production application NodePort: `http://127.0.0.1:31374`
Pinning the digest makes another installation reproducible. Review and update Pinning the digest makes another installation reproducible. Review and update
the Rancher version deliberately rather than running an unpinned `latest` image the Rancher version deliberately rather than running an unpinned `latest` image
@ -68,6 +70,8 @@ docker run -d \
--restart=unless-stopped \ --restart=unless-stopped \
-p 127.0.0.1:8000:80 \ -p 127.0.0.1:8000:80 \
-p 127.0.0.1:8443:443 \ -p 127.0.0.1:8443:443 \
-p 127.0.0.1:30080:30080 \
-p 127.0.0.1:31374:31374 \
-v /opt/rancher:/var/lib/rancher \ -v /opt/rancher:/var/lib/rancher \
-v "$HOME/.config/kubectl/registries.yaml:/etc/rancher/k3s/registries.yaml:ro" \ -v "$HOME/.config/kubectl/registries.yaml:/etc/rancher/k3s/registries.yaml:ro" \
--privileged \ --privileged \
@ -75,9 +79,10 @@ docker run -d \
rancher/rancher@sha256:5f6c4dc52a05e0c400b53c08bf778ca55790f277e443b5881269158499b7ebe5 rancher/rancher@sha256:5f6c4dc52a05e0c400b53c08bf778ca55790f277e443b5881269158499b7ebe5
``` ```
The explicit `127.0.0.1` bindings prevent ports `8000` and `8443` from being The explicit `127.0.0.1` bindings prevent Rancher and application NodePorts
published directly to the internet. Nginx on the same server can still reach from being published directly to the internet. Nginx on the same server can
them. still reach them. Docker cannot add port mappings to an existing container, so
new NodePorts must be included when recreating the Rancher container.
## 4. Verify the installation ## 4. Verify the installation
@ -95,10 +100,16 @@ docker exec rancher kubectl get nodes -o wide
Expected results: Expected results:
- The container is running with restart policy `unless-stopped`. - The container is running with restart policy `unless-stopped`.
- Only `127.0.0.1:8000` and `127.0.0.1:8443` are published. - Only loopback ports `8000`, `8443`, `30080`, and `31374` are published.
- `https://127.0.0.1:8443/ping` returns `pong`. - `https://127.0.0.1:8443/ping` returns `pong`.
- The embedded `local-node` reports `Ready`. - The embedded `local-node` reports `Ready`.
After deploying Go Guess, verify the application NodePort:
```bash
curl --fail http://127.0.0.1:30080/api/health
```
Retrieve the one-time bootstrap password locally, open Retrieve the one-time bootstrap password locally, open
`https://127.0.0.1:8443`, and immediately choose a permanent administrator `https://127.0.0.1:8443`, and immediately choose a permanent administrator
password: password: