profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/ramaboggarapu/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.
Ramakrishna Boggarapu ramaboggarapu IBM

ramaboggarapu/kube-sample-daemonset 0

Sample to show how to create a daemonset to automatically apply a change to worker nodes

ramaboggarapu/my-node-app 0

Application to test ibm-cloud-solutions Hubots

ramaboggarapu/node-sdk 0

:steam_locomotive: Node.js library to access IBM Watson services.

ramaboggarapu/nodejs-buildpack 0

Cloud Foundry buildpack for Node.js

ramaboggarapu/nodejs-cloudant 0

Sample Node.js application which uses Bluemix Cloudant NoSQL service

ramaboggarapu/prometheus 0

The Prometheus monitoring system and time series database.

pull request commentkubernetes/community

adding question

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: <a href="https://github.com/kubernetes/community/pull/5771#" title="Author self-approved">rficcaglia</a> To complete the pull request process, please assign iancoldwater after the PR has been reviewed. You can assign the PR to them by writing /assign @iancoldwater in a comment when ready.

The full list of commands accepted by this bot can be found here.

<details open> Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment </details> <!-- META={"approvers":["iancoldwater"]} -->

rficcaglia

comment created time in 2 hours

PR opened kubernetes/community

adding question

and answer after slack discussion 5/7

<!-- Thanks for sending a pull request! Here are some tips for you:

  • If this is your first contribution, read our Getting Started guide https://github.com/kubernetes/community/blob/master/contributors/guide/README.md
  • If you are editing SIG information, please follow these instructions: https://git.k8s.io/community/generator You will need to follow these steps:
    1. Edit sigs.yaml with your change
    2. Generate docs with make generate. To build docs for one sig, run make WHAT=sig-apps generate -->

Which issue(s) this PR fixes: <!-- Automatically closes linked issue when PR is merged. Usage: Fixes #<issue number>, or Fixes (paste link of issue). If PR is about failing-tests or flakes, please post the related issues/tests in a comment and do not use Fixes --> Fixes #

+6 -0

0 comment

1 changed file

pr created time in 2 hours

issue commentkubernetes/community

Clarify social media guidelines regarding boosting of non Kubernetes/CNCF events

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale

mrbobbytables

comment created time in 4 hours

pull request commentkubernetes/community

Update README.md

@caseydavenport one last lgtm needed ! :)

jayunit100

comment created time in a day

pull request commentkubernetes/community

Add co-chair Gaby to doc

@tashimi ack, will round up approvals early next week

tashimi

comment created time in a day

pull request commentkubernetes/community

Add co-chair Gaby to doc

@kubernetes/steering-committee : can you please approve this now, the checklist has been adhered to and we should be good to go.

tashimi

comment created time in a day

pull request commentkubernetes/community

Initial template for SIG Cloud Provider 2020 Annual Report

@nikhita Can we remove the hold?

cheftako

comment created time in a day

Pull request review commentkubernetes/community

Add charter for WG Structured Logging

+# WG Structured Logging Charter++This charter adheres to the conventions described in the [Kubernetes Charter README]+and uses the Roles and Organization Management outlined in [sig-governance].++[sig-governance]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md+[Kubernetes Charter README]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/README.md++## Scope++Modernize logging in Kubernetes core components, allowing users to efficiently consume, process, store and analyse +information stored in logs.++### In Scope++- Define the standard for logging - propose libraries, interfaces, metadata schema+- Reduce friction for using logging - reduce dependencies and performance overhead+- Give more choice over logging - allow pluggable logging implementation+- Ensure quality consistent logging - overview migration, create documentation, tooling and educate reviewers+- Prevent regressions caused by logging - measure performance overhead and log volume changes++For all of the above, we will focus on core Kubernetes components and addons.+Other SIG subprojects/components (e.g. SIG Scheduling descheduler) are out of+scope.++### Out of scope++- Logging of non-core Kubernetes components++## Stakeholders++Stakeholders in this working group span multiple SIGs that own parts of +the code in core Kubernetes components and addons.++  - API Machinery+  - Architecture+  - Cloud Provider+  - Instrumentation

we are not focusing on CLI?

serathius

comment created time in a day

pull request commentkubernetes/community

Initial template for SIG Cloud Provider 2020 Annual Report

Keywords which can automatically close issues and at(@) or hashtag(#) mentions are not allowed in commit messages.

The list of commits with invalid commit messages:

  • 48de733 SIG Cloud Provider 2020 Annual Report

<details>

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. </details>

cheftako

comment created time in a day

pull request commentkubernetes/community

Add dims as liaison for the new WG structured logging

/hold for reviews

dims

comment created time in a day

pull request commentkubernetes/community

Update README.md

@jayunit100: The following test failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
pull-community-verify d8af0622c86f92647fbc62f7b5abd0486d861130 link /test pull-community-verify

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

<details>

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. </details> <!-- test report -->

jayunit100

comment created time in a day

pull request commentkubernetes/community

Update README.md

New changes are detected. LGTM label has been removed.

jayunit100

comment created time in a day

Pull request review commentkubernetes/community

clarifying schema for multi-kind object references

 clearly described and the permissions issues should be resolved. This could be done with a double opt-in (an opt-in from both the referrer and the refer-ee) or with secondary permissions checks performed in admission.  -TODO: Plugins, extensions, nested kinds, headers+TODO: Plugins, extensions, headers +### Handling references to multiple kinds++References which can refer to multiple kinds should use a single field, and select the target kind via `apiVersion` and `kind` fields.++For example, if one can retrieving a referenced value from a `ConfigMap` or a `Secret` kind, the schema for the reference should be of the form:++```yaml+# preferred pattern+valueFrom:+  kind: Secret  # alternatively ConfigMap

David was mentioning he's seen a lot of other examples in openshift.

Further examples up here https://github.com/kubernetes/community/pull/5748/files#r628142544

toumorokoshi

comment created time in 2 days

Pull request review commentkubernetes/community

clarifying schema for multi-kind object references

 clearly described and the permissions issues should be resolved. This could be done with a double opt-in (an opt-in from both the referrer and the refer-ee) or with secondary permissions checks performed in admission.  -TODO: Plugins, extensions, nested kinds, headers+TODO: Plugins, extensions, headers +### Handling references to multiple kinds++References which can refer to multiple kinds should use a single field, and select the target kind via `apiVersion` and `kind` fields.

@deads2k can you explain what scenario results in a (group, kind, version) resolving to multiple resources? From what I can tell CRDs are uniquely identified by either "kind" or "plural" fields.

A common case is AdmissionReview.v1.admission.k8s.io. One easy way to get authentication for your admission webhook for free is it add it as an aggregated apiserver, then reference the kube-apiserver as the source. This way every client can sent serviceaccount tokens automatically for authentication. In some clusters, that kind can reference multiple resources.

Another example is SubjectAccessReview.v1.authorization.k8s.io for different kinds of webhook authorizers. Also TokenReview.v1.authorization.k8s.io.

The same apimachinery capability is used to enable Scale.v1.autoscaling to work against multiple subresource endpoints.

We also used it for Binding.v1. against /binding and pods/binding.

Just because you don't often see examples, doesn't mean they don't exist. Library code, APIs, and the architectural recommendations should reflect what the system is designed and used to do. In this case, kind has ambiguous mappings to resources and URLs. Using resource will eliminate this ambiguity.

toumorokoshi

comment created time in 2 days

pull request commentkubernetes/community

Add dims as liaison for the new WG structured logging

LGTM, Looking forward to working together. /cc @shubheksha

dims

comment created time in 2 days

pull request commentkubernetes/community

Add charter for WG Structured Logging

@serathius: The following test failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
pull-community-verify 59f570d7fc1609150f7e00cc6cd8c0786a8c45eb link /test pull-community-verify

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

<details>

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. </details> <!-- test report -->

serathius

comment created time in 2 days

pull request commentkubernetes/community

Add charter for WG Structured Logging

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: <a href="https://github.com/kubernetes/community/pull/5770#" title="Author self-approved">serathius</a> To complete the pull request process, please assign liggitt after the PR has been reviewed. You can assign the PR to them by writing /assign @liggitt in a comment when ready.

The full list of commands accepted by this bot can be found here.

<details open> Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment </details> <!-- META={"approvers":["liggitt"]} -->

serathius

comment created time in 2 days

PR opened kubernetes/community

Add charter for WG Structured Logging

/cc @dims @shubheksha @thockin @kubernetes/steering-committee

+71 -0

0 comment

2 changed files

pr created time in 2 days

pull request commentkubernetes/community

Add dims as liaison for the new WG structured logging

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: <a href="https://github.com/kubernetes/community/pull/5769#" title="Author self-approved">dims</a>

The full list of commands accepted by this bot can be found here.

The pull request process is described here

<details > Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment </details> <!-- META={"approvers":[]} -->

dims

comment created time in 2 days

PR opened kubernetes/community

Add dims as liaison for the new WG structured logging

Signed-off-by: Davanum Srinivas davanum@gmail.com

<!-- Thanks for sending a pull request! Here are some tips for you:

  • If this is your first contribution, read our Getting Started guide https://github.com/kubernetes/community/blob/master/contributors/guide/README.md
  • If you are editing SIG information, please follow these instructions: https://git.k8s.io/community/generator You will need to follow these steps:
    1. Edit sigs.yaml with your change
    2. Generate docs with make generate. To build docs for one sig, run make WHAT=sig-apps generate -->

Which issue(s) this PR fixes: <!-- Automatically closes linked issue when PR is merged. Usage: Fixes #<issue number>, or Fixes (paste link of issue). If PR is about failing-tests or flakes, please post the related issues/tests in a comment and do not use Fixes --> Fixes #

+5 -0

0 comment

3 changed files

pr created time in 2 days

pull request commentkubernetes/community

Psc rename

@lukehinds: PR needs rebase.

<details>

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. </details>

lukehinds

comment created time in 2 days

push eventkubernetes/community

Aeva Black

commit sha d185c5f2dba087f7b0bebee898583509ad4ee0f3

Update the CoC readme and process docs This updates wording in a few sections of our new incident-process docs, adds a link to our new Slack channel in the README, and adds some descriptions and a link to the incident-process doc to the README. Signed-off-by: Aeva Black <806320+AevaOnline@users.noreply.github.com>

view details

Kubernetes Prow Robot

commit sha bb99ed28bcd449acaa6e55cc890d188999955824

Merge pull request #5767 from AevaOnline/update-conduct-readme Update the CoC readme and process docs

view details

push time in 2 days

PR merged kubernetes/community

Reviewers
Update the CoC readme and process docs approved cncf-cla: yes lgtm size/M

This updates wording in a few sections of our new incident-process docs, adds a link to our new Slack channel in the README, and adds some descriptions and a link to the incident-process doc to the README.

Signed-off-by: Aeva Black 806320+AevaOnline@users.noreply.github.com

+43 -22

5 comments

4 changed files

AevaOnline

pr closed time in 2 days

pull request commentkubernetes/community

Update the CoC readme and process docs

/lgtm

AevaOnline

comment created time in 2 days

issue commentkubernetes/community

Missing documentation license

@mrbobbytables according to some interpretations Apache License 2.0 is a code license, this is why the documentation usually is licensed with a different license, like CC BY 4.0. The CNCF Charter also suggests this way.

CsatariGergely

comment created time in 2 days

issue commentkubernetes/community

Repurpose fejta-bot + k8s-ci-robot to ping-bot

The ping-bot could also collect public stats about most missing issues, most annoying notifications and the longest waited features.

abitrolly

comment created time in 2 days

issue commentkubernetes/community

Repurpose fejta-bot + k8s-ci-robot to ping-bot

/remove-lifecycle stale

abitrolly

comment created time in 2 days

issue commentkubernetes/community

Repurpose fejta-bot + k8s-ci-robot to ping-bot

A few weeks ago, I got the feedback that I should never use frozen on tickets, so I'm confused, and still support the ping alternative.

abitrolly

comment created time in 2 days

Pull request review commentkubernetes/community

Initial template for SIG Cloud Provider 2020 Annual Report

+# 2020 - SIG Cloud Provider - Community Meeting Annual Reports+---+## Operational+**How are you doing with operational tasks in sig-governance.md?**++**Is your README accurate? have a CONTRIBUTING.md file?**++Our README is accurate but we do not currently have a contributing.md file.++**All subprojects correctly mapped and listed in [sigs.yaml](https://github.com/kubernetes/community/blob/master/sigs.yaml)?**++I believe so.++**What’s your meeting culture? Large/small, active/quiet, learnings? Meeting notes up to date? Are you keeping recordings up to date/trends in community members watching recordings?**++Our meetings tends to be small and quiet. We try to keep the meeting notes upto date during the meeting. ++**How does the group get updates, reports, or feedback from subprojects? Are there any springing up or being retired? Are OWNERS files up to date in these areas?**+_Same question as above but for working groups._++We go ove the sub project updates during our primary biweekly meeting. +I believe the OWNERS files are all upto date.

Happy to!

cheftako

comment created time in 2 days

issue commentkubernetes/community

Repurpose fejta-bot + k8s-ci-robot to ping-bot

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale

abitrolly

comment created time in 2 days