go-http-client | wrap golang http client

I figured out part of the answer, by simply skipping all GET requests:

No, this us undoable with net/http because net/http implements HTTP and what you want to do simply isn't HTTP.

If it's not possible using net/http is there any other way that this would be doable?

Do raw networking, i.e. use package net.

This is wrong. Sorry.

You could use a recursive function. Search through the json for the dictionary whose "key" value matches lookup key (in this example, "request.headers[x-api-key]") and yield the value of the "values" key of that dictionary:

Posting the answer in case this helps someone

Had to add a few things to get this to work.

The filter section needed modification as follows

Kubernetes 1.22 is supported only with NGINX Ingress Controller 1.0.0 and higher = https://github.com/kubernetes/ingress-nginx#support-versions-table

You need tu upgrade your nginx-ingress-controller Bitnami Helm Chart to Version 9.0.0 in Chart.yaml. Then run a helm upgrade nginx-ingress-controller bitnami/nginx-ingress-controller.

You should also regularly update specially your ingress controller, as the version v0.34.1 is very very old bcs the ingress is normally the only entry appoint from outside to your cluster.

pvc thats gets created as a part of statefulset will have a name which is an amalgamation of 3 components joined by - :

1. Name defined in the volumeClaimTemplates section data
2. Name of the statefulset in the metadata section which is reddwarf-postgresql-postgresql
3. Its replica number , if it is first replica then it would be 0

So finally the name of the pvc that gets created when you create this statefulset is data-reddwarf-postgresql-postgresql-0.which is the pvc name that you also seeing in your setup.

please note when you delete the statefulset , pvc does not deleted automatically we need to pvc separately. When you recreate/scaleup the stateful set and if the pvc which matches above naming convention& spec does not exists then it will create a pvc.

From kubernetes documentation

As the documentation states:

The arguments req and via are the upcoming request and the requests made already, oldest first.

So at the first redirect, len(via) will be 1. If you return error if len(via)>1, it should fail for additional requests.

You are setting set_real_ip_from to 127.0.0.1, so as docs says in here , it makes client address 127.0.0.1

Just omit this line for getting real client address

Based on logs and details from certificate you provided it's safe to say it's working as expected.

Pay attention to revision: 5 in your certificate, which means that certificate has been renewed 4 times already. If you try to look there now, this will be 6 or 7 because certificate is updated every 12 hours.

First thing which can be really confusing is error messages in cert-manager pod. This is mostly noisy messages which are not really helpful by itself.

See about it here Github issue comment and here github issue 3667.

In case logs are really needed, verbosity level should be increased by setting args to --v=5 in the cert-manager deployment. To edit a deployment run following command: