feat: refactor stackit edge cloud provisioning#347
Open
Matthiator wants to merge 11 commits into
Open
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
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.
📝 Summary
Refactors STACKIT Edge Cloud provisioning so Edge Cloud can be handled as a separate, opinionated provisioning path next to SKE.
This PR:
/longhornTraefik subpath by rendering the required redirect and path rewrite middlewares.🧩 Type of change
The previous Edge Cloud Terraform input/output shape is replaced. Legacy single-host Edge inputs are intentionally removed in favor of the new Edge instance, image, and hosts structure.
🧪 Testing
Manual validation so far:
/longhornsubpath.make docs-buildsuccessfully.make testsuccessfully.Still pending before marking this PR ready:
🔗 Related Issues / Tickets
✅ Checklist
📎 Additional Context (optional)
This PR is intentionally opened as draft while the Edge Cloud flow is still being validated end-to-end.