Hot answers tagged

2

You can't configure your Ingress to serve static data (from your host files for example) alone because the Ingress resource is just a way to configure a way of understanding for Kubernetes on how to access a specific internal resource from outside the cluster. An API object that manages external access to the services in a cluster, typically HTTP. Ingress ...


1

Same TLS secret will not be mapped to two ingress at the same time within a namespace.It will map to the first deployed ingress. Create the same secret with a different name and map it to the other ingress for it to work.


1

Your ServiceMonitor seems to be correct with the exception that you have defined no path under spec.endpoints. You also need to define the port named prometheus under the ingress-nginx service or deployment. ServiceMonitors can be debugged this way:- Check if the ServiceMonitor created is being read by the Prometheus:- Look at the /targets URL. (There ...


1

Set automountServiceAccountToken: true in your pod specification in both of the jobs and the deployment. Ref: https://discuss.kubernetes.io/t/nginx-ingress-install-failure/5379/4


1

Try using this:- use-forwarded-headers apiVersion: v1 kind: ConfigMap data: use-forwarded-headers: "true" metadata: name: nginx-configuration namespace: default


1

I don't think it is the compatibility, need to really see your configuration to be sure. But most likely, you block something wrongly. If you use the default network policy api networking.k8s.io/v1 notice that it only allows what is defined.


1

The ConfigMap and Annotation configuration have different purposes. As per nginx-configuration/configmap/#ssl-protocols: Sets the SSL protocols to use. The default is: TLSv1.2 TLSv1.3 ngx_http_ssl_module.html#ssl_protocols Context: http, server i.e., enable the specified protocols to your Nginx Controller. client --ssl-protocols-> controller --> ...


1

I'm trying to architect a micro-service application, that runs in Kubernetes. It consists of several RESTful APIs. I want a central point to implement authentication for these APIs. This is a good idea. So what I'm looking for is a/the way to have central authentication in Kubernetes for users accessing the APIs. I would also require to be able to ...


1

The thing I was looking for was external-auth in ingress-nginx. I created a simple service with nodejs which took over all the basic-auth logic. Then I used an external link to this service in k8s annotations for restricted resources. annotation snippet: annotations: nginx.ingress.kubernetes.io/auth-url: http://service-name.default.svc.cluster.local:...


1

There are two main reasons for this issue to happen: Your dns are not exposed. Your code is redirecting to a https address (and since you are working in your local machine, most likely you don't have a secure certificate) CASE 1 - Exposing DNS On linux you can solve it like: minikube ip vim /etc/hosts Add the ip from the first step and the hostname you ...


1

There is no built-in configuration/annotation to handle this. Although, you can use the server-snippet annotation to create a custom configuration that intercepts the error 503, proxying the request to a service that is serving your custom error page. Example: apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: ingress annotations: ...


Only top voted, non community-wiki answers of a minimum length are eligible