rest_api | sample REST API in Django and Python for employees | REST library

Probably MatchTransactions.onlyInFile1 is undefined, so when the ngFor directive tries to access MatchTransactions.onlyInFile1[0] you get that error.

if you get all the data at time you can use

The problem is not with KFImage, which is loading as expected, but with the fact that TabView is somehow unaware that the image has been loaded and that it needs to re-render it, but it can be solved easily:

Store your urls to display in an array and then use ForEach inside the TabView - this is enough to make the images appear once they are loaded:

This is not valid hreq.setRequestHeader "-v -u {MyEmail}:{MyPassword}"

Try basic authentication instead

docker stop will fail if it fails to stop the container.

You can solve the issue in one of the two following ways:

1. Check that there is a running container before attempting to stop it:

The error message was self-explanatory. After some search, I found the parameter that needed to be added to the data source URL

Kubernetes is often used for apps that is composed of multiple services, e.g. microservice architecture. In such architecture, the https-connection to the "app" is terminated at the gateway, typically Kubernetes Ingress load balancer, and then depending on what url the request has, it is forwarded to the appropriated Pod within the cluster.

The case you describe is only a single Pod / Deployment. For so small use cases, it is probably not worth using a full Kubernetes cluster. Kuberntes is typically used for larger environments when you have many nodes to handle your workload.

A benefit with using Kubernetes in a larger environment is that it is very good on separating infrastructure from the applications. See e.g. DevOps Before and After Kubernetes. As an example, the developers of your app can focus on implementing features and let the infrastructure handle the rest. In your case, this means that the developer does not need to handle the SSL-certificates like privkey.pem and fullchain.pem - this can instead be handled outside the app and changed independently.

Can I consider traffic is encrypted inside the cluster (like pod to pod) when using Kubernetes services IP/pods IPs though we are in HTTP?

Pod to Pod traffic is not encrypted unless you or your cluster has configuration for SSL / HTTPS. But Pod to Pod traffic is internal traffic within the Kubernetes cluster and it is typically within a private IP-subnet. That said, you can add a service mesh product like e.g. Istio to get strong encryption for Pod to Pod using mTLS, also including authentication with certificates - but this is still managed by the infrastructure outside the app-container.

If you want to set a secret you should use logging command as below

Based on the comments.

The issue was caused by existing record set in Route53. The solution was to delete the record in Route53 console and use CloudFormation to re-create it.