You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: charts/metamcp/README.md
+36Lines changed: 36 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -112,6 +112,42 @@ users:
112
112
apiKeyName: cli
113
113
```
114
114
115
+
### Reconciliation modes (Flux/Helm upgrades)
116
+
117
+
By default the provisioning job runs after every Helm install and upgrade and will upsert Namespaces/Endpoints to match values. You can tune this behavior:
118
+
119
+
- `provision.runOnUpgrade`(bool, default `true`)
120
+
- `true`: run provisioning on every Helm upgrade (continuous upsert)
121
+
- `false`: run only on initial install (post-install). Upgrades do not re-run provisioning
- `true`: update existing Namespaces (description + membership) and Endpoints when names already exist
125
+
- `false`: create-only; existing objects are left untouched (good for “seed once, then manage via UI”)
126
+
127
+
Notes
128
+
- Servers are always create-only (by name). The job does not modify or delete existing servers.
129
+
- Deletions are not automatic. Removing items from values does not delete them in MetaMCP. If you need prune semantics, open an issue so we can add an opt‑in `prune` mode.
130
+
131
+
Examples
132
+
133
+
Continuous upsert (Git is the source of truth):
134
+
135
+
```yaml
136
+
provision:
137
+
enabled: true
138
+
runOnUpgrade: true
139
+
updateExisting: true
140
+
```
141
+
142
+
Seed once, keep UI changes later:
143
+
144
+
```yaml
145
+
provision:
146
+
enabled: true
147
+
runOnUpgrade: false
148
+
updateExisting: false
149
+
```
150
+
115
151
Provisioning authentication
116
152
117
153
- The provisioning Job authenticates using the first entry in `users` (email/password).
Copy file name to clipboardExpand all lines: charts/metamcp/README.md.gotmpl
+36Lines changed: 36 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -112,6 +112,42 @@ users:
112
112
apiKeyName: cli
113
113
```
114
114
115
+
### Reconciliation modes (Flux/Helm upgrades)
116
+
117
+
By default the provisioning job runs after every Helm install and upgrade and will upsert Namespaces/Endpoints to match values. You can tune this behavior:
118
+
119
+
- `provision.runOnUpgrade` (bool, default `true`)
120
+
- `true`: run provisioning on every Helm upgrade (continuous upsert)
121
+
- `false`: run only on initial install (post-install). Upgrades do not re-run provisioning
- `true`: update existing Namespaces (description + membership) and Endpoints when names already exist
125
+
- `false`: create-only; existing objects are left untouched (good for “seed once, then manage via UI”)
126
+
127
+
Notes
128
+
- Servers are always create-only (by name). The job does not modify or delete existing servers.
129
+
- Deletions are not automatic. Removing items from values does not delete them in MetaMCP. If you need prune semantics, open an issue so we can add an opt‑in `prune` mode.
130
+
131
+
Examples
132
+
133
+
Continuous upsert (Git is the source of truth):
134
+
135
+
```yaml
136
+
provision:
137
+
enabled: true
138
+
runOnUpgrade: true
139
+
updateExisting: true
140
+
```
141
+
142
+
Seed once, keep UI changes later:
143
+
144
+
```yaml
145
+
provision:
146
+
enabled: true
147
+
runOnUpgrade: false
148
+
updateExisting: false
149
+
```
150
+
115
151
Provisioning authentication
116
152
117
153
- The provisioning Job authenticates using the first entry in `users` (email/password).
0 commit comments