Skip to content
1 change: 1 addition & 0 deletions skaffold.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -219,6 +219,7 @@ profiles:
mixer.hostProject: "datcom-website-autopush"
mixer.serviceName: "website-esp.endpoints.datcom-website-autopush.cloud.goog"
serviceGroups.recon.enableEmbeddingsSidecar: "false"
serviceGroups.default.enableEmbeddingsSidecar: "true"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

https://github.com/datacommonsorg/mixer/blob/303a7931ac3e5f9436571fbd0c4b6432182b1de4/deploy/helm_charts/mixer/values.yaml#L441

In mixer, we set enableEmbeddingsSidecar to true for recon, which is why the line above sets it to false for website's recon.

Is it intentional to put this in defualt? Why have it in different mixer service groups across website and mixer?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For website, the recon workload isn't used:

serviceGroups:
recon: null

resolve traffic is routed to the default workload. Which is why for website-autopush we want the embeddings server in default and not recon

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Xiao, separate note is that this provides an added risk at deployment. So just make sure to monitor when this gets released to autopush, staging and prod and just double check this looks healthy.
Might want a note to secondary oncaller when he does the release.

- name: mixer-autopush
customActions:
- name: deploy-cloud-esp-mixer-autopush
Expand Down
Loading