add first version of gke-starter values file

[cjidboon94]

Tracking issue

#5016

Closes #5016

Why are the changes needed?

There are examples of how to deploy flyte minimally on AWS/EKS described in Single Cluster Simple Cloud Deployment but not for GCP/GKE.
This values file makes it easier for new people to deploy.

What changes were proposed in this pull request?

A minimal value file with default settings filled in for a minimal deployment on GKE/GCP using the flyte-binary chart

How was this patch tested?

I used it to deploy on GKE.

Setup process

Screenshots

Check all the applicable boxes

• I updated the documentation accordingly. (not sure if applicable)
• All commits are signed-off.

Related PRs

Docs link

[welcome]

Thank you for opening this pull request! 🙌

These tips will help get your PR across the finish line:

• Most of the repos have a PR template; if not, fill it out to the best of your knowledge.
• Sign off your commits (Reference: DCO Guide).

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 58.99%. Comparing base (5fc57fa) to head (f57b636).

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #5026      +/-   ##
==========================================
- Coverage   58.99%   58.99%   -0.01%     
==========================================
  Files         645      645              
  Lines       55648    55648              
==========================================
- Hits        32831    32830       -1     
- Misses      20222    20223       +1     
  Partials     2595     2595              

Flag	Coverage Δ
unittests	58.99% <ø> (-0.01%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[davidmirror-ops]

This is great. Thank you!

[davidmirror-ops]

For the failing Helm test, can you try running make helm from the base folder in your fork and then push the changes?

[cjidboon94]

For the failing Helm test, can you try running make helm from the base folder in your fork and then push the changes?

When I try to run make helm, I also get this (same as output of failing helm test):

bash script/generate_helm.sh
+ echo 'Generating Helm'
Generating Helm
+ HELM_SKIP_INSTALL=false
+ '[' false '!=' true ']'
+ curl https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3
+ bash
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 11679  100 11679    0     0   140k      0 --:--:-- --:--:-- --:--:--  140k
Helm v3.14.3 is already latest
+ helm version
version.BuildInfo{Version:"v3.14.3", GitCommit:"f03cc04caaa8f6d7c3e67cf918929150cf6f3f12", GitTreeState:"clean", GoVersion:"go1.21.7"}
+ DEPLOYMENT_CORE='eks gcp'
+++ dirname script/generate_helm.sh
++ cd script
++ pwd
+ DIR=<root>/projects/flyte/script
+ HELM_CAPABILITIES='-a rbac.authorization.k8s.io/v1 -a networking.k8s.io/v1/Ingress -a apiextensions.k8s.io/v1/CustomResourceDefinition'
+ helm dep update <root>/projects/flyte/script/../charts/flyte-deps/
Getting updates for unmanaged Helm repositories...
...Unable to get an update from the "https://googlecloudplatform.github.io/spark-on-k8s-operator" chart repository:
        failed to fetch https://googlecloudplatform.github.io/spark-on-k8s-operator/index.yaml : 404 Not Found
...Successfully got an update from the "https://kubernetes.github.io/dashboard/" chart repository
...Successfully got an update from the "https://helm.dask.org" chart repository
...Successfully got an update from the "https://charts.bitnami.com/bitnami" chart repository
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "flyteorg" chart repository
...Successfully got an update from the "jetstack" chart repository
Update Complete. ⎈Happy Helming!⎈
Error: no cached repository for helm-manager-06b85d82fd48330fadb64937df35abfe0b44014d605c8ab4244eb6e6fcc29780 found. (try 'helm repo update'): open <root>/.cache/helm/repository/helm-manager-06b85d82fd48330fadb64937df35abfe0b44014d605c8ab4244eb6e6fcc29780-index.yaml: no such file or directory
make: *** [Makefile:39: helm] Error 1

And creates no changes that I can commit

[eapolinario]

@cjidboon94 , can you merge master (to bring in d5784e5) and re-run?

[cjidboon94]

I see new tests failing after having bumped up the chart. Should I have done that? Or should I revert/undo the latest commit?

[davidmirror-ops]

@cjidboon94 Please revert :)

[lowc1012]

@cjidboon94 @davidmirror-ops
I'll create a PR to fix helm check CI errors, plz stay tuned

[lowc1012]

@davidmirror-ops @pingsutw
Could you help review this PR?

@cjidboon94
I think after my PR is merged, you can revert ddfe840 and rebase master branch to pass CI

[cjidboon94]

@davidmirror-ops Since #5072 is merged, I have rebased myself onto the new master and the tests aren't failing anymore. I think this is ready to merge now?

[davidmirror-ops]

Thank you!

[welcome]

Congrats on merging your first pull request! 🎉