Known Issues - Server in a Cluster
How To’s
- How to configure an AWS EKS Cluster for the vFunction Server
- How to create an HTTPProxy Ingress for a vFunction Server in a Kubernetes Cluster
- How to create an Istio Ingress for a vFunction Server in a Kubernetes Cluster
- How to modify autoscaling after increasing CPU on Measurements Pods
- Restore a vFunction Server in an OpenShift Cluster
- Restore a vFunction Server running via an Operator in an Kubernetes Cluster
- Restore a vFunction Server running via Helm in an Kubernetes Cluster
Known Issues
- A ‘401 Unauthorized’ error is thrown when adding Azure Devops integration to vFunction Server
- Error ‘[Backup]: Couldn’t clean up validation database restore_validate_idp’ prevents MySQL Pod from starting during upgrade
- Error ‘Container delay-start must set securityContext.allowPrivilegeEscalation=false’ when deploying vFunction Server on Kubernetes via Helm Charts
- Error, ‘PermissionError: [Errno 13] Permission denied: /.cache’ when starting Learning on an OpenShift vFunction Server
- Error ‘PodSecurity: seccompProfile (pod or containers istio-validation, istio-proxy must set securityContext.seccompProfile.type to RuntimeDefault or Localhost)’ when deploying vFunction Server on Kubernetes via Helm Charts
- No CONTROLLER_KEYS in vfapi-custom-env.list causes vfapi Pods to throw ‘One of the given keys is nil’ error
- Organizations Pod throws error, ‘Measurement services were not registered’
- Retain PersistentVolumeClaims in a vFunction Server Helm Kubernetes Upgrade if the current Server version is below 4.3