-
Notifications
You must be signed in to change notification settings - Fork 193
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
Epic: submariner-addon #1517
Comments
@dfarrell07 could you expand the “linters and bots” section? |
@skitt - we need to review the feature-set section. One thing that's missing in the list is VXLAN support, but there could be others. |
I think this is one of the first things we need to do, as how we want to add linting depends on what we decide. I tend to think we should use Shipyard's infra. |
Continuing to think we should build on Shipyard. I'm struggling, getting a taste of how it would be without Shipyard, with duplicating the infra required to add basic gitlint CI. The Makefile here as-is seems to require Go 1.15 for everything. The latest available from Ubuntu's package manager is 1.13, which why I'm having to install it manually. |
Right, that’s what I’m thinking too. My main concern is how well our Dapper-based builds will work with Prow; I reckon the best way to find that out would be to open a PR using Dapper ;-).
We even need 1.16 for the build itself (see |
I’ve added the missing pieces from the feature matrix (look at the last edit). |
I think we have Ubuntu 20.04 on the ubuntu-latest GHA runner. https://github.com/actions/virtual-environments#available-environments It seems to install 1.13.
https://github.com/dfarrell07/submariner-addon/pull/2/checks?check_run_id=3253760648
I made a basic Shipyard Makefile/Dockerfile.dapper per the docs, which was going fine until I realized I had clobbered the existing Makefile. 😅 On a somewhat-related note, I just saved your custom-Dapper PR from stalebot. Has Mike's feedback been addressed? Can we merge it? submariner-io/shipyard#594 |
Yes, runners only provide LTS releases of Ubuntu; the next update will be 22.04.
I think it has, but I’d rather wait for Mike to take another look at it — there’s no rush. (And thanks for re-opening it!) |
@SteveMattar would you be interested in working on adding an E2E test using OCM in Submariner? It should be similar to the work you’ve done to test the bundle with OLM. There’s already a “deploy” target in the addon which sets up kind with OLM and OCM. |
@skitt yes sure I will. |
We talked about moving away from vendoring today on the addon sync. In summary, it doesn't seem like vendoring is worth it. In particular:
The costs to vendoring are substantial:
|
@skitt Can we close this epic and track remaining work in new epic / issues? |
Yes, let’s close this, it has run its course. Remaining tasks should be added to appropriate epics or handled as individual issues. |
This epic tracks work to be done on https://github.com/open-cluster-management/submariner-addon:
strikethroughif we don't want it. For checked linters, send a PR to fix/enable the linter. Forunwantedlinters, send a PR to document inline why we don't want the linter. Once there is a PR, remove the linter from the list here and add the PR to the list above.subctl gather
)The text was updated successfully, but these errors were encountered: