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
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 byslo_service
module.This change will be available in the version 0.9.4
🛠️ Fixes #1063