Until now, SKF has only officially supported Azure and GCP as Cloud Providers within their documentation.
This makes it difficult for people within AWS environments to easily deploy SKF without encountering several bugs and issues in the way, and having to sort them to have a fully functional deployment. This PR tries to solve this.
Description
This PR includes the guidelines to easily manually deploy SKF in an AWS environment, and some minor modifications to the Kubernetes deployment yaml files to circumvent some issues AWS-specific, without affecting the proper functioning of the platform in other Cloud Providers (Azure and GCP).
It also fixes the SKIP_LOGIN functionality that was not currently working by default in Kubernetes deployments, as the Deployment_frontend.yaml was not properly catching the variable from configmaps.yaml.
Future Improvements
We are currently working in several improvements to this setup, that will increase security and scalability of the platform, while keeping a simple deployment process. Some of them are:
Infrastructure as a Code to easily deploy SKF in AWS through CDK
Support of Amazon's EFS CSI driver to deploy database successfully to Fargate without separate namespaces
Authentication between clusters through IAM instead of Service Accounts
Adding AWS Support
Context
Until now, SKF has only officially supported Azure and GCP as Cloud Providers within their documentation. This makes it difficult for people within AWS environments to easily deploy SKF without encountering several bugs and issues in the way, and having to sort them to have a fully functional deployment. This PR tries to solve this.
Description
This PR includes the guidelines to easily manually deploy SKF in an AWS environment, and some minor modifications to the Kubernetes deployment yaml files to circumvent some issues AWS-specific, without affecting the proper functioning of the platform in other Cloud Providers (Azure and GCP). It also fixes the SKIP_LOGIN functionality that was not currently working by default in Kubernetes deployments, as the Deployment_frontend.yaml was not properly catching the variable from configmaps.yaml.
Future Improvements
We are currently working in several improvements to this setup, that will increase security and scalability of the platform, while keeping a simple deployment process. Some of them are: