Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: reconcile gateway client's node port #368

Merged
merged 1 commit into from
Apr 17, 2024

Conversation

kon3m
Copy link
Contributor

@kon3m kon3m commented Apr 2, 2024

Description

Fixes #309

How Has This Been Tested?

Tested it manually using two single node kind clusters.

Checklist:

  • The title of the PR states what changed and the related issues number (used for the release note).
  • Does this PR requires documentation updates?
  • I've updated documentation as required by this PR.
  • I have ran go fmt
  • I have updated the helm chart as required by this PR.
  • I have performed a self-review of my own code.
  • I have commented my code, particularly in hard-to-understand areas.
  • I have tested it for all user roles.
  • I have added all the required unit test cases.
  • I have verified the E2E test cases with new code changes.
  • I have added all the required E2E test cases.

Does this PR introduce a breaking change?


@kon3m kon3m changed the title fix: reconcile gateway client node port fix: reconcile gateway client's node port Apr 2, 2024
Copy link
Contributor

@Rahul-D78 Rahul-D78 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

@kon3m
Copy link
Contributor Author

kon3m commented Apr 3, 2024

@narmidm could you please review and approve this PR? this is a duplicate of 333. I have opened a new one as multiple authors/files got added to the previous PR while rebasing and fixing conflicts which are not relevant to the PR, so opened this new clean one.

@narmidm
Copy link
Member

narmidm commented Apr 3, 2024

Sure @kon3m, will review it and update you soon.

@narmidm narmidm added bug Something isn't working ready-to-test labels Apr 4, 2024
@NishantSingh10
Copy link
Contributor

@kon3m
Copy link
Contributor Author

kon3m commented Apr 15, 2024

@narmidm a lot of e2e tests seem to fail after the recent update made to the pipeline.

@narmidm
Copy link
Member

narmidm commented Apr 15, 2024

@narmidm a lot of e2e tests seem to fail after the recent update made to the pipeline.

We've identified the root cause of the end-to-end failure; it was due to the last release. Please allow me half an hour to release a new image for automation, after which I will rerun and verify your PR.

Apologies for the delayed response.

@mridulgain
Copy link
Contributor

mridulgain commented Apr 15, 2024

@kon3m We have added a small fix for the PR pipeline failure. Please re-sync.

@kon3m kon3m force-pushed the fix-ovpn-client-port-clean branch from 4301fec to 5c9b367 Compare April 15, 2024 14:15
@kon3m
Copy link
Contributor Author

kon3m commented Apr 15, 2024

@mridulgain @narmidm i have just updated it, can you please trigger the e2e pipeline?

@NishantSingh10

This comment was marked as resolved.

@NishantSingh10

This comment was marked as duplicate.

@NishantSingh10
Copy link
Contributor

@NishantSingh10
Copy link
Contributor

@narmidm narmidm merged commit 82d7622 into kubeslice:master Apr 17, 2024
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working ready-to-test
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Reconcile port numbers in ovpn client deployments
5 participants