Issues Deploying Plane CE via Gateway API (Cilium Envoy) and ArgoCD: “Instance Not Configured”

Support Self-Hosted
,
1

Hi everyone,

I am currently deploying Plane CE (v1.5.0) in a Kubernetes cluster using a modern GitOps stack: ArgoCD for continuous delivery and Cilium Envoy Gateway (API Gateway) for inbound traffic.

Although the UI loads successfully on my custom domain, I cannot complete the initial setup/login. When entering an email address, I receive the following error:

“Instance not configured. Please contact the administrator.”

My Current Configuration

  1. ArgoCD Application (Helm values):
    I am using the official Helm chart (https://plane.so) with ingress.enabled: false and the following environment variables:

     apiVersion: argoproj.io/v1alpha1
 kind: Application
 metadata:
   name: plane
   namespace: argocd
 spec:
   project: default
   source:
     repoURL: https://helm.plane.so/
     chart: plane-ce
     targetRevision: 1.5.0
     helm:
       values: |
         ingress:
           enabled: false
 
         env:
           web_url: https://plane.local
           allowed_hosts: plane.local
           cors_allowed_origins: https://plane.local
 
           secret_key: "......."
           live_server_secret_key: "......."
 
         postgres:
           storageClass: local-path
           volumeSize: 10Gi
 
         redis:
           storageClass: local-path
           volumeSize: 5Gi
 
         minio:
           storageClass: local-path
           volumeSize: 10Gi
 
         rabbitmq:
           storageClass: local-path
           volumeSize: 5Gi
 
   destination:
     server: https://kubernetes.default.svc
     namespace: plane
 
   syncPolicy:
     automated:
       prune: true
       selfHeal: true
     syncOptions:
       - CreateNamespace=true

  2. Gateway API Configuration (HTTPRoute):

     apiVersion: gateway.networking.k8s.io/v1
 kind: HTTPRoute
 metadata:
   name: plane-route
   namespace: plane
   annotations:
     external-dns.alpha.kubernetes.io/hostname: plane.local
 spec:
   parentRefs:
     - name: main-gateway
       namespace: default
 
   hostnames:
     - plane.local
 
   rules:
     - matches:
         - path:
             type: PathPrefix
             value: /api
         - path:
             type: PathPrefix
             value: /auth
       backendRefs:
         - name: plane-api
           port: 8000
 
     - backendRefs:
         - name: plane-web
           port: 3000

Currently, the official documentation and Helm charts for Plane CE are primarily focused on standard Ingress controllers. When deploying Plane in a modern networking environment using Cilium Envoy Gateway and the Gateway API, there is a lack of clear guidance on configuring HTTPRoute resources to handle routing correctly.

I am currently experiencing issues with the initial authentication process, as the standard Ingress-based setup cannot be directly translated into an HTTPRoute configuration without specific details on path/header handling for Plane’s microservices.

2

It looks like you might be missing a few required routes in your plane route file, which could affect how the Plane app runs. For eg: God Mode which is the instance configuration page that you are not able to access.

Could you take a look at the Plane ingress routes and make sure they’re all set up properly?