profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/rajula96reddy/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.
Rajula Vineet Reddy rajula96reddy Geneva, Switzerland http://rajula96reddy.github.io/ Linux! Pharo! Kubernetes! IT Fellow @CERN, IIITB Alum '19, CERN Openlab Student '19, OMP Intern '18, GSoC '17

openmainframeproject-internship/LinuxOne_Kubernetes_SLES_Deployment_Documentation 2

Documentation on setting up Kubernetes under SLES on s390x. This work is a part of Open Mainframe Summer Internship 2018.

ClementMastin/clap-st 1

Command-line argument parsing for Pharo

nmdesai92/Projector_pi 1

Controlling Projector using Rpi

Alakazam03/ELK-Tutorial 0

Short setup for a demo visualization of apache-logs using logstash, kibana and elastic search

keerthivutla/ITDomains_Project 0

The Fun Begins !!!

openmainframeproject-internship/LinuxOne_Kubernetes_Canonical_Deployment_Documentation 0

Documentation on setting up Kubernetes under Ubuntu Linux 18.04 on s390x. This work is a part of Open Mainframe Summer Internship 2018.

rajula96reddy/2018-ESD_813-Real_Time_Operating_Systems 0

Assignments & other experimental work as a part of 2018-ESD 813-Real Time Operating Systems Course

rajula96reddy/Awesome-Linux-Software 0

🐧 A list of awesome applications, softwares, tools and other materials for Linux distros.

push eventrajula96reddy/website

Rajula Vineet Reddy

commit sha 0c643c00f9102937d593989699a8dbe9f309aaa5

1.22 feature blog for memory qos support

view details

push time in 4 days

Pull request review commentkubernetes/website

1.22 feature blog for alpha swap support

+---+layout: blog+title: 'New in Kubernetes v1.22: alpha support for using swap memory'+date: 2021-07-19

There were some minor changes, and the 1.21 comms team decided to move the date to 18th August. @ehashman will update the same here.

ehashman

comment created time in 4 days

PullRequestReviewEvent
MemberEvent

pull request commentkubernetes/website

[WIP] 1.22 feature blog for Node alpha swap support

Closing this. Since we are tracking the blog in a new PR https://github.com/kubernetes/website/pull/29060

rajula96reddy

comment created time in 6 days

PR closed kubernetes/website

Reviewers
[WIP] 1.22 feature blog for Node alpha swap support area/blog cncf-cla: yes language/en sig/docs size/XS

<!-- 🛈

Hello!

Remember to ADD A DESCRIPTION and delete this note before submitting your pull request. The description should explain what will change, and why.

PLEASE title the FIRST commit appropriately, so that if you squash all your commits into one, the combined commit message makes sense. For overall help on editing and submitting pull requests, visit: https://kubernetes.io/docs/contribute/start/#improve-existing-content

Use the default base branch, “main”, if you're documenting existing features in the English localization.

If you're working on a different localization (not English), see https://kubernetes.io/docs/contribute/new-content/overview/#choose-which-git-branch-to-use for advice.

If you're documenting a feature that will be part of a future release, see https://kubernetes.io/docs/contribute/new-content/new-features/ for advice.

--> Feature blog post for "Node Alpha swap support" (https://github.com/kubernetes/enhancements/issues/2400). This is part of the Kubernetes 1.22 release Feature blogs

Tentative publish date is 9th August 2021.

cc: @ehashman

Todo

  • [ ] Adjust publishing date
+6 -0

3 comments

1 changed file

rajula96reddy

pr closed time in 6 days

startediamadamdev/bypass-paywalls-firefox

started time in 6 days

MemberEvent

PR opened kubernetes/website

[WIP] 1.22 feature blog for Node alpha swap support

<!-- 🛈

Hello!

Remember to ADD A DESCRIPTION and delete this note before submitting your pull request. The description should explain what will change, and why.

PLEASE title the FIRST commit appropriately, so that if you squash all your commits into one, the combined commit message makes sense. For overall help on editing and submitting pull requests, visit: https://kubernetes.io/docs/contribute/start/#improve-existing-content

Use the default base branch, “main”, if you're documenting existing features in the English localization.

If you're working on a different localization (not English), see https://kubernetes.io/docs/contribute/new-content/overview/#choose-which-git-branch-to-use for advice.

If you're documenting a feature that will be part of a future release, see https://kubernetes.io/docs/contribute/new-content/new-features/ for advice.

--> Feature blog post for "Node Alpha swap support" (https://github.com/kubernetes/enhancements/issues/2400). This is part of the Kubernetes 1.22 release Feature blogs

Tentative publish date is 9th August 2021.

cc: @ehashman

Todo

  • [ ] Adjust publishing date
+6 -0

0 comment

1 changed file

pr created time in 13 days

create barnchrajula96reddy/website

branch : alpha-swap-support

created branch time in 13 days

PR opened kubernetes/website

[WIP] 1.22 feature blog for memory qos support with cgroups v2

<!-- 🛈

Hello!

Remember to ADD A DESCRIPTION and delete this note before submitting your pull request. The description should explain what will change, and why.

PLEASE title the FIRST commit appropriately, so that if you squash all your commits into one, the combined commit message makes sense. For overall help on editing and submitting pull requests, visit: https://kubernetes.io/docs/contribute/start/#improve-existing-content

Use the default base branch, “main”, if you're documenting existing features in the English localization.

If you're working on a different localization (not English), see https://kubernetes.io/docs/contribute/new-content/overview/#choose-which-git-branch-to-use for advice.

If you're documenting a feature that will be part of a future release, see https://kubernetes.io/docs/contribute/new-content/new-features/ for advice.

--> Feature blog post for "Support memory qos with cgroups v2" (https://github.com/kubernetes/enhancements/issues/2570). This is part of the Kubernetes 1.22 release Feature blogs

Tentative publish date is 08/18/21.

cc: @xiaoxubeii

Todo

  • [ ] Adjust publishing date
+73 -0

0 comment

1 changed file

pr created time in 13 days

create barnchrajula96reddy/website

branch : memory-qos

created branch time in 13 days

PR opened kubernetes/website

[WIP] [Placeholder] Add memory manager moves to beta feature blog post 1.22

<!-- 🛈

Hello!

Remember to ADD A DESCRIPTION and delete this note before submitting your pull request. The description should explain what will change, and why.

PLEASE title the FIRST commit appropriately, so that if you squash all your commits into one, the combined commit message makes sense. For overall help on editing and submitting pull requests, visit: https://kubernetes.io/docs/contribute/start/#improve-existing-content

Use the default base branch, “main”, if you're documenting existing features in the English localization.

If you're working on a different localization (not English), see https://kubernetes.io/docs/contribute/new-content/overview/#choose-which-git-branch-to-use for advice.

If you're documenting a feature that will be part of a future release, see https://kubernetes.io/docs/contribute/new-content/new-features/ for advice.

--> This adds the blog post about the Kubernetes Memory Manager beta feature.

This is part of the Kubernetes 1.22 release Feature blogs

CC: @cynepco3hahue

Todo

  • [ ] Adjust publishing date
+0 -0

0 comment

1 changed file

pr created time in 17 days

push eventrajula96reddy/website

Rajula Vineet Reddy

commit sha e8b26cced7fafb27e97f00945db7e0ce6577da5e

Add memory manager feature blog post

view details

push time in 17 days

push eventrajula96reddy/website

Vineet Reddy Rajula

commit sha 38fdf566fe8d11d2cf0313b6920b705137b93c60

Add memory manager feature blog post

view details

push time in 17 days

create barnchrajula96reddy/website

branch : memory-manager

created branch time in 17 days

fork rajula96reddy/website

Kubernetes website and documentation repo:

https://kubernetes.io

fork in 17 days

pull request commentkubernetes-sigs/contributor-tweets

Create 07-05-2021-first-tweet.tweet

Weird. Did it again?

I can the new changes now. The workflow is working. The tweet will go out once we merge this.

Just an FYI for future purposes: It is advised to not do a merge rebase if possible, it creates an additional commit. A normal rebase is preferred.

rainleander

comment created time in 24 days

pull request commentkubernetes-sigs/contributor-tweets

add: new tweet file via automation

yeah, that's right. The action is triggered by an event that is because of my activity. So yes.

Perfect. So, I guess when a user (who hasn't signed the CLA) creates an issue, it might cause an error.

github-actions[bot]

comment created time in 24 days

pull request commentkubernetes-sigs/contributor-tweets

add: new tweet file via automation

I see that prow retrieved you as the author, because you were the one who created the issue? So, in that case users need to sign the CLA as well to use this automation. Am I right?

github-actions[bot]

comment created time in 24 days

pull request commentkubernetes-sigs/contributor-tweets

add: new tweet file via automation

@gkarthiks Yay! Thanks a lot! :heart:

github-actions[bot]

comment created time in 24 days

pull request commentkubernetes-sigs/contributor-tweets

fix: default label set

/lgtm

gkarthiks

comment created time in 24 days

pull request commentkubernetes-sigs/contributor-tweets

Create 07-05-2021-first-tweet.tweet

Hey @rainleander Thanks for being patient. The workflow should be fixed now. Do you rebasing this PR on the latest master branch? Thanks!

Done!

Correct me if I am wrong, I don't see the rebase changes. Can you check again? https://github.com/rainleander/contributor-tweets/tree/patch-1 still says "This branch is 1 commit ahead, 13 commits behind kubernetes-sigs:master. "

rainleander

comment created time in 24 days

pull request commentkubernetes-sigs/contributor-tweets

fix: move label to kind/tweet

/lgtm

gkarthiks

comment created time in 24 days

pull request commentkubernetes-sigs/contributor-tweets

fix: move label to kind/tweet

@gkarthiks Thanks for the PR. I have one quick questions. Give we have prow to add or remove labels, I am not sure if we can add labels by default with the issue template. Do you know if it works?

In theory, this should work. Because prow is a tool for adding and removing labels. But the labels are part of the GitHub labels and the template is trying to add the labels from the same. So this should technically work. Let's check it out. What do you say? wink

Yeah I agree. Let's test it out.

gkarthiks

comment created time in 24 days

pull request commentkubernetes-sigs/contributor-tweets

fix: move label to kind/tweet

@gkarthiks Thanks for the PR. I have one quick questions. Give we have prow to add or remove labels, I am not sure if we can add labels by default with the issue template. Do you know if it works?

gkarthiks

comment created time in 24 days

issue closedkubernetes-sigs/contributor-tweets

Test: Creating a PR from a GH issue

Provide the actual tweet content between the commented colons <!-- Input your tweet content exactly between the commented colons --> <!--::--> Hello! This tweet is created from a GH issue, which was PRed automatically. <!--::-->

closed time in 24 days

rajula96reddy

push eventrajula96reddy/contributor-tweets

Rajula Vineet Reddy

commit sha 539c4dd4db00252cc9e3a1ea3e710c46e952f486

Add tweet about annual report

view details

push time in 25 days

create barnchrajula96reddy/contributor-tweets

branch : annual-report

created branch time in 25 days