-
Notifications
You must be signed in to change notification settings - Fork 33
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
Remove ManagedZone API #793
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #793 +/- ##
==========================================
+ Coverage 80.20% 82.01% +1.81%
==========================================
Files 64 76 +12
Lines 4492 6090 +1598
==========================================
+ Hits 3603 4995 +1392
- Misses 600 748 +148
- Partials 289 347 +58
Flags with carried forward coverage won't be shown. Click here to find out more.
|
6a9758a
to
790496c
Compare
a84a90c
to
ea3f66e
Compare
|
||
```sh | ||
export AWS_ACCESS_KEY_ID=xxxxxxx # Key ID from AWS with Route 53 access | ||
export AWS_SECRET_ACCESS_KEY=xxxxxxx # Access key from AWS with Route 53 access | ||
export AWS_DNS_PUBLIC_ZONE_ID=xxxxxx # DNS Zone ID in AWS Route 53 |
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.
will remove
c9e3aaf
to
0c01ad9
Compare
Signed-off-by: Michael Nairn <[email protected]> Signed-off-by: craig <[email protected]>
bab2b4c
to
bc61465
Compare
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.
Overall looks good to me. One question before giving LGTM, though.
stringData: | ||
AWS_ACCESS_KEY_ID: ${KUADRANT_AWS_ACCESS_KEY_ID} | ||
AWS_SECRET_ACCESS_KEY: ${KUADRANT_AWS_SECRET_ACCESS_KEY} | ||
AWS_REGION: ${KUADRANT_AWS_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.
missing ZONE_ID_FILTER
and ZONE_DOMAIN_FILTER
?
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.
These are no longer there. Instead we rely on the credential to filter down via permissions. Rather than having it in two places, suggestion is to create a secret with a credential that has access to the zones you want kuadrant to manage
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.
going to do a quick check for any other refs to that
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.
note now those are not needed, we will search the available zones for a matching zone and assign it to the dnsrecords. If there are 2 zones that match we will error out
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.
Sorry, I am confused. Do you mean they are optional or should not be there?
I see those two fields being added multiple times:
- https://github.com/Kuadrant/kuadrant-operator/pull/793/files#diff-676c95362ed2e144f27da53f2abc58119334a8f650ddbb61b93d2ff18ae8ef07R126
- https://github.com/Kuadrant/kuadrant-operator/pull/793/files#diff-0b71d4d09687455f24aaa3a2326bed45baa748fdfff795171148e2df85a066a8R52
- https://github.com/Kuadrant/kuadrant-operator/pull/793/files#diff-dd9adc823d5cb403f5710f23e6624096dd323f422723e7672b0f76c51385d849R242
- https://github.com/Kuadrant/kuadrant-operator/pull/793/files#diff-dd9adc823d5cb403f5710f23e6624096dd323f422723e7672b0f76c51385d849R262
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.
Yes. I noticed these also. Sorry took this PR over so was unsure. They are gone. So I will remove from those docs also
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.
ok should all be gone now @eguzki I also added an example AWS policy to set permissions
Signed-off-by: craig <[email protected]>
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.
doc/reference/dnspolicy.md
needs updating as well.
The information about the base domain name that was previously in ManagedZone spec.domainName
key is now lost or it can be mentioned in the dns Provider Secret somehow?
Signed-off-by: craig <[email protected]>
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.
doc/reference/dnspolicy.md
is still not updated with the mention of providerRefs
key
@azgabur my bad sorry. I updated a different doc. I see what you are referring to now 👍 |
Signed-off-by: craig <[email protected]>
LGTM |
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.
🧑🍳
ToDo:
Requires: