Compare commits
No commits in common. "065190afb77482deed0f5945d8a8889cfcd4c9a3" and "af661b1babca8df3631ff231e8941bff84cc4075" have entirely different histories.
065190afb7
...
af661b1bab
|
|
@ -65,29 +65,3 @@ Modular tool capabilities.
|
|||
|
||||
### 💡 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`.
|
||||
|
||||
## 🚨 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.
Loading…
Reference in New Issue