Office Hours is a live stream where we answer live questions about Kubernetes from users on the YouTube channel. 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.
Third Wednesday of every month, there are two sessions:
Tune into the Kubernetes YouTube Channel to follow along.
You can post questions on the #office-hours channel on Slack, or if you like you can submit your question to Stack Overflow and have us take a look.
If you submit a SO question we can prepare ahead of time and check important details.
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 SO question we answer.
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. We keep a backlog of open questions in the meeting notes.
The hosts will do a shout out of thanks to the current leaderboard of SO answerers each meeting so the people helping answer questions can get some recognition.
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:
Developer/Contributor questions: This event is for end users and operators, there is a separate livestream called Meet our Contributors where you can ask questions about getting started contributing, participating in peer reviews, and other development topics.
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.
Let’s try to not just dismiss bad questions outright, but use it as an opportunity for the answer to be a teaching tool as opposed to just answering “It’s in /var/log/foo, next question.” If the question is about logging then the developers might as well share their experiences in that area, recommend tools, share an anecdote, things of that nature.
Archives of all the sessions are kept here:
We’re always looking for volunteers to host and answer questions. Volunteers looking to host hours in more time zones are also welcome to join in and help us expand.
If you have any questions ping @castrojo.