[jboss-jira] [JBoss JIRA] (WFWIP-164) Multiple Operator CRDs on one shared cluster

[Petr Kremensky (Jira)]

     [ https://issues.jboss.org/browse/WFWIP-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Petr Kremensky closed WFWIP-164.
--------------------------------
    Resolution: Won't Fix


> Multiple Operator CRDs on one shared cluster
> --------------------------------------------
>
>                 Key: WFWIP-164
>                 URL: https://issues.jboss.org/browse/WFWIP-164
>             Project: WildFly WIP
>          Issue Type: Bug
>          Components: OpenShift
>            Reporter: Martin Choma
>            Assignee: Jeff Mesnil
>            Priority: Major
>
> For testing multiple product streams we will need to be able to have multiple CRDs definitions on one cluster. Operator pod is namespaced scoped, but Custom Resource Definition itself is cluster scope.
> I have tried to tweak definition from `WildFlyServer.wildfly.org` to `WildFlyServer.<namespace>.wildfly.org`. But operator start to complain:
> {code}
> {
>    "level": "error",
>    "ts": 1.56213363E9,
>    "logger": "kubebuilder.source",
>    "msg": "if kind is a CRD, it should be installed before calling Start",
>    "kind": "WildFlyServer.wildfly.org",
>    "error": "no matches for kind \"WildFlyServer\" in version \"wildfly.org/v1alpha1\"",
>    "stacktrace": "github.com/wildfly/wildfly-operator/vendor/github.com/go-logr/zapr.(*zapLogger).Error\n\t/Users/jmesnil/go/src/github.com/wildfly/wildfly-operator/vendor/github.com/go-logr/zapr/zapr.go:128\ngithub.com/wildfly/wildfly-operator/vendor/sigs.k8s.io/controller-runtime/pkg/source.(*Kind).Start\n\t/Users/jmesnil/go/src/github.com/wildfly/wildfly-operator/vendor/sigs.k8s.io/controller-runtime/pkg/source/source.go:89\ngithub.com/wildfly/wildfly-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Watch\n\t/Users/jmesnil/go/src/github.com/wildfly/wildfly-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:122\ngithub.com/wildfly/wildfly-operator/pkg/controller/wildflyserver.add\n\t/Users/jmesnil/go/src/github.com/wildfly/wildfly-operator/pkg/controller/wildflyserver/wildflyserver_controller.go:62\ngithub.com/wildfly/wildfly-operator/pkg/controller/wildflyserver.Add\n\t/Users/jmesnil/go/src/github.com/wildfly/wildfly-operator/pkg/controller/wildflyserver/wildflyserver_controller.go:45\ngithub.com/wildfly/wildfly-operator/pkg/controller.AddToManager\n\t/Users/jmesnil/go/src/github.com/wildfly/wildfly-operator/pkg/controller/controller.go:13\nmain.main\n\t/Users/jmesnil/go/src/github.com/wildfly/wildfly-operator/cmd/manager/main.go:103\nruntime.main\n\t/usr/local/Cellar/go/1.12.4/libexec/src/runtime/proc.go:200"
> }
> {code}
> Is it possible(safe) to relax this constraint?
> Also could we get rid of `jmesnil` part from stacktrace?



--
This message was sent by Atlassian Jira
(v7.12.1#712002)