Skip to content

Adding Loki deployment role#3790

Open
lnatapov wants to merge 1 commit intoopenstack-k8s-operators:mainfrom
lnatapov:Addin_ck_deployment_files
Open

Adding Loki deployment role#3790
lnatapov wants to merge 1 commit intoopenstack-k8s-operators:mainfrom
lnatapov:Addin_ck_deployment_files

Conversation

@lnatapov
Copy link

@lnatapov lnatapov commented Mar 23, 2026

This role will deploy Loki operator and Minio for CloudKitty

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 23, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign yorabl for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 23, 2026

Hi @lnatapov. Thanks for your PR.

I'm waiting for a openstack-k8s-operators member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Tip

We noticed you've done this a few times! Consider joining the org to skip this step and gain /lgtm and other bot rights. We recommend asking approvers on your previous PRs to sponsor you.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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.

@softwarefactory-project-zuul
Copy link

Build failed (check pipeline). Post recheck (without leading slash)
to rerun all jobs. Make sure the failure cause has been resolved before
you rerun jobs.

https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/34687bb83c6d45bc9ecb9f9a16a6d419

✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 24m 32s
✔️ podified-multinode-edpm-deployment-crc SUCCESS in 1h 18m 50s
✔️ cifmw-crc-podified-edpm-baremetal SUCCESS in 1h 26m 08s
✔️ cifmw-crc-podified-edpm-baremetal-minor-update SUCCESS in 2h 10m 54s
cifmw-pod-zuul-files FAILURE in 5m 09s
✔️ noop SUCCESS in 0s
✔️ cifmw-pod-ansible-test SUCCESS in 9m 06s
✔️ cifmw-pod-pre-commit SUCCESS in 8m 57s
✔️ cifmw-molecule-deploy_loki SUCCESS in 1m 37s

@lnatapov lnatapov force-pushed the Addin_ck_deployment_files branch from fe3741c to 021fd5c Compare March 23, 2026 23:17
@softwarefactory-project-zuul
Copy link

Build failed (check pipeline). Post recheck (without leading slash)
to rerun all jobs. Make sure the failure cause has been resolved before
you rerun jobs.

https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/a00a31aaec0e4ee9a062fa4a635f468a

✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 45m 10s
✔️ podified-multinode-edpm-deployment-crc SUCCESS in 1h 22m 38s
✔️ cifmw-crc-podified-edpm-baremetal SUCCESS in 1h 31m 25s
cifmw-crc-podified-edpm-baremetal-minor-update RETRY_LIMIT in 27m 15s
✔️ cifmw-pod-zuul-files SUCCESS in 6m 09s
✔️ noop SUCCESS in 0s
✔️ cifmw-pod-ansible-test SUCCESS in 10m 03s
✔️ cifmw-pod-pre-commit SUCCESS in 9m 36s
✔️ cifmw-molecule-deploy_loki SUCCESS in 1m 36s

@vyzigold
Copy link
Contributor

/ok-to-test

@softwarefactory-project-zuul
Copy link

Merge Failed.

This change or one of its cross-repo dependencies was unable to be automatically merged with the current state of its repository. Please rebase the change and upload a new patchset.
Warning:
Error merging github.com/openstack-k8s-operators/ci-framework for 3790,75e4a49e603e9675f46ef7b49597782dc960c6f7

@lnatapov lnatapov force-pushed the Addin_ck_deployment_files branch from 75e4a49 to 9222e31 Compare March 24, 2026 10:50
Comment on lines +36 to +40
kind: Pod
metadata:
labels:
app: minio
name: minio
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am working on the backup/restore feature and also needs minio for this. wondering if we should extract it into a dedicated role, to be reusable and use the same deployment, or if we keep it separate and run two instances, which can be different namespaces.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants