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

Why remove --cluster-scoped support in v0.10.0? #1870

Closed
yueyongyue opened this issue Aug 30, 2019 · 6 comments
Closed

Why remove --cluster-scoped support in v0.10.0? #1870

yueyongyue opened this issue Aug 30, 2019 · 6 comments
Assignees
Labels
triage/support Indicates an issue that is a support question.

Comments

@yueyongyue
Copy link

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 here

  • Kubernetes cluster kind:

Additional context
Add any other context about the question here.

@yueyongyue
Copy link
Author

@jmrodri jmrodri added the triage/support Indicates an issue that is a support question. label Aug 30, 2019
@joelanford
Copy link
Member

@yueyongyue Support for the --cluster-scoped flag was removed in v0.8.0. See #1434 for the motivation.

However, cluster-scoped CRDs and operators are still supported. Read the operator scope documentation on the changes needed to run a cluster-scoped operator.

@yueyongyue
Copy link
Author

@joelanford Use this document, Gets a empty Namespace

@hedeesaa
Copy link

hedeesaa commented Sep 1, 2020

@joelanford
the doc is not available anymore,
Is there any other documentation?

@camilamacedo86
Copy link
Contributor

camilamacedo86 commented Sep 1, 2020

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 https://github.com/operator-framework/operator-sdk/blob/<release-tag>/doc/operator-scope.md

@hedeesaa
Copy link

hedeesaa commented Sep 11, 2020

I followed steps defined in the Doc but it didn't work properly. I get this error from operator:
{"level":"error","ts":1599826757.1276085,"logger":"helm.controller","msg":"Release failed","namespace":"","name":"example-nginx2","apiVersion":"example.com/v1alpha1","kind":"Nginx","release":"example-nginx2","error":"failed to install release: rendered manifests contain a resource that already exists. Unable to continue with install: could not get information about the resource: an empty namespace may not be set when a resource name is provided","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\tpkg/mod/github.com/go-logr/[email protected]/zapr.go:128\ngithub.com/operator-framework/operator-sdk/pkg/helm/controller.HelmOperatorReconciler.Reconcile\n\tsrc/github.com/operator-framework/operator-sdk/pkg/helm/controller/reconcile.go:181\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\tpkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:256\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\tpkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:232\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).worker\n\tpkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:211\nk8s.io/apimachinery/pkg/util/wait.JitterUntil.func1\n\tpkg/mod/k8s.io/[email protected]/pkg/util/wait/wait.go:152\nk8s.io/apimachinery/pkg/util/wait.JitterUntil\n\tpkg/mod/k8s.io/[email protected]/pkg/util/wait/wait.go:153\nk8s.io/apimachinery/pkg/util/wait.Until\n\tpkg/mod/k8s.io/[email protected]/pkg/util/wait/wait.go:88"}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage/support Indicates an issue that is a support question.
Projects
None yet
Development

No branches or pull requests

5 participants