profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/Jaanki/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.
Janki Chhatbar Jaanki @RedHatOfficial India www.simplyexplainedblog.wordpress.com Open source enthusiast, Python, @openstack, SDN, NFV, Docker

Jaanki/CI-CD 0

This repo explains setting up Jenkins server and building Python scripts

Jaanki/cloud-prepare 0

Go library to prepare your cloud infrastructure via API for submariner to work on top

Jaanki/coastguard 0

Controller to facilitate network policing on a multi-cluster connected environments (proof-of-concept state)

Jaanki/community-operators 0

The canonical source for Kubernetes Operators that appear on OperatorHub.io, OpenShift Container Platform and OKD.

Jaanki/console 0

The user interface for the cluster management portion of open-cluster-management.

Jaanki/get.submariner.io 0

Get submariner/subctl script

Jaanki/inpycon-blog 0

PyCon India Blog

Jaanki/integration-packaging-puppet-opendaylight 0

ODL-managed repository for the puppet-opendaylight.

PR opened submariner-io/releases

Enable PR dependency check jobs

This job marks a PR dependent whenever a dependent PR is mentioned via Depends on/ depends on keyword.

The job fails until the dependent PR is not merged. This helps in properly managing merging of dependent PRs.

Signed-off-by: Janki Chhatbar jchhatba@redhat.com

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

  1. If this is your first time, please read our developer guide: https://submariner.io/development/
  2. Ensure you have added the appropriate tests for your PR: https://submariner.io/development/code-review/#test-new-functionality
  3. Read the code review guide to ease the review process: https://submariner.io/development/code-review/
  4. If the PR is unfinished, mark it as a draft: https://submariner.io/development/code-review/#mark-work-in-progress-prs-as-drafts
  5. If you are using CI to debug, use your private fork: https://submariner.io/development/code-review/#use-private-forks-for-debugging-prs-by-running-ci
  6. Add labels to the PR as appropriate.

This template is based on the K8s/K8s template:

https://github.com/kubernetes/kubernetes/blob/master/.github/PULL_REQUEST_TEMPLATE.md -->

+39 -0

0 comment

1 changed file

pr created time in a day

create barnchJaanki/releases

branch : dependent_pr

created branch time in a day

fork Jaanki/releases

Submariner release process repository

fork in a day

push eventJaanki/submariner-website

Sridhar Gaddam

commit sha 6f1314904e4cd50be5ddbfcd4d3cde62471bdef7

Documentation for subctl cloud prepare and cleanup This PR includes the documentation for subctl cloud prepare/cleanup commands. It covers aws, gcp and generic clouds. Signed-Off-by: Sridhar Gaddam <sgaddam@redhat.com>

view details

Daniel Farrell

commit sha ed2aa184015f01edf54951c4632d3ce9e7fd6c25

Add automated troubleshooting documentation Document the standard process to use subctl to debug Submariner issues and collect information for getting help. This is becoming something we answer a lot, so it's good to have a pointer with a prepared answer. Signed-off-by: Daniel Farrell <dfarrell@redhat.com>

view details

Daniel Farrell

commit sha 46bd4a4eead849a7f5117646e285d3ad92ef3ec3

Clarify OpenShift AWS cloud-prepare docs Make it clear that infra_id and region are per-cluster, and need to be set for each invocation of subctl cloud prepare. Also use subctl --ocp-metadata for simplicity. Fixes: #594 Signed-off-by: Daniel Farrell <dfarrell@redhat.com>

view details

Janki Chhatbar

commit sha 4dccd48683572355ba6c40d5cc9b3e2163e0f52e

Merge branch 'devel' into 11rc0_rn

view details

push time in 3 days

PullRequestReviewEvent
PullRequestReviewEvent
PullRequestReviewEvent
PullRequestReviewEvent

pull request commentopen-cluster-management/submariner-addon

Enable golangci-lint stylecheck linter, fix errors

