Enable apiserver access

[pbiggar]

Part of #3508

This allows users to test out the new backend in the editor by going to

https://darklang/a/canvasname?fsharp-backend=true

At also allows them to test loading the editor by going to

https://darklang.com/a-testing-fsharp/canvasname

Or to get both:

https://darklang.com/a-testing-fsharp/canvasname?fsharp-backend=true

[pbiggar]

predeployment checks are expected to fail as I haven't deployed the ingress configuration yet.

[StachuDotNet]

I don't quite know what's happening in nginx.conf or the ingress.yaml file, but rest all seems appropriate.

[pbiggar]

fyi

I don't quite know what's happening in nginx.conf or the ingress.yaml file, but rest all seems appropriate.

-  location ~ (/a/|/api/|/login|/logout|/check-apiserver) {
+  location ~ (/a/|/a-testing-fsharp/|/api/|/api-testing-fsharp/|/login|/logout|/check-apiserver) {

This matches (using regex) the paths /a/, /api/, etc, and passes them on to the apiserver on port 9001. So the change says to also pass on the paths /a-testing-fsharp/ and /api-testing-fsharp.

  rules:
    # See
    # https://cloud.google.com/kubernetes-engine/docs/how-to/load-balance-ingress#creating_an_ingress
    # These rules are intended to enable one user onto the new F# backend, while we
    # see what works.
    - http:
        paths:
-         # No slash at the end
-         - path: /a/trydarkfsharp
+         # Testing so that any user can use these
+         - path: /a-testing-fsharp/*
            pathType: ImplementationSpecific
            backend:
              service:
                name: apiserver-service
                port:
                  number: 80

This rule tells the load balancer to send traffic matching these paths to the apiserver-service (if it doesn't match, it goes to the defaultBackend, which is the darklang-nodeport (which should be called editor-service).

[StachuDotNet]

Thank you for that context!