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.

Sign up for GitHub

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

Support user provided acl's for zone-outages #233

Merged
merged 1 commit into from
Jan 6, 2025
Merged

Support user provided acl's for zone-outages #233

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/zone-outages.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,8 +36,8 @@ Parameter | Description
CLOUD_TYPE | Cloud platform on top of which cluster is running, [supported cloud platforms](https://github.com/krkn-chaos/krkn/blob/master/docs/node_scenarios.md) | aws |
DURATION | Duration in seconds after which the zone will be back online | 600 |
VPC_ID | cluster virtual private network to target ( REQUIRED ) | "" |
SUBNET_ID | subnet-id to deny both ingress and egress traffic ( REQUIRED ). Format: [subenet1, subnet2] | "" |

SUBNET_ID | subnet-id to deny both ingress and egress traffic ( REQUIRED ). Format: [subenet1, subnet2] | "" |
DEFAULT_ACL_ID | (Optional) ID of an existing network ACL to use instead of creating a new one. If provided, this ACL will not be deleted after the scenario | "" |

The following environment variables need to be set for the scenarios that requires intereacting with the cloud platform API to perform the actions:

Expand Down
1 change: 1 addition & 0 deletions zone-outages/env.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,5 +6,6 @@ export CLOUD_TYPE=${CLOUD_TYPE:="aws"}
export DURATION=${DURATION:=600}
export VPC_ID=${VPC_ID:=""}
export SUBNET_ID=${SUBNET_ID:=""}
export DEFAULT_ACL_ID=${DEFAULT_ACL_ID:=""}
export SCENARIO_TYPE=${SCENARIO_TYPE:=zone_outages_scenarios}
export SCENARIO_FILE=${SCENARIO_FILE:=scenarios/zone_outage.yaml}
1 change: 1 addition & 0 deletions zone-outages/zone_outage_scenario.yaml.template
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,3 +3,4 @@ zone_outage: # Scenario to create an out
duration: $DURATION # duration in seconds after which the zone will be back online
vpc_id: $VPC_ID # cluster virtual private network to target
subnet_id: $SUBNET_ID # subnet-id to deny both ingress and egress traffic
default_acl_id: $DEFAULT_ACL_ID # (Optional) ID of an existing network ACL to use instead of creating a new one. If provided, this ACL will not be deleted after the scenario.