Skip to content

Commit fa6d232

Browse files
committed
Merge branch 'feature/prepare-1.4'
2 parents 1f847a4 + e19aea7 commit fa6d232

File tree

1 file changed

+35
-3
lines changed

1 file changed

+35
-3
lines changed

deployment/minikube.md

Lines changed: 35 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -41,15 +41,24 @@ Minikube requires a driver for virtualization. The most common is Docker Engine.
4141
# Install TrustGraph CLI tools
4242
python3 -m venv env
4343
source env/bin/activate
44-
pip install trustgraph-cli
44+
pip install trustgraph-cli==x.y.z
4545
```
4646

47+
where `x.y.z` is the TrustGraph version.
48+
4749
### 2. Start Minikube
4850

51+
Minikube needs to be started with enough resources. At the time of
52+
writing, tracking TrustGraph 1.4, this is roughly 9 CPUs and 11GB of memory.
53+
4954
```bash
50-
minikube start --cpus=4 --memory=8192
55+
minikube start --cpus=9 --memory=11264
5156
```
5257

58+
Different deployment environments cause different pressures on memory, and so
59+
you may get different resource requirements depending on the options you
60+
deploy.
61+
5362
### 3. Verify Minikube
5463

5564
```bash
@@ -75,6 +84,29 @@ Obtain your TrustGraph Kubernetes configuration file from the [TrustGraph Config
7584
kubectl apply -f <configuration-file.yaml>
7685
```
7786

87+
You also need to deploy some secrets:
88+
89+
```
90+
kubectl -n trustgraph create secret generic gateway-secret \
91+
--from-literal=gateway-secret=
92+
93+
kubectl -n trustgraph create secret generic mcp-server-secret \
94+
--from-literal="mcp-server-secret="
95+
```
96+
97+
If you are deployment an Ollama integration, the Ollama URL needs to be
98+
presented to the system in a secret:
99+
100+
```
101+
kubectl -n trustgraph create secret generic ollama-credentials \
102+
--from-literal="ollama-host=http://MY.OLLAMA.HOST:11434"
103+
```
104+
105+
Replace `MY.OLLAMA.HOST` with the actual hostname.
106+
107+
When Minikube services want to access services on the host, the hostname
108+
`host.minikube.internal` can be used.
109+
78110
### 2. Launch LoadBalancer
79111

80112
**In a separate terminal window:**
@@ -277,4 +309,4 @@ minikube status
277309
- **Cloud Deployment**: Explore [AWS](aws), [GCP](gcp) managed Kubernetes
278310
- **Monitoring**: Set up comprehensive monitoring with Prometheus/Grafana
279311
- **Security**: Review [Security Considerations](security-considerations)
280-
- **Performance**: Optimize for larger workloads
312+
- **Performance**: Optimize for larger workloads

0 commit comments

Comments
 (0)