-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Why remove --cluster-scoped support in v0.10.0? #1870
Comments
@yueyongyue Support for the However, cluster-scoped CRDs and operators are still supported. Read the operator scope documentation on the changes needed to run a cluster-scoped operator. |
@joelanford Use this document, Gets a empty Namespace |
@joelanford |
See; https://sdk.operatorframework.io/docs/building-operators/golang/operator-scope/ for the latest release. However, note that you can check the old docs by using the tags. E.g |
I followed steps defined in the Doc but it didn't work properly. I get this error from operator: |
Type of question
Are you asking about community best practices, how to implement a specific feature, or about general context and help around the operator-sdk?
Question
What did you do?
A clear and concise description of the steps you took (or insert a code snippet).
What did you expect to see?
A clear and concise description of what you expected to happen (or insert a code snippet).
What did you see instead? Under which circumstances?
A clear and concise description of what you expected to happen (or insert a code snippet).
Environment
operator-sdk version:
insert release or Git SHA here
Kubernetes version information:
insert output of
kubectl version
hereKubernetes cluster kind:
Additional context
Add any other context about the question here.
The text was updated successfully, but these errors were encountered: