profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/shubheksha/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Shubheksha shubheksha London, England https://shubheksha.com I love computers.

freeCodeCamp/how-to-contribute-to-open-source 5664

A guide to contributing to open source

shubheksha/companies-sponsoring-visas 823

A list of companies that sponsor employees from other countries.

shubheksha/kubernetes-internals 518

This is a collection of resources that shed light on the inner workings of Kubernetes

shubheksha/System-Design-Papers 148

A list of papers on system design.

shubheksha/Kubernetes-Up-and-Running-Notes 93

Notes from the book Kubernetes Up and Running

shubheksha/how-to-contribute-to-open-source 67

A guide to contributing to open source

shubheksha/drawings 4

A place for all my drawings and illustrations

shubheksha/library 4

A collection of the papers, conference talks, articles, blog posts, interesting Twitter threads, HN/reddit comments on systems engineering

shubheksha/infrastructure-conferences 3

A list of industry conferences focusing on infrastructure, distributed systems and related topics.

pull request commentkubernetes/kubernetes

update azure_deploymentclient log

/close

lovebaby979

comment created time in a month

pull request commentkubernetes/kubernetes

Structured Logging migration: migrate package pkg/volume/util/operationexecutor for structured logging

@sanwishe would you be able to take a look at this and rebase please?

sanwishe

comment created time in a month

pull request commentkubernetes/kubernetes

migrate cmd/cloud-controller-manager to structured logging

@CaoDonghui123 Would you be able to rebase this please?

CaoDonghui123

comment created time in a month

pull request commentkubernetes/kubernetes

migrate legacy-cloud-providers /azure/azure_controller_vmss.go logs to structured logging

Hi, only bug fixes are being accepted in-tree for cloud providers, so I'll have to close this PR. We'll clarify this further in the contributor guide. /close

lovebaby979

comment created time in a month

pull request commentkubernetes/kubernetes

migrate legacy-cloud-providers /azure/clients/vmssvmclient logs to structured logging

Hi, only bug fixes are being accepted in-tree for cloud providers, so I'll have to close this PR. We'll clarify this further in the contributor guide. /close

lovebaby979

comment created time in a month

pull request commentkubernetes/kubernetes

migrate volume/csi/csi_mounter.go logs into structured logging

@CKchen0726 are you still planning to work on this?

CKchen0726

comment created time in a month

issue commentkubernetes/kubernetes

Structed Logging migration: selecting component(s) for 1.23 cycle

/sig instrumentation /wg structured-logging

shubheksha

comment created time in a month

issue openedkubernetes/kubernetes

Structed Logging migration: selecting component(s) for 1.23 cycle

After successfully migrating Kubelet to the new structured logging format in 1.21, we spent 1.22 streamlining processes and forming the working group now spearheading the migration as a whole. For 1.23, we'd like to pick a new component to start migrating over the new format. This requires a partnership between the WG and the responsible SIG.

What WG structured logging will do:

  • Migration the code
  • Review the majority of the code
  • Hand it over to the respective SIG for final approval

What the SIG will do:

  • Final approval to make sure the PRs are merged in time
  • Time commitment: half a day a week (this is a rough estimate and might change in the future depending on various factors)

If your SIG has some spare bandwidth and can help with the migration, please comment below :)

cc: @dims / @serathius

created time in a month

pull request commentkubernetes/community

Document structured logging contribution process

/approve

yangjunmyfm192085

comment created time in 3 months

Pull request review commentkubernetes/community

Document structured logging contribution process

 should be applicable at later stages or for other projects using `klog` logging  [Structured Logging KEP]: https://github.com/kubernetes/enhancements/tree/master/keps/sig-instrumentation/1602-structured-logging +## How to contribute++### About the migration++We would like for the Kubernetes community to settle on one preferred log message structure, that will be enforced by new klog methods. The goal of the migration is to switch C like format string logs to structured logs with explicit metadata about parameters.++Migration within the structured logging working group happens in two different ways - organized & non-organized. ++With organized, milestone-based, large-scale migration we try to target deliverables for a specific Kubernetes release. A good example of such an effort is the migration of the entire Kubelet code in the [#1.21 release](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.21.md#structured-logging-in-kubelet) ++For non-organized migrations, the onus is, generally, on the individual contributors.++* Organized Migration++Organized migration is carried out in a two state cycle aligning with the cadence of Kubernetes releases. ++In the first stage, we pick a particular migration milestone & create an issue to split the work into smaller chunks (for example, migrating just a single file). This ensures that the work can be easily picked up by multiple individual contributors and also avoids conflicts. After the migration activity is complete, we mark the directory as migrated to avoid regressions with the help of tooling that we have developed. ++In the second milestone, we take a break from migration to analyze results & improve our existing processes. Adding structured information to logs is a very costly & time-consuming affair. Setting aside time in the second stage to collect feedback, analyze the impact of changes on the log volume & performance, and better our PR review process helps us avoid mistakes and duplicate efforts.++* Non-organized migration++As aforementioned, our non-organized migration efforts are spearheaded by individual contributors who require particular code sections to utilize new features early. 

I'd re-word this as follows:

As aforementioned, our non-organized migration efforts are spearheaded by individual contributors who need to migrate particular code sections to utilize new features early. 
yangjunmyfm192085

comment created time in 3 months

PullRequestReviewEvent
PullRequestReviewEvent

startedmiguelprofespanol/Espanol

started time in 3 months