Felix Feedback #2
Conversation
| @@ -22,8 +22,17 @@ As you embark on these exercises, you're set to learn key practices in modern ap | |||
|
|
|||
| By the end of these exercises, you'll have a solid foundation in deploying and managing Kubernetes applications using Argo CD. | |||
|
|
|||
| > Hint to advanced topics that are beneficial to expert users. Like: | |||
There was a problem hiding this comment.
this should be towards the end right? Probably better if the beginning is not too cluttered right?
There was a problem hiding this comment.
Yeah, maybe just as a follow up. Anyway I wanted to point out that the Kutespace is not only useful for novices but for any knowledge level. It can be used as an "Argo CD dev/staging environment".
| ## Getting Started | ||
|
|
||
| > Link to https://codespaces.new/kutespaces/argocd |
There was a problem hiding this comment.
people get a little confused when they never used a codespace. Whats your preferred way to intruct them step by step?
- go to profile->settings->default editor to vs code, then open link https://codespaces.new/kutespaces/argocd
- go to top right corner, open codespace, wait for it to load, go to top left corner, press open in codespace
- open https://codespaces.new/kutespaces/argocd, wait for it to set up, then go to top left corner and open in vscode
3 sounds best now that I think about it.
There was a problem hiding this comment.
Opening the Codespace in the browser first comes with a risk. If the user forgets to open in VSCode, it almost works fine except for the ingress. I wish they added the dropdown to choose where to open it to the initial step.
I'm for (1) or (3) with no strong preference.
btw: As soon as the Codespace is created, you can specify it in the URL: https://github.com/codespaces/silver-space-fishstick-j6j7vwwjcqrwp?editor=vscode
| @@ -79,9 +88,16 @@ Here's a hands-on exercise to illustrate the power of GitOps: | |||
|
|
|||
| 1. Open the podinfo app and observe its default jade green background. | |||
| 2. Dive into the `manifests/podinfo/resources/deployment.yaml`` file to see its configuration. Locate the `PODINFO_UI_COLOR` environment variable and update its value to the golden hue of `#FFD700`. | |||
|
|
|||
| > Connecting the Git Repo Server with the Argo CD webhook would be user useful here to avoid confusion and automagically apply the updates. | |||
There was a problem hiding this comment.
webhook is actually quite hard because you need to send a certain payload with all the files that changed. I found a previous error now in adjusting the poll frequency. It works now and I adjusted the poll frequency to 5s now. That should be sufficient.
| @@ -92,12 +108,17 @@ Here's a hands-on exercise to illustrate the power of GitOps: | |||
| The beauty of GitOps lies in its ability to seamlessly reflect your git repository's state onto your cluster. Should you decide that the golden glimmer of podinfo doesn't quite suit your taste, reverting is a breeze: | |||
|
|
|||
| 1. Whip open your terminal and run `git log` to retrieve the hash of the commit you wish to undo. | |||
|
|
|||
| > Connect this with the Gitlens extension, e.g. link directly to Git history? Maybe too fancy for now. | |||
There was a problem hiding this comment.
mhh I'd like to not add that complexity. especially if users didn't use gitlens before it may even be confusing and add cognitive load (it does for me). I think for this single command git log does its job well. However, I could add the git revert HEAD~n to allow the user to undo n commits. Happens sometimes that users did 2 commits e.g. they made an error first or changed color 2 times.
| 2. Swiftly revert the change with `git revert <COMMIT HASH>` followed by `git push` to update the repository. | ||
| 3. Nudge the process along by refreshing the podinfo application within the Argo CD dashboard. | ||
| 4. Keep an eye on the transition by running `watch kubectl get pods -n podinfo`. This command lets you observe in real-time as Kubernetes orchestrates the replacement of the pod. | ||
| 5. Be greeted once more by the familiar, soothing jade green background of podinfo as the changes take hold. | ||
|
|
||
| ### Exercise 5: Unterstand GitOps End-to-End | ||
| ### Exercise 5: Understand GitOps End-to-End |
There was a problem hiding this comment.
mhh I definitely need to make the section more engaging.
Not sure about the order. I think this should still be located before deploying your own application so that you understand whats going on and then try it yourself when deploying your own application so that it clicks. I noticed that without this chapter users manage to do the tasks without learning anything because they can just follow instructions 1:1.
I think I should move this after game-2048 but still leave it before deploying your own application and before deploying the real world example.
There was a problem hiding this comment.
I'm not 100% sure if most users are interested in the custom SSH or if they are overwhelmed by it. We must explain GitOps as a concept though. Maybe we can clear up some of the Codespace-specific explanations and leave it generic.
No description provided.