Skip to content

Update KubeArmor Marketplace Releases

Ramakant Sharma edited this page Apr 15, 2024 · 4 revisions

Table of Contents:

  1. RedHat
  1. AWS
  1. Oracle [TBD]

  2. Digital Ocean [TBD]

Redhat

Update Operator Bundle

key parts of the bundle spec:

alm examples: provide an example of the CR (kubearmorconfig) supposed to be created by the user to configure the KubeArmor deployment.

crdSpec: specification of the Custom Resource that operator provides, use specDescriptors field to provide the short description of the fields supported by the CR for user's understanding.

description: self explanatory field that is used for long description of the operator.

permissions: rbac permissions required by the operator and the operands that are being deployed by the operator itself.

related images: container images that operator deploys as part of KubeArmor application.

version: operator version.

Note: Update the sha digest of all the images referenced in the operator.

Test the Operator

test and validate operator preferably using an OpenShift environment, apart from functionality test integration test can be performed to test the operator bundle, please check integration testing using OLM

Publish the operator

Create a new version (directory) with updated operator bundle and raise a PR to the upstream repo https://github.com/kubearmor/certified-operators/tree/main/operators/kubearmor-operator-certified.

AWS

Prerequisites:

Access to the AWS marketplace portal https://aws.amazon.com/marketplace/login Setup and configure AWS CLI https://aws.amazon.com/cli/

Update the Listing

On aws marketplace management portal, select KubeArmor under the server category of products. And add a new version of the KubeArmor. Once chosen this option, follow the instructions in the subsequent window. Update Listing with Helm and EKS add-on delivery method added and update the image or Helm chart references wherever prompted to create a new listing.

image1

Oracle [TBD]

Digital Ocean [TBD]

Clone this wiki locally