Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add preliminary support for other cloud providers to orchestratord #30534

Conversation

alex-hunt-materialize
Copy link
Contributor

@alex-hunt-materialize alex-hunt-materialize commented Nov 18, 2024

Adds preliminary support for other cloud providers to orchestratord.

Does not add any special handling of them, but accepts GCP, Azure, and Generic cloud providers.

In the future, we may want to expand our support for these to include their equivalent of IAM roles, to support advanced features such as non-password-based access to persist buckets or assuming roles, but that is all out of scope for now.

Motivation

  • This PR fixes a previously unreported bug.

With self-hosted, our customers may run this in other cloud providers.

Tips for reviewer

Checklist

  • This PR has adequate test coverage / QA involvement has been duly considered. (trigger-ci for additional test/nightly runs)
  • This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
  • If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
  • If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).
  • If this PR includes major user-facing behavior changes, I have pinged the relevant PM to schedule a changelog post.

@alex-hunt-materialize alex-hunt-materialize force-pushed the orchestratord_other_cloud_providers branch 4 times, most recently from eb54197 to 1a5a4f3 Compare November 19, 2024 13:36
Changes orchestratord to use the CloudProvider used by the catalog, to
reduce duplication and eliminate the possibility of incompatibilities
between them.
Adds preliminary support for other cloud providers.

Does not add any special handling of them, but accepts GCP, Azure, and
Generic cloud providers.

In the future, we may want to expand our support for these to include
their equivalent of IAM roles, to support advanced features such as
non-password-based access to persist buckets or assuming roles, but that
is all out of scope for now.
@alex-hunt-materialize alex-hunt-materialize force-pushed the orchestratord_other_cloud_providers branch from 1a5a4f3 to d0c0e38 Compare November 19, 2024 13:37
@alex-hunt-materialize alex-hunt-materialize marked this pull request as ready for review November 19, 2024 14:13
@alex-hunt-materialize alex-hunt-materialize requested a review from a team as a code owner November 19, 2024 14:13
@alex-hunt-materialize alex-hunt-materialize merged commit 5a40a50 into MaterializeInc:main Nov 19, 2024
83 checks passed
@alex-hunt-materialize alex-hunt-materialize deleted the orchestratord_other_cloud_providers branch November 19, 2024 16:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants