<p>I have followed this <a href="https://thechief.io/c/cloudplex/what-kubeflow-and-how-deploy-it-kubernetes/" rel="nofollow noreferrer">doc</a> to deploy kubeflow on gke</p>
<blockquote>
<p>Error:404 page not found</p>
</blockquote>
<p>when Accessing Central dashboard</p>
<p>Try to deploy multiple times but still getting same error</p>
<p>I'm new to kubernets</p>

Martin rudez
<p>As per this official <a href="https://v0-5.kubeflow.org/docs/gke/troubleshooting-gke/#404-page-not-found-when-accessing-central-dashboard" rel="nofollow noreferrer">doc</a>, try below troubleshooting steps to resolve your error :</p>
<blockquote>
<p>This section provides troubleshooting information for 404s, page not
found, being return by the central dashboard which is served at</p>
<pre><code>https://${KUBEFLOW_FQDN}/
</code></pre>
<p>KUBEFLOW_FQDN is your project’s OAuth web app URI domain name
<code>&lt;name&gt;.endpoints.&lt;project&gt;.cloud.goog</code></p>
<p>We can confirm that the Ambassador reverse proxy is functioning
properly by running the following command because we were able to sign
in.</p>
<pre><code> kubectl -n ${NAMESPACE} get pods -l service=envoy
    NAME                     READY     STATUS    RESTARTS   AGE
   envoy-76774f8d5c-lx9bd   2/2       Running   2          4m
   envoy-76774f8d5c-ngjnr   2/2       Running   2          4m
   envoy-76774f8d5c-sg555   2/2       Running   2          4m
</code></pre>
<p>Now try to Attempt different administrations to check whether they're
open for instance</p>
<pre><code>   https://${KUBEFLOW_FQDN}/whoami
   https://${KUBEFLOW_FQDN}/tfjobs/ui
   https://${KUBEFLOW_FQDN}/hub
</code></pre>
<p>We know that the issue is specific to the central dashboard and not
ingress if other services are accessible.</p>
<p>Now check that the central dashboard is running</p>
<pre><code>kubectl get pods -l app=centraldashboard
NAME                                READY     STATUS    RESTARTS   AGE
centraldashboard-6665fc46cb-592br   1/1       Running   0          7h
</code></pre>
<p>Check that an Ambassador route is properly defined or not</p>
<pre><code>kubectl get service centraldashboard -o jsonpath='{.metadata.annotations.getambassador\.io/config}'

apiVersion: ambassador/v0
  kind:  Mapping
  name: centralui-mapping
  prefix: /
  rewrite: /
  service: centraldashboard.kubeflow
</code></pre>
<p>,</p>
<p>Take a look at the logs of Envoy for blunders. Check to see if there
are any errors like these that indicate a problem parsing the route.
In the event that you are utilizing the new Stackdriver Kubernetes
observing you can utilize the accompanying channel in the stackdriver
console</p>
<pre><code> resource.type=&quot;k8s_container&quot;
 resource.labels.location=${ZONE}
 resource.labels.cluster_name=${CLUSTER}
 metadata.userLabels.service=&quot;ambassador&quot;
&quot;could not parse YAML&quot;
</code></pre>
</blockquote>
<p>You can also refer to this <a href="https://v1-5-branch.kubeflow.org/docs/distributions/gke/" rel="nofollow noreferrer">doc</a> for more information aboutdeploying kubeflow on GKE.</p>
