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

submariner-io/shipyard 14

E2E testing framework and general scripts to create multiple K8s clusters with kind (K8s in Docker) for local E2E testing and development.

dfarrell07/submariner 0

Connect all your Kubernetes clusters, no matter where they are in the world.

mkolesnik/actions-and-branch-playground 0

Testing actions and branch management for stacked PRs

mkolesnik/admiral 0

Admiral is the submariner API for integration with federation systems

mkolesnik/cloud-prepare 0

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

mkolesnik/duplicati 0

Store securely encrypted backups in the cloud!

mkolesnik/get.submariner.io 0

Get submariner/subctl script

mkolesnik/go-auto-yt 0

Development repository for GoAutoYT

mkolesnik/lighthouse 0

Controller to facilitate DNS discovery between clusters (proof of concept state)

mkolesnik/networking-odl 0

Neutron drivers for OpenDaylight.

push eventsubmariner-io/releases

Mike Kolesnik

commit sha 6c2dfcf05cf389e9c88b27bd952f2cefe36ffd6f

Advancing 0.11.0-rc2 release to status: released Signed-off-by: Mike Kolesnik <mkolesni@redhat.com>

view details

push time in a day

PR merged submariner-io/releases

Reviewers
Advancing 0.11.0-rc2 release to status: released

Advancing 0.11.0-rc2 release to status: released

+3 -1

1 comment

1 changed file

mkolesnik

pr closed time in a day

PR opened submariner-io/releases

Advancing 0.11.0-rc2 release to status: released

Advancing 0.11.0-rc2 release to status: released

+3 -1

0 comment

1 changed file

pr created time in a day

push eventsubmariner-io/releases

Mike Kolesnik

commit sha 5107a29da554c4591b0030e798dcc794b0a4bf11

Advancing 0.11.0-rc2 release to status: projects Signed-off-by: Mike Kolesnik <mkolesni@redhat.com>

view details

Mike Kolesnik

commit sha ba4e91da7cbb34f177e1cabcd57e47147839571b

Advancing 0.11.0-rc2 release to status: released Signed-off-by: Mike Kolesnik <mkolesni@redhat.com>

view details

push time in a day

delete branch submariner-io/submariner-operator

delete branch : z_pr1379/skitt/compare-crds-only

delete time in a day

delete branch submariner-io/submariner-operator

delete branch : z_pr1365/Jaanki/show_networks

delete time in a day

delete branch submariner-io/submariner-operator

delete branch : z_pr1400/skitt/golang-embed

delete time in a day

PullRequestReviewEvent

push eventsubmariner-io/releases

Mike Kolesnik

commit sha 5107a29da554c4591b0030e798dcc794b0a4bf11

Advancing 0.11.0-rc2 release to status: projects Signed-off-by: Mike Kolesnik <mkolesni@redhat.com>

view details

push time in a day

PR merged submariner-io/releases

Reviewers
Advancing 0.11.0-rc2 release to status: projects

Advancing 0.11.0-rc2 release to status: projects

+4 -1

1 comment

1 changed file

mkolesnik

pr closed time in a day

push eventsubmariner-io/releases

Mike Kolesnik

commit sha 55633eba5dacd12fd848172675c3e0b66bf83540

Advancing 0.11.0-rc2 release to status: admiral Signed-off-by: Mike Kolesnik <mkolesni@redhat.com>

view details

Mike Kolesnik

commit sha 20236e11dcef5f20554f8d2bbb3ef10e9e1b65a7

Advancing 0.11.0-rc2 release to status: projects Signed-off-by: Mike Kolesnik <mkolesni@redhat.com>

view details

push time in 2 days

PR opened submariner-io/releases

Advancing 0.11.0-rc2 release to status: projects

Advancing 0.11.0-rc2 release to status: projects

+4 -1

0 comment

1 changed file

pr created time in 2 days

PR merged submariner-io/releases

Reviewers
Advancing 0.11.0-rc2 release to status: admiral

Advancing 0.11.0-rc2 release to status: admiral

+2 -1

1 comment

1 changed file

mkolesnik

pr closed time in 2 days

push eventsubmariner-io/releases

Mike Kolesnik

commit sha 55633eba5dacd12fd848172675c3e0b66bf83540

Advancing 0.11.0-rc2 release to status: admiral Signed-off-by: Mike Kolesnik <mkolesni@redhat.com>

view details

push time in 2 days

PR opened submariner-io/releases

Advancing 0.11.0-rc2 release to status: admiral

Advancing 0.11.0-rc2 release to status: admiral

+2 -1

0 comment

1 changed file

pr created time in 2 days

push eventsubmariner-io/releases

Mike Kolesnik

commit sha b11e4a9ba85fe0ac89473b8fb2dbf0e84b33a42e

Advancing 0.11.0-rc2 release to status: shipyard Signed-off-by: Mike Kolesnik <mkolesni@redhat.com>

view details

Mike Kolesnik

commit sha 4db376e2483035f43032355ccf8f48e00ab7797c

Advancing 0.11.0-rc2 release to status: admiral Signed-off-by: Mike Kolesnik <mkolesni@redhat.com>

view details

push time in 2 days

PR opened submariner-io/shipyard

Rename job so it won't shard on stable branches

Right now auto release logic updates devel to the stable branch name when creating stable branches. This leads to this job "sharding" into multiple jobs, and messes up branch protections.

To keep things simple, the main job name will remain the same so that there's no "PR targets X" and "PR targets Y" jobs, just the one "PR targets branch" job

Signed-off-by: Mike Kolesnik mkolesni@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 -->

+2 -2

0 comment

1 changed file

pr created time in 2 days

PR opened submariner-io/submariner

Rename job so it won't shard on stable branches

Right now auto release logic updates devel to the stable branch name when creating stable branches. This leads to this job "sharding" into multiple jobs, and messes up branch protections.

To keep things simple, the main job name will remain the same so that there's no "PR targets X" and "PR targets Y" jobs, just the one "PR targets branch" job

Signed-off-by: Mike Kolesnik mkolesni@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 -->

+2 -2

0 comment

1 changed file

pr created time in 2 days

PR opened submariner-io/cloud-prepare

Rename job so it won't shard on stable branches

Right now auto release logic updates devel to the stable branch name when creating stable branches. This leads to this job "sharding" into multiple jobs, and messes up branch protections.

To keep things simple, the main job name will remain the same so that there's no "PR targets X" and "PR targets Y" jobs, just the one "PR targets branch" job

Signed-off-by: Mike Kolesnik mkolesni@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 -->

+2 -2

0 comment

1 changed file

pr created time in 2 days

PR opened submariner-io/lighthouse

Rename job so it won't shard on stable branches

Right now auto release logic updates devel to the stable branch name when creating stable branches. This leads to this job "sharding" into multiple jobs, and messes up branch protections.

To keep things simple, the main job name will remain the same so that there's no "PR targets X" and "PR targets Y" jobs, just the one "PR targets branch" job

Signed-off-by: Mike Kolesnik mkolesni@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 -->

+2 -2

0 comment

1 changed file

pr created time in 2 days

PR opened submariner-io/submariner-operator

Rename job so it won't shard on stable branches

Right now auto release logic updates devel to the stable branch name when creating stable branches. This leads to this job "sharding" into multiple jobs, and messes up branch protections.

To keep things simple, the main job name will remain the same so that there's no "PR targets X" and "PR targets Y" jobs, just the one "PR targets branch" job

Signed-off-by: Mike Kolesnik mkolesni@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 -->

+2 -2

0 comment

1 changed file

pr created time in 2 days

PR opened submariner-io/submariner-website

Rename job so it won't shard on stable branches

Right now auto release logic updates devel to the stable branch name when creating stable branches. This leads to this job "sharding" into multiple jobs, and messes up branch protections.

To keep things simple, the main job name will remain the same so that there's no "PR targets X" and "PR targets Y" jobs, just the one "PR targets branch" job

Signed-off-by: Mike Kolesnik mkolesni@redhat.com

+2 -2

0 comment

1 changed file

pr created time in 2 days

PR opened submariner-io/admiral

Rename job so it won't shard on stable branches

Right now auto release logic updates devel to the stable branch name when creating stable branches. This leads to this job "sharding" into multiple jobs, and messes up branch protections.

To keep things simple, the main job name will remain the same so that there's no "PR targets X" and "PR targets Y" jobs, just the one "PR targets branch" job

Signed-off-by: Mike Kolesnik mkolesni@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 -->

+2 -2

0 comment

1 changed file

pr created time in 2 days

PR opened submariner-io/releases

Rename job so it won't shard on stable branches

Right now auto release logic updates devel to the stable branch name when creating stable branches. This leads to this job "sharding" into multiple jobs, and messes up branch protections.

To keep things simple, the main job name will remain the same so that there's no "PR targets X" and "PR targets Y" jobs, just the one "PR targets branch" job

Signed-off-by: Mike Kolesnik mkolesni@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 -->

+2 -2

0 comment

1 changed file

pr created time in 2 days

PR opened submariner-io/get.submariner.io

Rename job so it won't shard on stable branches

Right now auto release logic updates devel to the stable branch name when creating stable branches. This leads to this job "sharding" into multiple jobs, and messes up branch protections.

To keep things simple, the main job name will remain the same so that there's no "PR targets X" and "PR targets Y" jobs, just the one "PR targets branch" job

Signed-off-by: Mike Kolesnik mkolesni@redhat.com

+2 -2

0 comment

1 changed file

pr created time in 2 days

PR opened submariner-io/submariner-charts

Rename job so it won't shard on stable branches

Right now auto release logic updates devel to the stable branch name when creating stable branches. This leads to this job "sharding" into multiple jobs, and messes up branch protections.

To keep things simple, the main job name will remain the same so that there's no "PR targets X" and "PR targets Y" jobs, just the one "PR targets branch" job

Signed-off-by: Mike Kolesnik mkolesni@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 -->

+2 -2

0 comment

1 changed file

pr created time in 2 days

create barnchmkolesnik/submariner-website

branch : fix_pr_target_gha

created branch time in 2 days

create barnchmkolesnik/admiral

branch : fix_pr_target_gha

created branch time in 2 days

create barnchmkolesnik/submariner-charts

branch : fix_pr_target_gha

created branch time in 2 days

create barnchmkolesnik/releases

branch : fix_pr_target_gha

created branch time in 2 days