-
Notifications
You must be signed in to change notification settings - Fork 8
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
[2] Configure firewall rules and policies for the federated learning use case #74
Conversation
c65e608
to
d1ac6dc
Compare
9123bf4
to
e5385e4
Compare
a869035
to
8f05a35
Compare
865fa3a
to
0f461fe
Compare
0f461fe
to
5096b6b
Compare
c3ecb28
to
3783ea1
Compare
052b3bf
to
4d73609
Compare
Can you remove the It prevents the teardown script from running on a deploy failure. |
c68a80e
to
8bdcb96
Compare
Done! |
It seems like the build is silently failing on the "Provisioning the core platform": As it doesn't seem to reach the "Provisioning the use case resources" and just goes straight to the destroy. |
I was able to get it to deploy, but it looks like the destroy is failing on "Destroying the services that the core platform depends on" |
- configure firewall for federated learning - configure iam roles and service accounts - configure dedicated node pools - configure policy controller and policies - configure dedicated Kubernetes namespaces
8bdcb96
to
1c2f4a0
Compare
This is the error:
I think this is due to the fact that we cannot enable a global feature if it's already enabled. Importing it in the Terraform state would work around this, but it will also disable the feature when running the teardown script. We can sync about this.
The cause of this issue was that the use case deploy script initialized core platform configuration files after running the core platform deploy script, so the |
- configure firewall for federated learning - configure iam roles and service accounts - configure dedicated node pools - configure policy controller and policies - configure dedicated Kubernetes namespaces
- configure firewall for federated learning - configure iam roles and service accounts - configure dedicated node pools - configure policy controller and policies - configure dedicated Kubernetes namespaces
teardown.sh
script: remove backend configuration only when destroying the coreinitialize
terraservice, instead of running it in any case after destroying the Terraservices inCORE_TERRASERVICES_DESTROY
becauseCORE_TERRASERVICES_DESTROY
might not includeinitialize
.teardown.sh
script: ensure that terraservices are destroyed in order.