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

caa: support peerpods in node-installer (again) #1043

Closed
wants to merge 19 commits into from

Conversation

burgerdev
Copy link
Contributor

@burgerdev burgerdev commented Nov 29, 2024

This reapplies most of the commits that moved CAA into the node-installer. I've split the commits into the clean reapplies and dedicated fixup commits where I found problems in the original commits. These include:

  • Ensure that the agent config is not skipped while serializing.
  • Add missing environment variable and RBAC on the CAA container.
  • Include iptables in the CAA container image.
  • Deploy RBAC resources from the apply-runtime target, which is the point when we know the namespace to apply them to.

The last commit adapts the peer-pods e2e test to the prior changes, which means that the peer-pods workflow is not expected to work for the last 3 commits or so. We could squash this PR, but I think I'd prefer to have the history intact.

@burgerdev burgerdev added the no changelog PRs not listed in the release notes label Nov 29, 2024
@burgerdev burgerdev force-pushed the burgerdev/revert-revert branch from 0e9248a to aa53900 Compare December 2, 2024 09:43
@burgerdev burgerdev marked this pull request as ready for review December 2, 2024 10:52
@burgerdev burgerdev requested a review from katexochen as a code owner December 2, 2024 10:52
@katexochen
Copy link
Member

We could squash this PR, but I think I'd prefer to have the history intact.

You mean you want to keep the fixup commits?

Changes lgtm, didn't test yet.

@burgerdev
Copy link
Contributor Author

We could squash this PR, but I think I'd prefer to have the history intact.

You mean you want to keep the fixup commits?

Changes lgtm, didn't test yet.

Sorry, I meant to say that I want to fixup the fixups and then rebase. We keep the history, but have a few intermediate commits that won't pass e2e tests.

@burgerdev burgerdev force-pushed the burgerdev/revert-revert branch from aa53900 to 3caff7b Compare December 5, 2024 14:39
@burgerdev burgerdev force-pushed the burgerdev/revert-revert branch 2 times, most recently from 92e2e90 to b373dfa Compare December 6, 2024 15:58
@burgerdev burgerdev force-pushed the burgerdev/revert-revert branch from b373dfa to d1b8911 Compare December 10, 2024 18:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no changelog PRs not listed in the release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants