# Contributors Awards Ceremony Playbook awards/ README.md -- list of everyone playbook.md Kubernetes has a tradition of yearly peer awards. These are commonly handed out during the end-of-year Contributor Summit. The CNCF typically has awards as part of KubeCon + CloudNativeCon, the Kubernetes awards are a compliment to those, and are meant to be peer awards. ## Ideals and Values Typically each SIG will nominate two(2) recipients for an award. Ultimately the individual SIGs are responsible for their award nominations, in certain cases there may be an example of excellent work that requires more than two awards, co-chairs should use their judgement to determine if this is the case. Here are a few suggestions or ideas that make for a good award nominee: - Contributions to the project - Should consider contributions to the SIG and to upstream Kubernetes - Many contributors work on other projects, these awards are specific to Kubernetes itself - In some cases a top-level CNCF award nomination might be more appropriate - Should consider contributions to other SIGs, especially cross-SIG collaboration - Should consider large multi-cycle work that encompasses multiple releases - Kubernetes Values - Is the person exemplifying the Kubernetes values? - Remember that non-code contributions are important! - Community Input - Leads should take input from other SIG members, larger SIGs might consider mentioning the awards ahead of time to allow members to communicate nominations to leads. - Celebrate the Individuals as people - Awards are affiliation-free and earned by individuals, we do not mention vendors at all as part of this process - Vendors are encouraged to celebrate individuals via their own social properties, the awards themselves will remain neutral - Spread the Wealth - Should consider lookin at underserved areas of the project - For every "rock star" there's probably a few people quietly doing excellent work. - Should consider past awards, having the same person winning the award repeatedly shouldn't be the norm. ## Process ### Coordinating with the CNCF Typically a representative from the CNCF will be assigned to assist with the awards. Payment of the vendor MUST happen through the CNCF, do NOT pay for community awards with your work credit card, keep the awards affiliation free. Coordinate with the CNCF to determine the budget to ensure that the awards fit within it. Shipping costs and other fees like customs, etc. might be taken into account so it's important to set this goal first before proceeding. The CNCF will also help brainstorm awards and recommend vendors, if you need it. Generally speaking we try to come up with something creative and unique. ### Determining the Award Our community is clever and unconventional, the awards should be classy, but quirky. The awards should also be a "surprise" when unveiled, discussion about the awards are done publically as part of SIG Contributor Experience. The contributor summit subproject owners will determine how best to keep this open secret, usually leaving out the award specifics from the meeting notes or meeting recordingss are enough to keep it fun and a surprise. Here are some examples of past awards: ### Choosing a Vendor Vendors are important! Our community is spread all over the world, so when choosing a vendor consider if they can ship to where our contributors are, not just the US and EU. ### Checklist - [ ] Contributor Summit Planning Begins - [ ] Event Team should assign someone as the Awards Lead and one or two shadows - [ ] Awards Team determines what kind of award for that Contributor Summit - [ ] Awards team should plan for 3 weeks of vendor research - [ ] Once an Award has been selected, the vendor needs to be approved by the CNCF Representative - [ ] Can they ship to the countries we need? - [ ] Do they accept our payment options? - [ ] Ideally the vendor can handle accepting a planning spreadsheet from us so they can produce the awards. - [ ] Customs considerations - [ ] Other things Deb looks for go here - [ ] Create an Awards Spreadsheet - [ ] With the Kubernetes Gsuite Account - [ ] Only the Awards team, the CNCF Representative, the lead of the Contributor Summit Planning, and SIG Contributor Experience should have access to this sheet. - [ ] Awards Nomination should be announced to the SIG Chairs/TLs via their normal channels. - [ ] Awards team collects nominations from the SIGs and fills out the tracking sheet. - [ ] Name, Address, Phone number, github handle, email - Vendors will usually need more info depending on customs - [ ] CNCF Representative proofs and ensures the sheet has all the fields/information that the vendor requires. - [ ] Do not assume that nominators, coworkers, etc. have spelled submissions correctly, you need to double check each name and address, having to redo an award because of a typo can get expensive. - [ ] Coordinate with the Marketing Team - [ ] Awards tweets for the ceremony - [ ] Awards tweets for the winners - [ ] Blog post announcing the winners, and linking to the contributor site page - [ ] Amplify awardee social media posts when they post pics of their awards, thanking people, etc. ### Awards Ceremony The Awards Ceremony is typically done as part of the Contributor Summit. There may be cases where the ceremony is seperate or virtual, here are some tips: - Ceremony should be fun, but taken seriously. - Awards team should either be the hosts or select someone appropriate to be the hosts. - The ceremony is all about the awardees and celebrating their achievements. - [link to last one] - Ceremony should be easy to share and easy for other contributors to celebrate. - Pregenerate tweets so people can share. - Try to mention names and github/twitter/social handles so that it's easier for the audience to share - (This should be rewritten so it doesn't sound so partisan but whatever, jorge) - If you have time find tell one of their coworkers in the project so that their employer knows that they're getting an award, we want companies to celebrate and reward when their employees do awesome things. Get them in on the secret. :D - During actual Contributor Summits - It might be more efficient for the team to bring one example of the award from the vendor to show as part of the ceremony instead of bringing all the awards to the event! - Consider awardee's travel luggage, in many cases drop shipping will be much easier and cheaper. - Virtual Contributor Summits - Usually a picture of the award is sufficient and then drop ship the rest. - Awardees should be made aware of logistics - The awards are given during the time right up to the end of year holidays, shipping after the holidays is usually easier, awardees should be given a general idea of when the award ships.
Last changed by  
 
