AWS Support and SKIP Login fix in kubernetes #800
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
CarlesLlobet
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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: