-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: create Cloud Shell tutorial for Garden #6
Conversation
c7b32d5
to
1e56264
Compare
|
I've figured this out. K3d uses its own registry and conveniently disregards the local registry Garden pushes images to. For a solution, see comment. I'm trying out k3s (so k3d minus the docker) to see about using k3s directly, which supports the |
@twelvemo, @mkhq , @10ko it works! 🎉 The One issue I encountered was the postgres deploy failing and not re-trying (this happened again on a brand new Cloud Shell and I don't know why): I just ran We didn't need a Cloudflare Tunnel, Inlets, etc. because Cloud Shell rewrites localhost links: |
Oh that's so nice that cloud shell rewrites the links! |
|
||
# Copy k3s config to user's home directory | ||
mkdir -p ~/.kube | ||
sleep 5 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is needed to allow k3s time to generate the kubeconfig.
@worldofgeese should we create a separate garden environment for cloud shell or do you want it to be the local environment? |
@twelvemo I think local env is fine unless you think it's a good idea to have a separate one? |
We don't need to clone the quickstart if the tutorial lives inside the quickstart-example repo.
Dash tries to open a URL for authentication: unsupported by Cloud Shell
d0e6dd3
to
6502987
Compare
@mkhq added button with shortlink to original post. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
deploy | ||
``` | ||
|
||
If you receive an error like the following, wait until the `deploy` has finished, then try again: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why are we getting this error in the first place? 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rendering bug has been fixed!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Use this button to demo:
With shortlink:
We have two types of quickstart tutorials: the Dashboard-driven experience and following the directions in the docs. Both require users to install tools on their local filesystem and clone the quickstart to get started, increasing friction. With Cloud Shell, a user gets an integrated experience, with a web editor (Eclipse Theia) on one side, and an interactive tutorial pane on the right. The tutorial pane is interactive using Markdown extensions that can do things like spotlight Editor elements and open files when clicked, creating a delightful, user-friendly experience.
Spotlighting UI elements:
Notes for reviewer:
I've chosen in this tutorial to use minikube inside a user's Cloud Shell. We can, at our option, also include instructions for provisioning and using a GKE cluster. The advantages to using Cloud Shell for this are that Cloud Shell is already authorized to the user so it's a muck quicker onboarding to the full remote experience. And Cloud Shell can present the GCP project picker inside the tutorial window.
Integrated project picker: