Scenario: KCP Azure VpcPeering is created 1583.02ms 100.00% ✔
Given Scope exists 41.88ms 2.65% ✔
And Given local Azure VNET exists 0.06ms 0.01% ✔
And Given remote Azure VNet exists with Kyma tag 0.01ms 0.01% ✔
When KCP VpcPeering is created 28.12ms 1.78% ✔
Then KCP VpcPeering is in missing local network error state 203.52ms 12.86% ✔
When local KCP Network is created 1.27ms 0.08% ✔
Then KCP VpcPeering is in waiting local network to be ready error state 202.36ms 12.78% ✔
When local KCP Network is Ready 204.62ms 12.93% ✔
Then KCP VpcPeering is in missing remote network error state 0.67ms 0.04% ✔
When remote KCP Network is created 1.09ms 0.07% ✔
Then KCP VpcPeering is in waiting remote network to be ready error state 203.73ms 12.87% ✔
When remote KCP Network is Ready 224.88ms 14.21% ✔
Then local Azure VPC Peering is created 0.04ms 0.01% ✔
And Then remote Azure VPC Peering is created 0.03ms 0.01% ✔
Then KCP VpcPeering state is Initiated 22.54ms 1.42% ✔
When Azure VPC Peering state is Connected 0.08ms 0.01% ✔
Then KCP VpcPeering has Ready condition 229.54ms 14.50% ✔
And Then KCP VpcPeering has finalizer 0.01ms 0.01% ✔
Then KCP VpcPeering state is Connected 0.01ms 0.01% ✔
And Then KCP VpcPeering has status.id equal to local Azure Peering ID 0.01ms 0.01% ✔
And Then KCP VpcPeering has status.remoteId equal to remote Azure Peering ID 0.01ms 0.01% ✔
When KCP VpcPeering is deleted 2.70ms 0.17% ✔
Then KCP VpcPeering does not exist 203.88ms 12.88% ✔
And Then local Azure peering does not exist 0.01ms 0.01% ✔
Description
Related issue(s)