-
Notifications
You must be signed in to change notification settings - Fork 0
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
Red Hat Konflux update osc-caa #14
Conversation
/ok-to-test |
7d8062b
to
3f8b192
Compare
There is no need to support iptables-wrapper. You can cherry-pick my commit here, or reproduce it yourself. |
0c5be74
to
1c56c07
Compare
Seems like we have something that builds ! |
@littlejawa your latest commit ace242e overwrites what you did with 3628d91. |
257e3ad
to
dc31262
Compare
I'm removing iptables from the release image, to be consistent with what we are doing on the CPaaS builds. |
18c7f11
to
1f25c3e
Compare
Signed-off-by: red-hat-konflux <[email protected]>
We need to enable the CRB in the builder image, but this requires managing the subscription too. The activation key and org ID are already available to us through a mount file, so we should be able to use them. Making the same change in the release image, but commenting it out, as it seems the subscription is already done, and calling it again breaks the build. Keeping it as comments for local builds. Signed-off-by: Julien Ropé <[email protected]>
We don't need it on RHEL because we know the iptables mode we support, nft. The wrapper provides an easy way to support both "legacy" and "nft" modes when you don't know the system the container will run in. RHEL only supports nft, so there is no point in supporting legacy through the wrapper. See docs at https://github.com/kubernetes-sigs/iptables-wrappers
dc31262
to
6e96a37
Compare
Pipelines as Code configuration proposal
To start the PipelineRun, add a new comment with content
/ok-to-test
For more detailed information about running a PipelineRun, please refer to Pipelines as Code documentation Running the PipelineRun
To customize the proposed PipelineRuns after merge, please refer to Build Pipeline customization