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

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

submariner-io/lighthouse 52

Controller to facilitate DNS discovery between clusters

submariner-io/submariner-operator 46

Submariner's Operator installs and maintains your Submariner deployment.

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.

submariner-io/admiral 7

Admiral is the submariner API to distribute and exchange metadata between clusters.

submariner-io/coastguard 4

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

submariner-io/releases 4

Submariner release process repository

submariner-io/submariner-website 4

This is the submariner website source code (hugo based).

submariner-io/get.submariner.io 1

Get submariner/subctl script

pull request commentsubmariner-io/lighthouse

Allow fine grain control over weights per cluster

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

danibachar

comment created time in 3 hours

delete branch submariner-io/submariner

delete branch : z_pr1512/sridhargaddam/test-gn-flaky-service

delete time in 3 hours

pull request commentsubmariner-io/submariner

Delete iptable chains as soon as service is deleted

🤖 Closed branches: [z_pr1512/sridhargaddam/test-gn-flaky-service]

sridhargaddam

comment created time in 3 hours

PR closed submariner-io/submariner

Reviewers
Delete iptable chains as soon as service is deleted wontfix ready-to-test

In the new implementation of Globalnet, as soon as a service is deleted, we are initially deleting the corresponding GlobalIngressIP Object and in the respective controller.OnDelete method, we are flushing out the iptable rules. This is causing some delay and in the meantime when kubeproxy is trying to remove the corresponding service related iptable chains, its erroring out as there are still some references to the chain. Kubeproxy continues to retry the delete operation. This PR modifies the behavior to delete the itpable chains as soon as the service is deleted.

Signed-Off-by: Sridhar Gaddam sgaddam@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 -->

+50 -3

9 comments

2 changed files

sridhargaddam

pr closed time in 3 hours

issue closedsubmariner-io/submariner

[Question]: why submariner only support k8s version 1.17 or later

Submariner doc Prerequisites section here show Minimum supported Kubernetes version is 1.17, why?

  1. does that mean submariner only verified on k8s version 1.17 or later, then it announce that version is supported ? Maybe submariner support k8s 1.16, but this version doesn't get verified?
  2. for k8s api compatibility issue so that submariner only support k8s version 1.17 or later?
  3. submariner depends on k8s specific feature that only include from k8s version 1.17?

If I want submariner works well on k8s 1.16/1.15, what is the porting works that I MUST do? do we have any plan to support old k8s version, since 1.17 is too high, many k8s clusters still state in 1.14/1.15 at IDC or Cloud.

closed time in 11 hours

huxiaoliang

issue commentsubmariner-io/submariner

Avoid dependency on the iptable chains programmed by IPtables kube-proxy driver.

This issue has been automatically marked as stale because it has not had activity for 60 days. It will be closed if no further activity occurs. Please make a comment if this issue/pr is still valid. Thank you for your contributions.

sridhargaddam

comment created time in 11 hours

issue commentsubmariner-io/submariner

Epic: OVN support

This issue has been automatically marked as stale because it has not had activity for 60 days. It will be closed if no further activity occurs. Please make a comment if this issue/pr is still valid. Thank you for your contributions.

nyechiel

comment created time in 11 hours

fork Icarus9913/submariner

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

fork in 16 hours

startedsubmariner-io/submariner

started time in a day

push eventsubmariner-io/submariner-operator

Mike Kolesnik

commit sha 3928012be343b70e8f1466472ba5cb8a9adb4aa8

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>

view details

Steve Mattar

commit sha 9e0a5217745cc41c9cdf470fa813be4e1c51fb19

build(bundle): set the replaced version using kustomize use the FROM_VERSION to update the replaced version in the csv file. update the description release branch dynamically. Signed-off-by: Steve Mattar <smattar@redhat.com>

view details

Steve Mattar

commit sha dd691381067b5cc2a9b92590e85f58d921f12802

build(bundle): add required OLM descriptors for scorecard tests Signed-off-by: Steve Mattar <smattar@redhat.com>

view details

Steve Mattar

commit sha 837340d32a46b79ae9d4e2d1d4aa4dc3c686b276

test(periodic): use scorecard tool Statically validate the operator bundle is free of syntax errors and packaged properly using the built-in OLM tests. Signed-off-by: Steve Mattar <smattar@redhat.com>

view details

Steve Mattar

commit sha 134fa54ae355dcfebcab1eb844d636c33a1bf15b

chore: update bundle to 0.11.0 Signed-off-by: Steve Mattar <smattar@redhat.com>

view details

push time in a day

pull request commentsubmariner-io/submariner-charts

Allow submariner-globalnet role to handle endpoints

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

mkimuram

comment created time in a day

PullRequestReviewEvent

create barnchsubmariner-io/releases

branch : z_pr249/Jaanki/dependent_pr

created branch time in a day

pull request commentsubmariner-io/releases

Enable PR dependency check jobs

🤖 Created branch: z_pr249/Jaanki/dependent_pr

Jaanki

comment created time in a day

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

fork Jaanki/releases

Submariner release process repository

fork in a day

startedsubmariner-io/submariner

started time in a day

issue commentsubmariner-io/lighthouse

Port conflict in aggregated ServiceImports for SRV records

This issue has been automatically marked as stale because it has not had activity for 60 days. It will be closed if no further activity occurs. Please make a comment if this issue/pr is still valid. Thank you for your contributions.

aswinsuryan

comment created time in 2 days

PullRequestReviewEvent

push eventsubmariner-io/submariner-io.github.io

Submariner Website CI

commit sha 6437c3a7eafb02044cc5067225ea6d362ddf88df

Updated website from submariner-io/website c148379

view details

push time in 2 days

pull request commentsubmariner-io/submariner-website

Fix typo

🤖 Closed branches: [z_pr602/vincent-pli/fix-typo]

vincent-pli

comment created time in 2 days

delete branch submariner-io/submariner-website

delete branch : z_pr602/vincent-pli/fix-typo

delete time in 2 days

push eventsubmariner-io/submariner-website

pengli

commit sha 9a61157433d532e0b0b1a801511dc7e29637f84a

fix typo Signed-off-by: pengli <justdoit.pli@gmail.com>

view details

push time in 2 days

PR merged submariner-io/submariner-website

Reviewers
Fix typo

should be two cluster : )

+1 -1

2 comments

1 changed file

vincent-pli

pr closed time in 2 days

PullRequestReviewEvent

push eventsubmariner-io/shipyard

Mike Kolesnik

commit sha e407fa0047aafb4bccf4aebb5ee489fa377419d5

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>

view details

Stephen Kitt

commit sha 28e7ef051570ff55ec7b190b9f2e4717ecfbbd73

Merge branch 'devel' into update-k8s-versions

view details

push time in 2 days

created tagsubmariner-io/submariner-operator

tagv0.11.0-rc2

Submariner's Operator installs and maintains your Submariner deployment.

created time in 2 days

release submariner-io/submariner-operator

v0.11.0-rc2

released time in 2 days

release submariner-io/submariner-charts

v0.11.0-rc2

released time in 2 days