You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Office Hours is a live stream where we answer live questions about Kubernetes
6
+
from users on the YouTube channel. Office hours are a regularly scheduled
7
+
meeting where people can bring topics to discuss with the greater community.
8
+
They are great for answering questions, getting feedback on how you’re using
9
+
Kubernetes, or to just passively learn by following along.
10
+
---
11
+
1
12
# Kubernetes Community Office Hours
2
13
3
-
Office Hours is a live stream where we answer live questions about Kubernetes from **users** on the [YouTube channel](https://www.youtube.com/c/KubernetesCommunity/). Office hours are a regularly scheduled meeting where people can bring topics to discuss with the greater community. They are great for answering questions, getting feedback on how you’re using Kubernetes, or to just passively learn by following along.
14
+
Office Hours is a live stream where we answer live questions about Kubernetes
15
+
from **users** on the [YouTube channel]. Office hours are a regularly scheduled
16
+
meeting where people can bring topics to discuss with the greater community.
17
+
They are great for answering questions, getting feedback on how you’re using
18
+
Kubernetes, or to just passively learn by following along.
4
19
5
20
### When and Where
6
21
7
22
Third Wednesday of every month, there are two sessions:
8
23
9
-
- European Edition: [9am ET](http://www.thetimezoneconverter.com/?t=09:00&tz=ET%20%28Eastern%20Time%29)
10
-
- Western Edition: [9am PT](http://www.thetimezoneconverter.com/?t=12:00&tz=ET%20%28Eastern%20Time%29)
24
+
- European Edition: [9am ET]
25
+
- Western Edition: [9am PT]
11
26
12
-
Tune into the [Kubernetes YouTube Channel](https://www.youtube.com/c/KubernetesCommunity/live) to follow along.
27
+
Tune into the [Kubernetes YouTube Channel] to follow along.
13
28
14
-
You can post questions on the [#office-hours channel](https://kubernetes.slack.com/messages/office-hours) on Slack, or if you like you can submit your question to Stack Overflow and have us take a look.
29
+
You can post questions on the [#office-hours channel] on Slack, or if you like
30
+
you can submit your question to Stack Overflow and have us take a look.
15
31
16
32
### How it Works
17
33
18
34
#### Bringing your own question
19
35
20
-
If you submit a question on [discuss.kubernetes.io](https://discuss.kubernetes.io) that is prewritten that always makes it easier for the panelists to read all your information ahead of time. You can also submit a question from [StackOverflow](https://stackoverflow.com/questions/tagged/kubernetes).
36
+
If you submit a question on [discuss.kubernetes.io] that is prewritten that
37
+
always makes it easier for the panelists to read all your information ahead of
38
+
time. You can also submit a question from [StackOverflow].
21
39
22
-
As a thanks to the community the person asking the question can then ensure that a well written answer makes it way to the question afterwards so that we can build a knowledge base and help maintain the incoming questions. We can also use the video archive of each meeting to bring context to each question we answer.
40
+
As a thanks to the community the person asking the question can then ensure that
41
+
a well written answer makes it way to the question afterwards so that we can
42
+
build a knowledge base and help maintain the incoming questions. We can also use
43
+
the video archive of each meeting to bring context to each question we answer.
23
44
24
-
Questions that aren’t addressed or need work can be punted to the next week or we can encourage other people to give them a look, at a bare minimum we can at least help socialize the difficult questions.
45
+
Questions that aren’t addressed or need work can be punted to the next week or
46
+
we can encourage other people to give them a look, at a bare minimum we can at
47
+
least help socialize the difficult questions.
25
48
26
49
#### What’s on topic?
27
50
28
-
Specific questions about Kubernetes as pertaining to the topic. Since this is a Q&A format, we’d like questions that can be answered generally. So for example:
29
-
30
-
- Bad: My ingress configuration is broken please fix it. (Dependent on local configuration)
31
-
- Good: My ingress configuration is broken can you discuss what problems you usually see and common mistakes that people make so I can avoid them? (Generalized and can communicate things that can help multiple people)
32
-
- Bad: How do I deploy my application in Kubernetes? (Easy to look up, tons of content on this)
33
-
- Good: What best practice techniques are there for deploying applications in Kubernetes? (Nuanced version lets us cover RBAC, application lifecycle)
51
+
Specific questions about Kubernetes as pertaining to the topic. Since this is a
52
+
Q&A format, we’d like questions that can be answered generally. So for example:
53
+
54
+
- Bad: My ingress configuration is broken please fix it. (Dependent on local
55
+
configuration)
56
+
- Good: My ingress configuration is broken can you discuss what problems you
57
+
usually see and common mistakes that people make so I can avoid them?
58
+
(Generalized and can communicate things that can help multiple people)
59
+
- Bad: How do I deploy my application in Kubernetes? (Easy to look up, tons of
60
+
content on this)
61
+
- Good: What best practice techniques are there for deploying applications in
62
+
Kubernetes? (Nuanced version lets us cover RBAC, application lifecycle)
34
63
- Bad: My pods aren’t coming up on a node. (Vague)
35
-
- Good: My pods aren’t coming up or misbehaving, what are the debugging steps to find out the root cause? (Helps us communicate the thought process for debugging to a general audience)
64
+
- Good: My pods aren’t coming up or misbehaving, what are the debugging steps to
65
+
find out the root cause? (Helps us communicate the thought process for
66
+
debugging to a general audience)
36
67
37
68
#### What’s off topic?
38
69
39
-
Developer/Contributor questions: This event is for end users and operators, there is a separate livestream called [Meet our Contributors](/mentoring/meet-our-contributors.md) where you can ask questions about getting started contributing, participating in peer reviews, and other development topics.
70
+
Developer/Contributor questions: This event is for end users and operators,
71
+
there is a separate livestream called [Meet our Contributors] where you can ask
72
+
questions about getting started contributing, participating in peer reviews,
73
+
and other development topics.
40
74
41
-
Local installation and debugging: The participants don’t have access to your network or your hardware. The host can/should help the user transform a vague question into something answerable and reusable.
75
+
Local installation and debugging: The participants don’t have access to your
76
+
network or your hardware. The host can/should help the user transform a vague
We're always looking for volunteers to host and answer questions. Volunteers looking to host hours in
52
-
more time zones are also welcome to join in and help us expand.
87
+
We're always looking for volunteers to host and answer questions. Volunteers
88
+
looking to host hours in more time zones are also welcome to join in and help us
89
+
expand.
53
90
54
-
-[Volunteer working sheet](http://bit.ly/k8s-office-hours-volunteers)
91
+
-[Volunteer working sheet]
55
92
56
-
If you have any questions ping [@castrojo](https://github.com/castrojo).
93
+
If you have any questions ping [@castrojo].
57
94
58
95
## Host Information
59
96
@@ -62,41 +99,86 @@ This information is for the host/panel to prep the show.
62
99
### Host Checklist
63
100
64
101
-[ ] 1st of the month: Create the livestream events in YouTube.
65
-
-[ ] 1st of the month: Update topic in #kubernetes-users, #office-hours, and #kubernetes-novice with the correct YouTube URLs.
66
-
-[ ] 2nd wednesday of the month: Remind panelists of dates, get confirmation for each event.
67
-
-[ ] Monday before: Post "Office hours is this Wednesday" with the links to everything in #kubernetes-users, #office-hours, and #kubernetes-novice.
68
-
-[ ] Monday before: Post to the general section of discuss.k8s.io with a link to the show and a link to this github page. Tag the post with #office-hours
69
-
-[ ] Monday before: Tweet "Office hours is this Wednesday" with the links to everything, send a mail to [email protected] to RT your tweet.
70
-
-[ ] -1h before show: Tweet again, repost "Office hours is going live in ~1h" with the links to everything in #kubernetes-users, #office-hours, and #kubernetes-novice
102
+
-[ ] 1st of the month: Update topic in [#kubernetes-users], [#office-hours],
103
+
and [#kubernetes-novice] with the correct YouTube URLs.
104
+
-[ ] 2nd wednesday of the month: Remind panelists of dates, get confirmation
105
+
for each event.
106
+
-[ ] Monday before: Post "Office hours is this Wednesday" with the links to
107
+
everything in [#kubernetes-users], [#office-hours], and [#kubernetes-novice].
108
+
-[ ] Monday before: Post to the general section of discuss.k8s.io with a link
109
+
to the show and a link to this github page. Tag the post with [#office-hours]
110
+
-[ ] Monday before: Tweet "Office hours is this Wednesday" with the links to
-[ ] -1h before show: Tweet again, repost "Office hours is going live in ~1h"
113
+
with the links to everything in [#kubernetes-users], [#office-hours], and
114
+
[#kubernetes-novice].
71
115
-[ ] -30m before show: Ensure panelists have link to Zoom meeting.
72
-
-[ ] -30m before show: Prep a hack.md document with notes and questions from the channel over the course of the last month, ensure panelists have the URL.
73
-
-[ ] 0: Go live, do the show.
74
-
-[ ] After show: Collate links from the show as markdown and post it in the show thread that you posted in the forums.
75
-
-[ ] After show: Check and publish the video on youtube, ensure it's in the Office Hours playlist.
116
+
-[ ] -30m before show: Prep a hack.md document with notes and questions from
117
+
the channel over the course of the last month, ensure panelists have the URL.
118
+
-[ ] 0: Go live, do the show.
119
+
-[ ] After show: Collate links from the show as markdown and post it in the
120
+
show thread that you posted in the forums.
121
+
-[ ] After show: Check and publish the video on YouTube, ensure it's in the
122
+
Office Hours playlist.
76
123
77
124
### Intro Script
78
125
79
-
Welcome everyone to today’s Kubernetes Office Hours, where we answer your user questions live on the air with our esteemed panel of experts. You can find us in #office-hours on slack, and check the topic for the URL for the information.
126
+
Welcome everyone to today’s Kubernetes Office Hours, where we answer your user
127
+
questions live on the air with our esteemed panel of experts. You can find us in
128
+
[#office-hours] on slack, and check the topic for the URL for the information.
80
129
81
-
- Before we begin let’s start by introducing ourselves: (Give each panelist about a minute)
130
+
- Before we begin let’s start by introducing ourselves: (Give each panelist about
131
+
a minute)
82
132
- Before we start here are the ground rules:
83
-
- This is a Kubernetes event so the Code of Conduct is in effect, please be excellent to each other.
84
-
- This is a judgement-free zone, everyone had to start from somewhere so please help out your buddy by having a supportive environment in the channel.
85
-
- While we will do our best to answer your questions the panel doesn’t have access to your cluster, so live debugging is off topic, but we will do our best to get you moving down the next step.
86
-
- Panelists, you’re encouraged to expand on answers with your experiences and pro-tips.
87
-
- Audience, you can help by pasting in URLs to official docs, blogs, or anything that might be relevant to the topic at hand.
88
-
- Post your questions on discuss.kubernetes.io
89
-
- You can also help us out by tweeting, spreading the word, and paying it forward.
90
-
- This panel is made entirely of volunteers, if you want to rotate in please let us know, we love to have new people rotate in and help out.
133
+
- This is a Kubernetes event so the Code of Conduct is in effect, please be
134
+
excellent to each other.
135
+
- This is a judgement-free zone, everyone had to start from somewhere so please
136
+
help out your buddy by having a supportive environment in the channel.
137
+
- While we will do our best to answer your questions the panel doesn’t have
138
+
access to your cluster, so live debugging is off topic, but we will do our
139
+
best to get you moving down the next step.
140
+
- Panelists, you’re encouraged to expand on answers with your experiences and
141
+
pro-tips.
142
+
- Audience, you can help by pasting in URLs to official docs, blogs, or
143
+
anything that might be relevant to the topic at hand.
144
+
- Post your questions on [discuss.kubernetes.io].
145
+
- You can also help us out by tweeting, spreading the word, and paying it
146
+
forward.
147
+
- This panel is made entirely of volunteers, if you want to rotate in please
148
+
let us know, we love to have new people rotate in and help out.
91
149
92
150
### Contest
93
151
94
-
The hack.md notes document will have a list of who has asked questions, roll a dice to see who won the shirts. On occasion if someone from the audience has been helpful feel free to give them a shirt as well, we want to reward people for helping others. Note: Multi-sided dice not included.
152
+
The hack.md notes document will have a list of who has asked questions, roll a
153
+
dice to see who won the shirts. On occasion if someone from the audience has
154
+
been helpful feel free to give them a shirt as well, we want to reward people
155
+
for helping others. Note: Multi-sided dice not included.
95
156
96
157
### Outro
97
158
98
159
(Note, the companies will change over time depending on the hosts)
99
160
100
-
- Thanks to the following companies for supporting the community with developer volunteers: Giant Swarm, StockX, Pivotal, Pusher.com, Weaveworks, VMware, University of Michigan, Red Hat, and Utility Warehouse. Special thanks to CNCF for sponsoring the t-shirt giveaway.
101
-
102
-
And lastly, feel free to hang out in #office-hours afterwards, if the other channels are too busy for you and you’re looking for a friendly home, you’re more than welcome to pull up a chair and hang out.
161
+
- Thanks to the following companies for supporting the community with developer
0 commit comments