How to install dependent operator using OLM way

[tbhagwat16]

Type of question How to install dependent operator using OLM way

Hi All, Sorry if this question is already asked, but I have checked google and github but did not get the required answer. My operator A is dependent on operator B and C. Before operator A gets install, I want to install operator B and C.

I have defined dependencies.yaml under bundle/metadata folder but what to do next? I am not getting the steps on google.

Thank you in advance.

Question

What did you do?

Hi All, Sorry if this question is already asked, but I have checked google and github but did not get the required answer. My operator A is dependent on operator B and C. Before operator A gets install, I want to install operator B and C.

I have defined dependencies.yaml under bundle/metadata folder but what to do next? I am not getting the steps on google.

Thank you in advance.

What did you expect to see?

Whatever I have defined in the dependecies.yaml is getting reflected in operator CSV and when I try to install operator A, operator B and C should get installed.

What did you see instead? Under which circumstances?

No changes in CSV and installation

Environment

Operator type:

Kubernetes cluster type:

Openshift

tejshribhagwat@Tejshris-MacBook-Pro Documents % operator-sdk version
operator-sdk version: "v1.38.0", commit: "0735b20c84e5c33cda4ed87daa3c21dcdc01bb79", kubernetes version: "v1.30.0", go version: "go1.23.3", GOOS: "darwin", GOARCH: "arm64"
tejshribhagwat@Tejshris-MacBook-Pro Documents % go version
go version go1.23.4 darwin/arm64
tejshribhagwat@Tejshris-MacBook-Pro Documents % kubectl version
Client Version: v1.32.0
Kustomize Version: v5.5.0
error: You must be logged in to the server (the server has asked for the client to provide credentials)

Additional context

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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.