Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update enable-data-copilot.md #429

Merged
merged 3 commits into from
Nov 26, 2024
Merged

Update enable-data-copilot.md #429

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
aa9ecbc
Update enable-data-copilot.md
alexanderahn Nov 11, 2024
d81a45c
Update enable-data-copilot.md
alexanderahn Nov 11, 2024
38cb8ac
Merge branch 'main' into enable-data-copilot-edits
alexanderahn Nov 26, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 1 addition & 8 deletions docs/concepts/copilot/enable-data-copilot.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,14 +31,7 @@ From the Kubernetes cluster where Prophecy services are running:
2. Check that the `athena` Prophecy service is running version `3.3.8.0` or greater. This is only required if using the Pipeline approach to the upgrade.
3. In the `ProphecyCluster` CR, do the following:

- add `copilot` to `enabledapps`
- add `image` section as below, providing the version
- add the `copilot` section as below in the same level as other enabled apps

```
copilot:
image: gcr.io/prophecy-share/copilot:<release-version>
```
- Add `copilot` to `enabledapps`.

4. Once deployed, wait for the `copilot-cm` to be created. Then edit the default values in the configmap to match the ENVs required.
5. Supply the API keys for the appropriate endpoint and ENV as below. Prophecy Copilot requires two types of models:
Expand Down
Loading