-
Notifications
You must be signed in to change notification settings - Fork 188
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
Feature: dependencies of resources #4054
Comments
We think there may be a bug where we're not retrying after a failed attempt to reconcile a PublicIPAddress - we'll look into that. That said, you can make this work by making a minor tweak to your YAML files. Instead of referencing the PublicIPPrefix by it's ARM ID, reference the ASO resource directly, within the cluster, by using the E.g. apiVersion: network.azure.com/v1api20201101
kind: PublicIPAddress
metadata:
name: clusterapi-prov-second-cluster-egress-ip-12
namespace: second-cluster
...
spec:
location: westeurope
owner:
armId: /subscriptions/xxxxxx-xxxx-xxxxx-xxxxxx-xxxxxxxxxx/resourceGroups/xxxxxxxxx
sku:
name: Standard
publicIPAllocationMethod: Static
publicIPAddressVersion: IPv4
publicIPPrefix:
group: network.azure.com
kind: PublicIPPrefix
name: clusterapi-prov-second-cluster-ip-prefix-2 Where possible, you should prefer to reference resources known to ASO by using their |
I think you meant to use -
I tried this but looks like here the retry logic is missing again. I still get the similar error although the publicIPPrefix created successfully PublicIPPrefix Status
Error
Again after waiting for some time I see the same erros that I provided initially -
|
The warnings you are seeing appear to be normal to me - but the errors do seem to indicate a problem. I'll try to reproduce the problem and see if I can work out what's going on. |
I am new to ASO and not sure whether this feature already exist. It would nice if you could guide me. I am trying to create a PublicIPPrefix and 3 egress ips attached to them. when I apply all the yamls I see that IP Prefix gets created but rest of the three egress IPs go in a race condition and they are stuck in a loop (appears to be a race condition)resulting none of the IPs get created.
Alternatively, if I apply the ipprefix.yaml file and wait for few seconds before applying the egress.yaml, everything works fine..
Here is my Yaml file
ipprefix.yaml
egress.yaml
Error
Expectation
It is expected that the IPs have dependency on the IPPrefix, once IPPrefix is created then IPs will be created.
The text was updated successfully, but these errors were encountered: