Current state, some tools still not working correctly
This commit is contained in:
parent
5eea56eb34
commit
d368896a91
|
|
@ -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.
Loading…
Reference in New Issue