-
Notifications
You must be signed in to change notification settings - Fork 12
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
feat(net): Add multizone deployment capabilities to subnets #276
Conversation
You have to keep a compatibility with user which are currently used network.subregionName. |
Also you can also add subnet.subregionName here in https://github.com/outscale/cluster-api-provider-outscale/blob/main/api/v1beta1/oscmachine_validation.go the subregionName, (Like in osc_machine https://github.com/outscale/cluster-api-provider-outscale/blob/main/api/v1beta1/oscmachine_validation.go ) |
Also please add a example with multi subnet region. |
Also you can also migrate all the template which are used in CI https://github.com/outscale/cluster-api-provider-outscale/blob/main/test/e2e/data/infrastructure-outscale |
And also in template ? |
Yes i agree, i will do just that! |
I don't understand what you mean here. |
60d7d5b
to
bc97a16
Compare
And please rebase from main branch (because some omi have changed) |
(Ps i use tilt (which is recommand in cluster-api https://cluster-api.sigs.k8s.io/developer/tilt.html?highlight=Tilt#customizing-tilt ) and vscode to dev cluster-api (https://github.com/outscale/cluster-api-provider-outscale/blob/main/docs/src/developers/developement.md ) |
in osccluster_controller_test.go (osc_region and osc_subregion) is
|
bc97a16
to
42520ec
Compare
8ba94b5
to
d84bfab
Compare
def133f
to
f029fe4
Compare
@outscale-vbr this MR is ready to review |
@sebglon @gvdhart
Please ignore your mock:
|
We just tried to reproduce this error but we did not succeed :
|
@@ -890,17 +891,8 @@ var _ = Describe("Outscale Cluster Reconciler", func() { | |||
}) | |||
It("should create a simple cluster with default values", func() { | |||
ctx := context.Background() | |||
osc_region, ok := os.LookupEnv("OSC_REGION") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please set it back osc_region and osc_subregion for ci
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I put back this line but go trig a warning causes they're unused
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Put it back this
SubregionName: osc_subregion (line 903)
@gvdhart @sebglon
Ps it test your PR locally and with ci with those changes. So after your PR will be merged. |
infraClusterSpec := infrastructurev1beta1.OscClusterSpec{ | ||
Network: infrastructurev1beta1.OscNetwork{ | ||
SubregionName: osc_subregion, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Keep it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
What type of PR is this?
/kind feature New functionality with test.
What this PR does / why we need it:
This PR implements the multi az feature for subnets. Subnets that are deployed with cluster-api can now be defined with a SubregionName instead of defaulting to the OscNetwork SubregionName.
In order to be fully resilient the NAT services can also be deployed in multi az's in this PR.
TODOs: