-
ABP Framework version: v9.X
-
UI Type: Blazor WASM
-
Database System: EF Core SQL Server
-
Tiered (for MVC) or Auth Server Separated (for Angular): yes/no
-
Exception message and full stack trace:
-
Steps to reproduce the issue:
In the ABP 7 we successfully made deployments in public cloud (DigitalOcean) using the generated Helm charts. We modified the values.yaml file and configured the domain names, with TLS certificates using Certmanager and Lets Encrypt.
Now, the Helm charts looking totally different and seems to be used for local deployment?
Can you please give short instructions how to deploy on public cloud?
Thanks
1 Answer(s)
-
0
Hello, first of all, sorry for the late reply, we somehow missed this.
Along with the microservice template, it provides K8s configurations ready for deployment to a local or remote K8s cluster. By default, this configuration uses the Stagging .NET environment. However, you can override this and other values, as you have done before.
I have shared the documents that I think will make it easier for you to do this with you below:
-
https://abp.io/docs/latest/solution-templates/microservice/helm-charts-and-kubernetes
-
https://abp.io/docs/latest/studio/kubernetes#abp-studio-working-with-kubernetes
Basically, between the last version of ABP and version
7.*.*
the suffix “local” was added to the filenames because all environment variables are configured for local. You need to change them for production. In addition, the feature of building images with a different tag each time when building images has been added so that deployment can be done from scratch each time. -