453 smce deployment #454
Merged
453 smce deployment #454
Conversation
This file contains hidden or 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
…uccessfully deploying airflow now
…th mcp s3 buckets with same naming conventions
…eycloak before I test this
…I merged PRs into the main repos
can successfully deploy and login with airflow
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.
Purpose
Amazon Linux 2023 AMI upgrade and transition to using SMCE resources
No longer using custom templates for EKS to simplify
Not using the common services management console or proxies. This is because this was making things too complicated and we no longer have a common services team
This PR will provide vanilla airflow authentication, still working on adding keycloak authentication
Deploying this will only make it available for JPL subnets and the airflow login is also needed
Proposed Changes
Issues
Testing