In this article:

Setting Up Access on Creating Persistent Volume and Persistent Volume Claim

Settings on Installation Failure

Settings on Connection Failure During Installation

Solving Possible Issues on Use of Kubernetes

The following issues may arise during deployment of a fault-tolerant cluster based on Kubernetes:

Setting Up Access on Creating Persistent Volume and Persistent Volume Claim

By default, pod and container security management policies are disabled in the mobile platform.

To set up access on creating persistent volume and persistent volume claim:

  1. Open the fmp/chart/values.yaml file and comment the strings:

containerSecurityContext:
 enabled: false
podSecurityContext:
 enabled: false

  1. Delete and reinstall Foresight Mobile Platform in the cluster.

Settings on Installation Failure

Installation of Foresight Mobile Platform may return the error:

* admission webhook "sgcluster.mutating-webhook.stackgres.io" denied the request: Failure executing: POST at: https://10.222.0.1:443/apis/stackgres.io/v1/namespaces/fmp/sgpoolconfigs. Message: sgpoolconfigs.stackgres.io "generated-from-default-1712323110835" already exists. Received status: Status(apiVersion=v1, code=409, details=StatusDetails(causes=[], group=stackgres.io, kind=sgpoolconfigs, name=generated-from-default-1712323110835, retryAfterSeconds=null, uid=null, additionalProperties={}), kind=Status, message=sgpoolconfigs.stackgres.io "generated-from-default-1712323110835" already exists, metadata=ListMeta(_continue=null, remainingItemCount=null, resourceVersion=null, selfLink=null, additionalProperties={}), reason=AlreadyExists, status=Failure, additionalProperties={}).

To solve the issue, delete Foresight Mobile Platform and then reinstall StackGres.

Settings on Connection Failure During Installation

If connection fails during installation of Foresight Mobile Platform, increase timeout and remove the constraint for request body in ingress:

kubectl annotate ingress -n fmp --all --overwrite nginx.ingress.kubernetes.io/proxy-body-size='0'
kubectl annotate ingress -n fmp --all --overwrite nginx.ingress.kubernetes.io/proxy-read-timeout='3600s'
kubectl annotate ingress -n fmp --all --overwrite nginx.ingress.kubernetes.io/proxy-send-timeout='3600s'

See also:

Preparation and Deployment of Fault-Tolerant Cluster Based on Kubernetes