feat: изолированное preview-окружение для PR - #12
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Ожидаемый результат
Каждый инфраструктурный pull request можно проверить в namespace
portable-agent-pr-<number>с ограничениями ресурсов и сети, используя те же Helm charts, что и будущие окружения.Что добавлено
charts/previewдля Namespace, ResourceQuota, LimitRange и default-deny NetworkPolicy;task preview:smoke PR=<number>;charts/service;Pull request preview smoke;TDD
check-preview.ps1сначала упал из-за отсутствующего preview chart;Проверено локально
helm lint --strictиhelm templateдля всех четырёх chart;check-config.ps1;task --listиgit diff --check.Runtime k3d smoke выполнит новый check этого PR, потому что локальный Docker Engine выключен.
Ограничение текущего этапа
Это ephemeral CI-preview без публичного URL. Постоянный URL, TLS и TTL-controller требуют общего Kubernetes-кластера и будут отдельным решением.