diff --git a/docs/concepts/copilot/enable-data-copilot.md b/docs/concepts/copilot/enable-data-copilot.md index ae26f114a1..51d43e96e6 100644 --- a/docs/concepts/copilot/enable-data-copilot.md +++ b/docs/concepts/copilot/enable-data-copilot.md @@ -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: - ``` + - 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: