selfsigned | Generate self-signed certificates from node.js | Runtime Evironment library

I've updated angular cli and created a new project, with routing and scss.

When I run npm install i see:

I am following the devops guy tutorial for setting up CERT manager.

Steps:

Create new kind cluster

I have the following Dockerfile:

I am working on a microservice app and I use nginx ingress. I setup rules with 3 services, when I mention host in the rules like this bellow it always gives me 404 for all the services

I'm trying to add a self-signed certificate in my AKS cluster using Cert-Manager.

I created a ClusterIssuer for the CA certificate (to sign the certificate) and a second ClusterIssuer for the Certificate (self-signed) I want to use.

I am not sure if the certificate2 is being used correctly by Ingress as it looks like it is waiting for some event.

Am I following the correct way to do this?

This is the first ClusterIssuer "clusterissuer.yml":

Trying to use library 'pem' to generate a certificate with v3_req extension but I'm always getting an error. API documentation says that If I specify config then the v3_req section will be used. But right now, it can't be load and display this error :

I'm using a private key to sign a JWT token, which works as expected. However, I'd like to leverage Azure Key Vault to do the signing for me, so that the private key doesn't leave KeyVault. I'm struggling to get this to work, but not sure why.

Here's the code that doesn't use KeyVault and does work...

I'm trying to deploy bazel-remote, but when I try to:

I have a Problem with my grpc connections and nginx.

So, i've got these things : a client, a server, nginx. They all run on the same machine.

The client does some network scanning and is supposed to send it's results to the server,

The server is supposed to take the scanning-results and put them into a database. The server is based on ASP.Net - See appsettings.json The client and server use "grpc-dotnet" with "protobuf". Both also use the SSL certificate and generally they both work as expected.

The nginx proxy is supposed to be used as a Reverse-Proxy -> Clients only need to know one Endpoint for all their Requests. Nginx is only configured to pass grpc requests, nothing else.

First of all, almost all grpc requests do work. But they stop working, if the request gets too big. I dont know the exact size, but it must be under 180kb.

(180kb is the size of the scan results.In a test, sending half of these results succeded, where sending all did not. Custom test data (with the same class of course) did show the same results. If they got too big, it stopped working)

Without nginx, there are no errors while sending data from client to server. With nginx however, the client does recieve a HTTP 504 error.

Content of error.log (nginx)

2021/07/27 13:27:28 [error] 21464#7952: *66 upstream timed out (10060: Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat) while sending request to upstream, client: 127.0.0.1, server: , request: "POST /UI.Remoting.Discovery.Contract.DiscoveryService/SaveDiscoveryResult HTTP/2.0", upstream: "grpcs://127.0.0.1:30053", host: "localhost:30051"

"Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat" translates to :

A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond

nginx.conf - i did try many configurations - they do not solve my problems. The configurations shown below are just to show you, which ones i've tested, but there might be missing some. I've tested them in multiple different arrangements and selectively tested out each configuration in different areas (server, http, location)