helloapp | ASP.NET MVC Project - HelloApp is an ASP | Model View Controller library

Eventually, I could resolve the issue. The issue was trivial yet bothering. In the Dockerfile, there was a missing script, i.e., npm run build. So, here is the final Dockerfile I used it for building the dist directory along with other requirements:

You probably want an intermediate object something like MessageView

The getItemViewType() is the right place for determining the item layout. So you need to move the logic there, so override it in the adapter:

You can't have the same "path: /" for the same host. Change the path to a different one for your the new service.

In your routes, add:

First of all, a proof it can actually work, somehow, with your code.
Here I read JPG images located in the resources folder, but it actually doesn't really matter.

Your code is a bit messy too. Where are you attaching the btnStart JButton to the outer panel? You need to understand how to layout components too.

You have a main JFrame, and a root JPanel which needs a layout. In this case we can opt for a BorderLayout.

In my opinion, if you has enabled the https on the apache and just use http redirect between the apache and the kestrel server, you could use http. Like this:

Brower --->https ---> Apache --> http ---> kestrel.

This will not causing the security issue. HTTPS helps prevent intruders from tampering with the communications between your websites and your users' browsers. Since if someone hack your server to capture the http request, he could also get your server's all information.

As mentioned in comments

If you have exposed your service as ClusterIP it's visible only internally in the cluster, if you wan't to expose your service externally you have to use either nodePort or LoadBalancer.

Publishing Services (ServiceTypes)

For some parts of your application (for example, frontends) you may want to expose a Service onto an external IP address, that's outside of your cluster. Kubernetes ServiceTypes allow you to specify what kind of Service you want. The default is ClusterIP.

Type values and their behaviors are:

ClusterIP: Exposes the Service on a cluster-internal IP. Choosing this value makes the Service only reachable from within the cluster. This is the default ServiceType.

NodePort: Exposes the Service on each Node's IP at a static port (the NodePort). A ClusterIP Service, to which the NodePort Service routes, is automatically created. You'll be able to contact the NodePort Service, from outside the cluster, by requesting :.

LoadBalancer: Exposes the Service externally using a cloud provider's load balancer. NodePort and ClusterIP Services, to which the external load balancer routes, are automatically created.

ExternalName: Maps the Service to the contents of the externalName field (e.g. foo.bar.example.com), by returning a CNAME record with its value. No proxying of any kind is set up.

Related documentation about that.

With minikube you can achieve that with minikube service command.

There is documentation about minikube service and there is an example.

As mentioned here by @murgatroid99

The gRPC library does not recognize the https:// scheme for addresses, so that target name will cause it to try to resolve the wrong name. You should instead use grpc-server-xxx.com:9090 or dns:grpc-server-xxx.com:9090 or dns:///grpc-server-xxx.com:9090. More detailed information about how gRPC interprets channel target names can be found in this documentation page.

As it does not recognize https I assume it's the same for http, so it's not possible.

Additionally as @IsolatedSushi mentioned

It also works when I portforward with the command kubectl -n hellospace port-forward svc/helloservice 8080:50051

As mentioned here

Kubectl port-forward allows you to access and interact with internal Kubernetes cluster processes from your localhost. You can use this method to investigate issues and adjust your services locally without the need to expose them beforehand.

There is an example in documentation.

Okay, it can sound ridiculous, but all what i need was updating of NuGet package Microsoft.Data.SqlClient