-
Notifications
You must be signed in to change notification settings - Fork 25
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
Do not use default namespace in AKS e2e example #1149
Conversation
09d218a
to
8c47bf2
Compare
8c47bf2
to
42dc941
Compare
spec: | ||
allowedNamespaces: {} | ||
clientID: ${AZURE_CLIENT_ID} | ||
clientSecret: | ||
name: cluster-identity-secret | ||
namespace: capz-system | ||
namespace: ${NAMESPACE} |
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.
This is going to break the test. The Secret is actually in the capz-system
namespace (it's reused across tests).
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.
According our documentation: Note that the AzureClusterIdentity is a namespaced resource and it needs to be created in the same namespace as the Cluster.
https://turtles.docs.rancher.com/turtles/next/en/user/clusterclass.html#_setup
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.
@mjura The documentation is correct. The line I mentioned however is a Secret reference.
The Secret is in capz-system
, the AzureClusterIdentity
is not.
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #
Special notes for your reviewer:
Checklist: