-
Notifications
You must be signed in to change notification settings - Fork 34
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
Fix cloud provider installation in AWS template #583
Fix cloud provider installation in AWS template #583
Conversation
@@ -229,6 +235,7 @@ apiVersion: addons.cluster.x-k8s.io/v1beta1 | |||
kind: ClusterResourceSet | |||
metadata: | |||
name: crs-ccm | |||
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.
I think when specifying -n <namespace>
in kubectl apply
, namespace is being set for each resource from the list. It may however conflict with an already set value. Could this value be removed from templates instead?
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.
@Danil-Grigorev the namespace is there to align with clusterctl
templates, where it's used to substitute namespace in generate
command
Signed-off-by: Alexandr Demicev <[email protected]>
c9f7cd0
to
74764d8
Compare
Signed-off-by: Alexandr Demicev <[email protected]>
cae8f95
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: