Kubernetes Blocked Mixed Active Content

Question

Issue:

When working with K8's [Kubernetes] on development, I'm running into the issue where my Ingress/Nginx seems keep my client side (React) from pulling data from my API (Flask/Python).

Details:

The connection between the client and API is facilitated using an Environment Variable that we'll call API_URL for the sake of this post. API_URL is used so that the Client knows which API routes to GET and POST.

On Minikube with K8's in dev, the Minikube IP that is provided forces https from what I understand (or maybe it's ingress/nginx?). The API_URL environment variable value is value: api-cluster-ip-service. However, when I hit the dev site it's showing that this value gets assigned to http://localhost (not-https)

This causes: Blocked loading mixed active content “http://localhost/server/stuff". As a result, I can't pull anything from my API.

Question:

Is there a recommended approach for this? Perhaps a way to turn https off on dev (I don't even know if that's possible)? Or maybe I need a certificate for localhost? I'm fairly new to Kubernetes so any help is much appreciated!

Ingress-server.yaml

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: ingress-service
  annotations:
    kubernetes.io/ingress.class: nginx
spec:
  rules:
    - http:
        paths:
          - path: /
            backend:
              serviceName: client-cluster-ip-service
              servicePort: 3000
          - path: /api/
            backend:
              serviceName: server-cluster-ip-service
              servicePort: 5000

Ingress Namespace output

kubectl get ing --all-namespaces
default     ingress-service   *       10.0.2.15   80      4d21h

@dizzy, have you tried specifying the host in your .yaml? Also you can disable the redirect adding annotation nginx.ingress.kubernetes.io/ssl-redirect: "false" — Crou

dizzy dizzy · Accepted Answer · 2019-01-27T21:09:46

I found the cause of my problem...and the error message was fairly misleading. On a local environment, my Client side talks to my API via http://localhost/api/. However, I realized that because I was on Minikube, it's no longer on localhost (because Minikube has it's own IP). Once I changed my API_URL to http:// it began working immediately.

The only challenge here is that minikube, when stopped, changes the IP on each refresh, meaning I need to grab the IP and update the API_URL each time. However, that's a separate question/answer.

Summary:

Changed my API_URL from http://localhost to the Minikube IP. Began working immediately.

Kubernetes Blocked Mixed Active Content

1 Answers