Skip to content
This repository has been archived by the owner on Nov 2, 2024. It is now read-only.

fix: Explicitly create SLO services when installation with ASM is launched #1064

Merged
merged 5 commits into from
May 1, 2024

Conversation

minherz
Copy link
Contributor

@minherz minherz commented Apr 30, 2024

Modify terraform to add explicit SLO service provisioning. In the past, deploying Istio services result in automatic creation of matching SLO services. The recent change in behavior resulted in the installation process running forever while waiting for SLO services to be available.
The change configures terraform (in slo_services.tf) to provision SLO service instances and makes additional changes to use the new resources instead of data that was generated by slo_service module.

This change will be available in the version 0.9.4

🛠️ Fixes #1063

minherz added 4 commits April 30, 2024 16:24
Modify and apply kustomize config in a temp folder instead of using in-place changes.
fix error behavior of collecting public IP when ASM is installed.
because known SLO services are no longer auto-created, add provisioning of SLO services.
use CLUSTER_ISTIO as service type.
modify SLO provisioning to use the new added resource.
modify alert provisioning to use the added SLO services resources.
add location parameter to monitoring module.
Refresh the list of input arguments
@minherz minherz self-assigned this Apr 30, 2024
@minherz minherz marked this pull request as ready for review April 30, 2024 23:46
@minherz minherz merged commit 4ff3fa1 into release/0.9 May 1, 2024
7 of 9 checks passed
@minherz minherz deleted the minherz/fix-slo-service-creation branch May 1, 2024 00:00
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant