Kubernetes + Ingress Controller + Http2 + React + e6 polyfil

9/21/2019

Our Kubernetes Cluster has a Windows Node.

We have a nodeJS react server side rendering on express.

We also have an Ingress Controller which has two routes both that are backed by LetsEncrypt Cert for testing.

Here is our debate at work.

We have consultants who working on an Azure App service via Linux Containers.

Our production environment will be windows on Azure Kubernetes.

When I deployed the app to our production windows container environment.

I had to change the webpack polyfil to an e6promise to get it to work for Windows.

The consultants used a different version of the polyfil that worked with Linux.

Now during testing. Our testers have reported that we are having issues with IE.

I told them it’s most likely the polyfil.

Other people on our technical team believe it’s the Ingress Controller that’s is using http2.

Since express nodeJS server doesn’t support http2 from what I was told. They believe it’s causing the problems with IE.

So my question here.

Which is more likely here.

Me using a completely differently webpack polyfil that is an e6 promise version.

Or

It’s http2 and the ingress controller is now some how messing with IE only.

I think it’s the polyfil. I could be wrong here.

So I decided to hit the threads about this.

-- Mark Richardson
azure
kubernetes
kubernetes-ingress
nodejs-server
polyfills

0 Answers