Compatibility with Kubernetes or/and OpenShift

[dimtitricognet]

Hello,

We are trying to deploy AzureNamingTool from the Dockerfile and modifying the permissions on the application directories using a non-root user to comply with security policies on Kubernetes. However, we are encountering the following errors. Has anyone managed to run the application on Kubernetes? If so, what modifications were made to the Dockerfile?

Additionally, one last question: the application generates resource names based on a naming convention to store a history in a JSON file on the filesystem. If we delete a resource in Azure, how can we release the name in the application so it can be reused ?

Thank you !

[captainhook]

The answer is that you can't without some custom implementation; there's no sync between the two.

[ciprianglg]

Dimitri C (@dimtitricognet) :
"If we delete a resource in Azure, how can we release the name in the application so it can be reused ?"

This will allow you to generate the same name as many times you want.

About k8s, at the moment i'm running as container in azure webapp. B1 plan should be enough for day to day operations.

[FrankTheodoloz]

Hi there ! I faced the same issue on Openshift, but changing the port to 8080 in the Dockerfile (ASPNETCORE_HTTP_PORTS) allows the app to start.
The app was still crashing after a while or when trying to log with admin.
Removing Resources Limits was the key.