Thanks for your feedback!
The ABP is a development framework as you know. Since we have limited resources to focus on, seamless development experience is our top priority.
We are trying to help with the deployment aswell even if costs lots of time to learn different devops techs and stacks. Although, you can see that ABP has lots of varient for application development such as tiered, non-tiered; using mongodb, postgres, microservices etc. It is not possible to cover all the deployment scenarios.
Even though, we are trying to cover most common deployment scenarios and also the community shares their experiences on specific deployment scenarios in community posts.
For microservice azure specific deployment, we already have an eShopOnAbp sample which is deployed to Azure already; even to artifact.io.
You can also examine the scripts and the values for helm templates at https://github.com/abpframework/eShopOnAbp/tree/main/etc/k8s.
Moreover we are working on documentation for different deployment scenarios one by one but I can not give time for a relase date yet unfortunatelly.
Thank you!
The problem is about reaching the redis in the kubernetes network for sure.
Your configuration for authserver overrides the redis connection to http://redis. Since redis is running on TCP. As far as I have checked in our deployment scenarios, we configured it as the service name itself without the http protocol.
Other than that, this is not really related to ABP. You can ask it to StackOverflow with kubernetes tags that can be more helpful since I have limited knowledge on kubernetes.
Can you try using
- name: Redis__Configuration
value: redis (without http)
Do you have redis deployment file? You may not be exposing redis at all.
Yes, if you can check the module ConfigureServices method that has CORS configuration, you are basically missing it.
You may also forget to override it on production environment aswell.
I don't think sticky session is a nice solution for this since the tiered mvc application is using jwt tokens.
You can use ASP.NET Data Protection to store this information in a distributed cache for persistancy.
Simply add:
context.Services
.AddDataProtection()
.SetApplicationName("myApp")
.PersistKeysToStackExchangeRedis(redis, "myApp-Protection-Keys");
Library is from Microsoft.AspNetCore.DataProtection.StackExchangeRedis.
Did you try removing .AllowCredentials(); and tested again?
Do you still get the same error? Did you check the appsettings.json file is overridden correctly on deployment?
It is using Helm charts for deployment. Maybe you missed https://github.com/abpframework/eShopOnAbp/blob/main/etc/k8s/eshoponabp/charts/gateway-web/templates/gateway-web-configmap.yaml
The submit button located in the form is basically a view component called ViewFormViewComponent.
Currently, the redirection happens hard-codedly in the component's javascript which is written in Vue.js:
async submitAnswers(submittedForm) {
...
try {
const result = await this.formResponseService.saveAnswers(this.formId, postData);
location.href = `${window.origin}/Forms/${result.id}/FormResponse`;
}
...
},
You can override this component or modify it however I am not sure if it will be a good fit for a wizard/step type of process.
Trusting the self-sign certificate needs to be done in the server it is running at and unfortunatelly It is not something that i can do.
You can try OpenSSL to generate and trust the certificate as documented in https://learn.microsoft.com/en-us/dotnet/core/additional-tools/self-signed-certificates-guide#with-openssl