search

wso2 / k8s-api-operator

API Operator for Kubernetes
Apache License 2.0
115 stars 48 forks source link

WSO2 API Operator to support volumeMounts #615

Closed Thilinika closed 2 years ago

Thilinika commented 2 years ago

Problem

There are 2 concerns when using the API operator-2.0.2 for Micro Integrator deployments.

Requirement 1

The WSO2 recommendation is to have pre-built images (immutable) to deploy via the API Operator. The requirement is using volumes mounted by config maps as it is easier to maintain and it follows the same pattern as APIM.

Is this something we can facilitate via the API operator?

Requirement 2

At the moment using helm charts to deploy APIM and is using node affinity to schedule nodes in Pod based on node labels.

Please refer to the screenshots of how we have configured affinity in APIM deployments. AM Node 1

image

AM Node 2 image

Since the using API Operator for Micro Integrator deployments, would like to have the support to configure node affinity for MI via the API Operator as well. Is this something we can provide?

Solution

Since we using API Operator for Micro Integrator deployments, we would like to have the support to configure node affinity for MI via the API Operator as well. Is this something we can provide?

Affected Component

MI

Version

No response

Implementation

No response

Related Issues

No response

Suggested Labels

MI-4.0.0

malakaganga commented 2 years ago

Requirement 1

Added with: https://github.com/wso2/k8s-api-operator/pull/613

Requirement 2

Added with: https://github.com/wso2/k8s-api-operator/pull/614

github-actions[bot] commented 2 years ago

This issue is NOT closed with a proper Resolution/ label. Make sure to add proper reason label before closing. Please add or leave a comment with the proper reason label now.

      - Resolution/Cannot Reproduce - Issue cannot be reproduced.
      - Resolution/Duplicate - Issue is already reported before.
      - Resolution/Fixed - Issue has already been fixed.
      - Resolution/Answered - Issue has already been answered.
      - Resolution/Invalid - Issue is invalid.
      - Resolution/Not a bug - Issue is not a bug.
      - Resolution/Postponed - Issue is postponed.
      - Resolution/Won’t Fix - Issue won't be fixed.