We have lunched .Net microservice on container and published it on EKS Cluster. It's working fine on http.
We follow the link to deploy .Net microservice as deploy as a container. https://dotnet.microsoft.com/en-us/learn/aspnet/microservice-tutorial/docker-file
We used below deploy.yaml
**--- apiVersion: apps/v1 kind: Deployment metadata: name: mymicroservice spec: replicas: 1 template: metadata: labels: app: mymicroservice spec: containers: - name: mymicroservice image: [YOUR DOCKER ID]/mymicroservice:latest ports: - containerPort: 80 env: - name: ASPNETCORE_URLS value: http://*:80 selector: matchLabels: app: mymicroservice
apiVersion: v1 kind: Service metadata: name: mymicroservice spec: type: LoadBalancer ports:
- port: 80 selector: app: mymicroservice**
This exposed our microservices behind classic load balancer. It's working fine on Http. but we facing challenges on HTTPS. How can this be achieved? If we need to use Nginx Ingress Controller how that yaml we can tune according to our deployment.yaml
