Compare commits

...

3 Commits

Author SHA1 Message Date
Moritz Graf 065190afb7 Adding a few more tools 2026-02-15 16:15:27 +01:00
Moritz Graf d368896a91 Current state, some tools still not working correctly 2026-02-15 15:41:35 +01:00
Moritz Graf 5eea56eb34 Latest changes to config, but still having issues 2026-02-15 14:29:29 +01:00
2 changed files with 26 additions and 0 deletions

View File

@ -65,3 +65,29 @@ Modular tool capabilities.
### 💡 Special Requirements ### 💡 Special Requirements
- **`nano-banana-pro`**: Requires the `uv` tool. It is installed at `/home/node/.openclaw/bin/uv` (on the PVC) and included in the system `PATH`. - **`nano-banana-pro`**: Requires the `uv` tool. It is installed at `/home/node/.openclaw/bin/uv` (on the PVC) and included in the system `PATH`.
## 🚨 Startup & Troubleshooting
### Investigating Issues
You can execute commands directly inside the running pod to inspect the environment or file system:
```bash
# Get the pod name
kubectl get pods -n openclaw
# Execute a command (e.g., check config)
kubectl exec -it -n openclaw <pod-name> -c openclaw -- cat /home/node/.openclaw/openclaw.json
# Check environment variables
kubectl exec -it -n openclaw <pod-name> -c openclaw -- env | grep OPENCLAW
```
### Applying Configuration Changes
Any change to `openclaw.secret.yaml` (ConfigMap or Deployment) requires a rollout restart to take effect:
```bash
kubectl apply -f k8s/openclaw/openclaw.secret.yaml
kubectl rollout restart deployment openclaw -n openclaw
```
Always verify the rollout status:
```bash
kubectl rollout status deployment openclaw -n openclaw
```

Binary file not shown.