Repository navigation
[release-6.6] test: deploy loki operator once per lokistack e2e suite - #3549
Conversation
Apply the loki-e2e-deploy-operator-once changes to release-6.6: - deploy the loki operator once per suite (BeforeSuite/AfterSuite) instead of per-spec, and skip install when the deployment already exists, waiting for it to become available instead - gate WaitForLokistackReady on the LokiStack Ready condition, failing fast on GET errors other than NotFound - stabilize the lokistack OTLP e2e against ingestion rate limits: slower log generator, higher ingestion limits, and console labels so OTLP-mode queries can use k8s_* stream selectors - narrow HasApplicationLogs with optional stream label matchers Also bump the default loki operator channel to stable-6.6 in the test framework and the Makefile export; release-6.6 still defaulted to stable-6.4 in both. Co-Authored-By: Claude Code <noreply@anthropic.com>
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jcantrill The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
Bot
added
the
approved
|
/test e2e-target |
|
/override ci/prow/functional-target as does not affect this change. functional test resolved with merger #3517 |
|
@jcantrill: Overrode contexts on behalf of jcantrill: ci/prow/functional-target DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
/label verified |
openshift-ci
Bot
added
the
verified
|
/lgtm |
|
/retest-required |
1 similar comment
|
/retest-required |
|
/test images |
|
/retest-required |
|
/label verified |
|
@jcantrill: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
1b4ef38
into
openshift:release-6.6
What
Backport of #3543 to release-6.6.
BeforeSuite/AfterSuite) instead of redeploying it in every spec'sBeforeEach, and skip install when the operator deployment is already available.WaitForLokistackReadyon the LokiStackReadycondition, failing fast on GET errors other than NotFound.k8s_*stream selectors).HasApplicationLogswith optional stream label matchers.stable-6.6in the test framework and the Makefile export; release-6.6 still defaulted tostable-6.4in both (master's dbfd9ed bump was never backported).Why
Reinstalling/uninstalling the operator for each spec is wasteful and slow, and the per-spec cleanup could delete an operator it did not create. Backporting aligns the release-6.6 e2e with master and points it at the 6.6 loki operator channel for z-stream testing.
Testing
go vet ./test/framework/e2e/... ./test/e2e/logforwarding/lokistack/...passes on this branch.🤖 Generated with Claude Code