|
8 | 8 |
|
9 | 9 | We use this for `inner-loop` Kubernetes development. Note that it is not appropriate for production use but is a great `Developer Experience`. Feedback calls the approach `game-changing` - we hope you agree!
|
10 | 10 |
|
11 |
| -## Notes for the Hands-on Lab |
12 |
| - |
13 |
| -We have over 300 people registered!!! |
14 |
| - |
15 |
| -Please mute your Teams client unless you're asking a question. |
16 |
| - |
17 |
| -Please turn your cameras off. While we love to see your smiling faces, we have a lot of people registered and this will save us a lot of bandwidth. |
18 |
| - |
19 |
| -Please raise your hand or use the Teams chat to ask questions. We will have several team members available to answer questions. The presenters will pause after every step to address any issues or questions. |
20 |
| - |
21 | 11 | For ideas, feature requests, future sessions and any long-running discussion, please use GitHub discussions so we can collaborate and follow up.
|
22 | 12 |
|
23 |
| -We are on a tight schedule, so we may have to `table` discussions. We will use GitHub Discussions to follow up and setup follow-on sessions if there is enough interest in the topic. Please `up vote` and `react` to the discussion topics that are interesting to you. |
24 |
| - |
25 |
| -We may have a surprise guest or two ... :) |
26 |
| - |
27 | 13 | This Codespace is tested with `zsh` and `oh-my-zsh` - it "should" work with bash but hasn't been fully tested. For the HoL, please use zsh to avoid any issues.
|
28 | 14 |
|
29 |
| -You can run the `dev container` locally and you can also connect to the Codespace with a local version of VS Code. For the HoL, please use GitHub Codespaces in your browser to avoid any issues. |
| 15 | +You can run the `dev container` locally and you can also connect to the Codespace with a local version of VS Code. |
30 | 16 |
|
31 | 17 | You will have access after the event, so please experiment and add any issues to the GitHub Discussion.
|
32 | 18 |
|
33 | 19 | We LOVE PRs! (this is a downstream repo, so post in GitHub Discussions if you want to PR and we'll point you to the right repo and ensure access)
|
34 | 20 |
|
35 |
| -Enough of the `fine print` - let's hack! |
36 |
| - |
37 | 21 | ## Shoutout for the "."
|
38 | 22 |
|
39 | 23 | GitHub just released some pretty AWESOME new features including `"."` and `Codespaces`
|
@@ -75,33 +59,6 @@ HUGE shoutout and thank you to GitHub, DevDiv and 1ES for the amazing support ov
|
75 | 59 |
|
76 | 60 | ```
|
77 | 61 |
|
78 |
| -## DDOS Issue |
79 |
| - |
80 |
| -> In the morning session, we ran into what we think is a DDOS issue while creating the jumpbox |
81 |
| -
|
82 |
| -- Your output should look like this |
83 |
| - |
84 |
| - ```bash |
85 |
| - |
86 |
| - # start a jumpbox pod |
87 |
| - pod "jumpbox" deleted |
88 |
| - pod/jumpbox created |
89 |
| - pod/jumpbox condition met |
90 |
| - ###### If you get an error after this #### |
91 |
| - # run make patch-jumpbox |
92 |
| - # Run an interactive bash shell in the jumpbox |
93 |
| - # kj |
94 |
| - # use kje <command> |
95 |
| - # kje http ngsa-memory:8080/version |
96 |
| - |
97 |
| - ``` |
98 |
| - |
99 |
| -- If the failure as after the comment, run `make patch-jumpbox` until it works |
100 |
| - - this is the normal failure we saw this morning |
101 |
| -- if the failure was after `start a jumpbox` and before `#### if you get an error ...` |
102 |
| - - run `make jumpbox` |
103 |
| -- If you see a different error, raise your hand and we'll debug |
104 |
| - |
105 | 62 | 
|
106 | 63 |
|
107 | 64 | ## Validate Deployment
|
|
0 commit comments