operator-sdk

operator-sdk copied to clipboard

Feature Request

Describe the problem you need a feature to resolve.

operator-sdk olm install (and other commands) uses the default context, there doesn't seem to be any clear way to switch to a different context (when for example installing in multiple clusters)

The only solution I have found is to copy the kube config file, change the default context in the copy then run the operator-sdk after setting the KUBECONFIG environment variable run the operator-sdk command which picks up the new context

Describe the solution you'd like.

the operator-sdk run command supports the --kubecontext flag, this could be added to the operator-sdk olm (install / upgrade / uninstall)

Seems reasonable, @atimgraves would you be interested in adding this functionality?

Hi There I don't have any experience with coding in go (my background is Java). I'll have a look, but don't think I have the skills Thanks, Tim

On Mon, 15 Aug 2022 at 19:13, Austin Macdonald @.***> wrote:

Seems reasonable, @atimgraves https://github.com/atimgraves would you be interested in adding this functionality?

— Reply to this email directly, view it on GitHub https://github.com/operator-framework/operator-sdk/issues/5981#issuecomment-1215550301, or unsubscribe https://github.com/notifications/unsubscribe-auth/AG4VUTHPF2TAO4HH7LQZJITVZKCDPANCNFSM56BEDLZA . You are receiving this because you were mentioned.Message ID: @.***>

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

/remove-lifecycle stale

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

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

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-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/test-infra repository.