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(cni): check to enable ipv6 flag on transparent proxy engine #4642

Merged
merged 1 commit into from
Jul 19, 2022

Conversation

slonka
Copy link
Contributor

@slonka slonka commented Jul 19, 2022

Signed-off-by: slonka [email protected]

Summary

Check if ipv6 can be enabled and pass the value to the config

Full changelog

  • [Fix failing ipv6 build https://app.circleci.com/pipelines/github/kumahq/kuma/15351/workflows/cb3322ce-4881-40a7-b8f4-1cd7cef2b07f/jobs/185366/parallel-runs/4

Issues resolved

No issue created, build failing.

Documentation

- [ ] Link to the website documentation PR

Testing

- [ ] Unit tests
- [ ] E2E tests
- [ ] Manual testing on Universal

  • Manual testing on Kubernetes

Backwards compatibility

- [ ] Update UPGRADE.md with any steps users will need to take when upgrading.
- [ ] Add backport-to-stable label if the code follows our backporting policy

@slonka slonka marked this pull request as ready for review July 19, 2022 12:39
@slonka slonka requested a review from a team as a code owner July 19, 2022 12:39
Copy link
Contributor

@bartsmykla bartsmykla left a comment

Choose a reason for hiding this comment

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

lgtm

@slonka
Copy link
Contributor Author

slonka commented Jul 19, 2022

I reverted back the commit that enabled the whole suite of the tests, the ipv6 now passes. merging

image

@slonka slonka merged commit ed7a22e into kumahq:master Jul 19, 2022
@slonka
Copy link
Contributor Author

slonka commented Jul 19, 2022

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants