Shows an approach to work with a microservices based architecture using .Net Core, Docker, and Azure Service Fabric/Kubernetes, applying Domain Driven Design (DDD) and Comand and Query Responsibility Segregation (CQRS) and other patterns.
We are looking to find ways to help developers find security misconfigurations, i.e., violation of security best practices in Kubernetes manifests. We have noticed an instance of no security context in one of your Kubernetes manifests. The recommended practice is use of security context for pods. Without defining a security context for the pod, a container may run with root privilege and write permission into the root file system, making the Kubernetes cluster vulnerable. For examples of Kubernetes security anti-patterns we are following our peer-reviewed publication on Kubernetes security best practices (https://arxiv.org/pdf/2006.15275.pdf).
Please use securityContext to fix this misconfiguration. We would like to hear if you agree to fix this misconfiguration or have fixed the misconfiguration.
Hi, I'm learning micro services using service fabric. I read different tutorial and they inherit from StatefulService or StatelessService service in service fabric but you don't have any inheritance from StatefulService or StatelessService. why you don't have inheritance from service fabric?
Hi , Thanks so much for this article - really learned allot. I have tried deploying a couple of time but my invoice service just does not want to work in Azure. And the error message does not provide much details...any suggestions? See below screenshot