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
The Fides chart has been predominantly tested using an ingress and the service type of NodePort. The chart should be modified to make adoption easier when using the service type of LoadBalancer.
When using a service type of LoadBalancer, there are a few challenges.
CORS origins expect https://.
The workaround for this is to add the actual origins, which might require http:// and may specify a port, to the additionalCORSOrigins field in the values.yaml.
For the publicHostname fields, unless you create CNAMES to the service URLs, you cannot specify the service URLs (because they don't exist yet)
The workaround for this is to either create a CNAME that points to your service URL or to deploy it without specifying the publicHostname fields and then redeploy it once the URLs exist.
The text was updated successfully, but these errors were encountered:
The Fides chart has been predominantly tested using an ingress and the service type of NodePort. The chart should be modified to make adoption easier when using the service type of LoadBalancer.
When using a service type of LoadBalancer, there are a few challenges.
https://
.http://
and may specify a port, to theadditionalCORSOrigins
field in thevalues.yaml
.publicHostname
fields and then redeploy it once the URLs exist.The text was updated successfully, but these errors were encountered: