Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deprecation Notice for Service Binding Operator #7254

Open
jeffgus opened this issue Jun 25, 2024 · 1 comment
Open

Deprecation Notice for Service Binding Operator #7254

jeffgus opened this issue Jun 25, 2024 · 1 comment
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/*` and requires one.

Comments

@jeffgus
Copy link

jeffgus commented Jun 25, 2024

/kind bug

The odo add binding command requires the Service Binding Operator, but the page shows that the operator has been deprecated as of Feb 2024.

What versions of software are you using?

Operating System:
Fedora 40

Output of odo version:
odo v3.16.1 (cd346c5-nightly)

Server: https://xxxxxxxxxxxxxxxxxx:6443
OpenShift: 4.14.27
Kubernetes: v1.27.13+048520e
Podman Client: 5.1.1

How did you run odo exactly?

odo add binding

Actual behavior

✗ Service Binding Operator is not installed on the cluster, please ensure it is installed before proceeding. See installation instructions: https://odo.dev/docs/command-reference/add-binding#installing-the-service-binding-operator

Expected behavior

I can install the operator, but should I since it is now deprecated?

@openshift-ci openshift-ci bot added the kind/bug Categorizes issue or PR as related to a bug. label Jun 25, 2024
@github-actions github-actions bot added the needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. label Jun 25, 2024
@jeffgus
Copy link
Author

jeffgus commented Jun 25, 2024

I installed https://github.com/servicebinding/runtime which appears to be the replacement for the operator, but odo doesn't recognize it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/*` and requires one.
Projects
Status: No status
Development

No branches or pull requests

1 participant