Also while you are at it, please do add staticcheck initialisations https://github.com/submariner-io/submariner-operator/commit/0af339a9e681b3431c93612d233290711fc41c43 in sync with submariner projects.

dfarrell07

comment created time in 5 days

Pull request review commentopen-cluster-management/submariner-addon

Enable golangci-lint stylecheck linter, fix errors

 type ManagedClusterInfo struct { 	Region string `json:"region,omitempty"` 	// InfraId represents the infrastructure id of the managed cluster. 	// +optional-	InfraId string `json:"infraId,omitempty"`+	InfraID string `json:"infraId,omitempty"`

This also can't be changed IMO. It would mean makjng API changes and non-backward compatibility,

dfarrell07

comment created time in 5 days

PullRequestReviewEvent
PullRequestReviewEvent
PullRequestReviewEvent

PR opened submariner-io/submariner-operator

Remove extra 'when'

Signed-Off-By: Janki Chhatbar jchhatba@redhat.com

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

  1. If this is your first time, please read our developer guide: https://submariner.io/development/
  2. Ensure you have added the appropriate tests for your PR: https://submariner.io/development/code-review/#test-new-functionality
  3. Read the code review guide to ease the review process: https://submariner.io/development/code-review/
  4. If the PR is unfinished, mark it as a draft: https://submariner.io/development/code-review/#mark-work-in-progress-prs-as-drafts
  5. If you are using CI to debug, use your private fork: https://submariner.io/development/code-review/#use-private-forks-for-debugging-prs-by-running-ci
  6. Add labels to the PR as appropriate.

This template is based on the K8s/K8s template:

https://github.com/kubernetes/kubernetes/blob/master/.github/PULL_REQUEST_TEMPLATE.md -->

+12 -12

0 comment

1 changed file

pr created time in 5 days

create barnchJaanki/submariner-operator

branch : twice_when

created branch time in 5 days

delete branch Jaanki/console

delete branch : release-2.3

delete time in 5 days

push eventJaanki/submariner-addon

Jaanki

commit sha 23a93f9f5c904ccdcffa44b6823a011287edf385

Use latest Submariner in KIND setup Signed-Off-By: Janki Chhatbar <jchhatba@redhat.com>

view details

push time in 5 days

PullRequestReviewEvent

push eventJaanki/submariner-operator

Jaanki

commit sha 351d8dd5aab39e2cd81006a2eb4fdc366b9f725b

Use go:embed instead of go:generate Signed-Off-By: Janki Chhatbar <jchhatba@redhat.com>

view details

push time in 6 days

pull request commentsubmariner-io/submariner-operator

Use go:embed instead of go:generate

It was supposed to be a draft :)

Jaanki

comment created time in 6 days

PullRequestReviewEvent

Pull request review commentopen-cluster-management/submariner-addon

Use latest Submariner in KIND setup

 spec: EOF      submrepo="quay.io/submariner"-    submver="0.9.1"+    submver=$(curl -s https://github.com/submariner-io/submariner/releases/latest | grep -Po '(?<=tag/v)[^"]+')

That gives version 0.11.0-rc0. I guess the next question is do we want to use latest release or latest major release eg. 0.10.0 in this case.

Another problem with this would be when 0.10.1 is release after 0.11.0, this curl will get 0.10.1 as latest release which we don't want.

Jaanki

comment created time in 6 days

pull request commentopen-cluster-management/submariner-addon

Use latest Submariner in KIND setup

cc @skitt @tpantelis @sridhargaddam @dfarrell07

Jaanki

comment created time in 8 days

pull request commentopen-cluster-management/submariner-addon

Use latest Submariner in KIND setup

/assign @Jaanki

Jaanki

comment created time in 8 days

create barnchJaanki/submariner-addon

branch : use_latest_subm

created branch time in 8 days

PullRequestReviewEvent
PullRequestReviewEvent
PullRequestReviewEvent