<p>I'm trying to connect an external webflow page to our kubernetes cluster ingress on GCP GKE. Specifically, I want everything at <a href="http://www.domain.com" rel="nofollow noreferrer">www.domain.com</a> to go to the external webflow service, and everything at <a href="http://www.domain.com/app" rel="nofollow noreferrer">www.domain.com/app</a> to go to our local service in the cluster.</p>
<p>I've seen this question <a href="https://stackoverflow.com/questions/65919773/ingress-nginx-proxy-to-outside-website-webflow-hosted">Ingress Nginx Proxy to Outside Website (Webflow hosted)</a> and followed it, but I couldn't get it working. I keep getting an error
<code>Translation failed: invalid ingress spec: service &quot;default/external-service&quot; is type &quot;ExternalName&quot;, expected &quot;NodePort&quot; or &quot;LoadBalancer&quot;; service &quot;default/external-service&quot; is type &quot;ExternalName&quot;, expected &quot;NodePort&quot; or &quot;LoadBalancer&quot;</code></p>
<p>Here's my setup</p>
<p>External Service:</p>
<pre><code>apiVersion: v1
kind: Service
metadata:
  name: external-service
  namespace: default
spec:
  externalName: participant-homepage-9f8712.webflow.io
  ports:
  - port: 443
    protocol: TCP
    targetPort: 443
  sessionAffinity: None
  type: ExternalName
status:
  loadBalancer: {}
</code></pre>
<p>Ingress:</p>
<pre><code>apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  annotations:
    ingress.gcp.kubernetes.io/pre-shared-cert: _,
    ingress.kubernetes.io/backends: _,
    ingress.kubernetes.io/forwarding-rule: _,
    ingress.kubernetes.io/https-forwarding-rule: _,
    ingress.kubernetes.io/https-target-proxy: _,
    ingress.kubernetes.io/preserve-host: &quot;false&quot;
    ingress.kubernetes.io/secure-backends: &quot;true&quot;
    ingress.kubernetes.io/ssl-cert: _,
    ingress.kubernetes.io/static-ip: _,
    ingress.kubernetes.io/target-proxy: _,
    ingress.kubernetes.io/url-map: _,
    networking.gke.io/managed-certificates: _,
    nginx.ingress.kubernetes.io/backend-protocol: HTTPS
    nginx.ingress.kubernetes.io/server-snippet: |
      proxy_ssl_name participant-homepage-9f8712.webflow.io;
      proxy_ssl_server_name on;
    nginx.ingress.kubernetes.io/upstream-vhost: participant-homepage-9f8712.webflow.io
  name: my-ingress
  namespace: default
spec:
  backend:
    serviceName: external-service
    servicePort: 443
  rules:
  - host: www.honeybeehub.xyz
    http:
      paths:
      - backend:
          serviceName: app-service
          servicePort: 80
        path: /app/*
        pathType: ImplementationSpecific
      - backend:
          serviceName: external-service
          servicePort: 443
        path: /*
        pathType: ImplementationSpecific
status:
  loadBalancer:
    ingress:
    - ip: _._._._
</code></pre>
<p>Any help would be greatly appreciated. Thank you!</p>

<p>The reason why the steps on the question you quoted <a href="https://stackoverflow.com/questions/65919773/ingress-nginx-proxy-to-outside-website-webflow-hosted">Ingress Nginx Proxy to Outside Website (Webflow hosted)</a> are not working, is because that question focuses on EKS (Amazon Elastic Kubernetes Service). ExternalName Services are not supported in GCE Ingress, as you can see in the following <a href="https://stackoverflow.com/questions/53107348/error-creating-ingress-path-with-gce-externalname">question</a>.
What I can recommend to you is to post it as a Feature Request on the <a href="https://www.google.com/url?q=https://cloud.google.com/support/docs/issue-trackers&amp;sa=D&amp;source=docs&amp;ust=1636750079733000&amp;usg=AOvVaw2ocSL1lAPc3gUomJhKCRJm" rel="nofollow noreferrer">Google's Issue tracker</a></p>