Kubernetes
Production grade container orchestration, made with love

Read more

Lessons Learned from 3 years of Kubernetes Office Hours

Date: 23 August 2020 Authors: Jorge Castro (VMware), Josh Berkus (Red Hat), Chris Carty (Google), Dan "POP" Papandrea (Sysdig), David McKay (Equinix Metal) Today we celebrate three years of the Kubernetes Office Hours. This is a monthly event where we take a panel of volunteers, stick them on a live stream, and then see how many questions we can field from the community. I started the show for one reason. I had recently started my Kubernetes journey and was learning all these new concepts while rewiring my traditional sysadmin brain to be more cloud native. So the idea was if I'm going to dig into this stuff and bother my new coworkers with silly questions, we might as well do it together and on the air to share our experiences and do it in a way that is fun and useful for others. Give away some tshirts, fame and fortune would surely follow. After 65 episodes we've decided to take a look at some of the more common problem areas that we've been tackling, and put together a quick summary for you on things where you might want to invest your attention. You will find many articles on "Top X things to know about Kubernetes". We've specifically avoided those and went back into our archives because what people think you need to know and what you actually need to know can be different.

3/18/2021
Office Hours Feb 2021

EU Edition Panelists Person: Andrew Question: We're writing a controller with controller-runtime, and trying to use the Generation/ObservedGeneration pattern to avoid reconciling if there isn't any change (not using the predicate provided by controller-runtime for that purpose yet though). My question is how can that work with the possibility of a stale cache? When we write the ObservedGeneration to the Status of our CR, it triggers another reconcile immediately, but in some cases, the cache is stale and the CR it "Get"s still has the old Status, and therefore the old ObservedGeneration. What is the recommended strategy of dealing with this? Thanks! Person: Simone Baracchi Question: I'd like to configure my small cluster as "highly available" with no single master / single point of failure and make the best use of all the cluster resources. My current plan is to make 3 nodes run as masters and be able to schedule pods on the masters. From my research the issues in doing so are 1) security issues about sensitive data on master which could be read from malicious pods and 2) pods competing for resources (especially in case of a node failure). I'm not too concerned about security atm, and I can think of limiting the max number of pods / resources used. Is there any other red flag in doing so? Person: Jesper Berg Axelsen

2/17/2021
Office Hours January 2021

EU Edition Panelists Rachel Leekin, Chris Carty, Dan POP Papandrea, Saiyam Pathak Person: Mostafa Elmenbawy (https://kubernetes.slack.com/archives/C6RFQ3T5H/p1609991530274100?thread_ts=1607960423.257700&cid=C6RFQ3T5H) Question: What is recommended for on premise production cluster spanning multiple hosts? Answer:

1/20/2021
To CNFC Maintainers

(TODO: We need a derived version appropriate to send to cncf-maintainers list) Sub: You're invited to the Kubernetes Contributor Celebration in one week! TL;DR we would love to have fellow cloud native contributors to join in the fun. Register now to be the first to join our Discord and we'll see you next week! https://forms.gle/51tqQgxuHxLaeU1P8 The Kubernetes community would normally celebrate this year by meeting in person, and that's not in the cards for us. So we decided to throw something fun online. With a change of venue, and with a lack of physical room limitations there’s no reason we can’t grow this to include all our friends and family! All we ask is that you register for logistical purposes. Here's the overview:

12/4/2020
Read more from Kubernetes
Published on HackMD