Purpose of PR?:
When KubeArmor is installed on nodes with CPUs not supporting x86-64-v3 architecture, the following error was reported from init container

Fatal glibc error: CPU does not support x86-64-v3

KubeArmor ships two different init images

1. kubearmor-init: Based on Apline, uses musl
2. kubearmor-init-ubi: Based on RedHat UBI 10, uses glibc

The above error was seen when KubeArmor used the kubearmor-init image, which should never happen because Alpine based images uses musl and not glibc. This error is not possible unless the image is UBI 10 based, since UBI 10 dropped support for x86-64-v3 CPU architecture and uses glibc.

The reason for this error was that in the push_kubearmor.sh script used to build kubearmor and kubearmor-init images, it missed the --target kubearmor-init flag in the following line which caused the UBI 10 based image to be built instead of the Alpine based one.

Fixes #

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:

• Bug fix. Fixes #
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update
• PR Title follows the convention of <type>(<scope>): <subject>
• Commit has unit tests
• Commit has integration tests