-
Notifications
You must be signed in to change notification settings - Fork 176
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
Managed CSC for in-cluster CSM #1674
base: main
Are you sure you want to change the base?
Changes from all commits
44a292e
47784bc
377e116
352931d
686e65a
82acd1d
64eb7f8
f8e82a2
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -50,9 +50,7 @@ validate_dependencies() { | |
if ! is_stackdriver_enabled; then | ||
enable_stackdriver_kubernetes | ||
fi | ||
if needs_service_mesh_feature; then | ||
enable_service_mesh_feature | ||
fi | ||
enable_service_mesh_feature | ||
if [[ "${CA}" == "managed_cas" ]]; then | ||
x_wait_for_gke_hub_api_enablement | ||
x_enable_workload_certificate_on_fleet "gkehub.googleapis.com" | ||
|
@@ -64,8 +62,9 @@ validate_dependencies() { | |
exit_if_service_mesh_feature_not_enabled | ||
fi | ||
fi | ||
else | ||
enable_service_mesh_feature | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This will enable_service_mesh_feature for offGCP platforms in asmcli validate command also. So asmcli install and asmcli validate both calls validate_dependencies. in asmcli validate command user can not pass Now I think we can move out the logic from is_gcp section and add something like
So now we will need extra |
||
fi | ||
|
||
if can_register_cluster; then | ||
register_cluster | ||
exit_if_cluster_unregistered | ||
|
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.
We need to install managed CSC only when in-cluster CSC is not present, we will need to check for existence of in-cluster CSC.
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 see that we are doing this in install_managed_canonical_controller but we need to do
kubectl apply -f "${CANONICAL_CONTROLLER_MANIFEST}"
if in-cluster CP exists if there is change in in-cluster csc manifest.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.
Moved the logic to update the existing in-cluster CSC Deployment and checking the managed CSC status under one routine "verify_canonical_controller".