-
Notifications
You must be signed in to change notification settings - Fork 8
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
Conversation
0e9248a
to
aa53900
Compare
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. |
aa53900
to
3caff7b
Compare
92e2e90
to
b373dfa
Compare
This reverts commit da32110.
This reverts commit 22ba580.
This reverts commit 9438bdb.
…d config" This reverts commit 3ecbce3.
This reverts commit 39e8274.
…SNP" This reverts commit 36c6293.
This reverts commit 5abaf33.
This reverts commit 85fe4dc.
This reverts commit fde72c2.
This reverts commit ee335a7.
This reverts commit a475b4a.
…PEER-SNP"" This reverts commit 63b147d.
b373dfa
to
d1b8911
Compare
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:iptables
in the CAA container image.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.