Fix(pkg): build multi-arch controllers #1103
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: rksharma95 <[email protected]>
|
imo we can retain |
|
@rksharma95 Lets keep it for now. |
Signed-off-by: rksharma95 <[email protected]>
rksharma95
force-pushed
the
fix-pkg-build
branch
from
29d68ce to
b4015dd
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose of PR?:
KubeArmor custom controllers i.e.
kubearmor-policy-manager,kubearmor-annotation-managerandkubearmor-host-policy-managerwere built with hardcoded build flagsGOOS linux GOARCH amd64therefore they were failing to execute on arm platform. the PR handles that and also thekube-rbac-proxydeployed along with custom controllers will be removed with this PR.Update:
kube-rbac-proxyhas been upgraded instead of removing it.Fixes #1101 #1084
Does this PR introduce a breaking change?
No
If the changes in this PR are manually verified, list down the scenarios covered::
Additional information for reviewer? :
Mention if this PR is part of any design or a continuation of previous PRs
Checklist:
<type>(<scope>): <subject>