Repository navigation
example(iaas): restrict the egress of a VM with the STACKIT Server Agent - #37
Merged
mauritzuph merged 38 commits intoOct 20, 2026
Conversation
added 30 commits
October 15, 2026 09:02
added 8 commits
October 16, 2026 12:04
devpie
force-pushed
the
example/iaas-server-agent-restricted-egress
branch
from
October 19, 2026 13:31
8017bf1 to
c7c58d1
Compare
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.
Description
This PR adds the example
iaas-server-agent-restricted-egress: a VM with the STACKIT Server Agent behind an egress allow-list and a jump host.The provider cannot remove the two default egress rules of a security group (stackitcloud/terraform-provider-stackit#1810), so
remove-default-egress-rules.shdeletes them through the IaaS API.Test runs on 15 and 19 October 2026 showed that cloud-init, the Server Agent and Run Command need only DHCP and the metadata service.
A service account gets the project role
run-command.editor, because the roleowneron a folder carries no Run Command permission.Please review the README, the deletion script and the open egress of the jump host.
Checklist