-
Notifications
You must be signed in to change notification settings - Fork 42
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
NFD Operator on OperatorHub not installing #54
Comments
Hi @madorn , could you try the namescpace-scoped branch?, although it has been merged now into master, it had the fix for the SCC API issue |
@ArangoGutierrez Hi Carlos, thank you!! can we can get this change committed to the image that currently resides in OpenShift 4x? It is located at If you need assistance pushing the commit there, happy to help! |
is now on master, we can close this issue |
@ArangoGutierrez Thanks Carlos. Will the built image be pushed here?: https://access.redhat.com/containers/?tab=tags#/registry.access.redhat.com/openshift4/ose-cluster-nfd-operator |
Heya @madorn , is it working for you? or do we need some extra work here :) |
I'm experiencing the a similar issue when installing through the web console on openshift. |
Yes it is working now! |
Justin, I don't think Node Discovery will run on CRC.....needs to be multi-node environment, i.e. master and work nodes properly labeled. |
Is this expected to work on vanilla kubernetes? I get the same error as originally reported. |
@mythi how did you install the Operator on the vanilla kubernetes cluster? Is OLM installed in the cluster? |
@madorn I used |
@madorn ah, thanks I had that missing but even with that the same error occurs:
|
@mythi The Operator you are attempting to install only works on an OpenShift environment - you can see the Operator is looking for This endpoint is only found in Openshift environments. Because this specific issue deals with installing NFD via OperatorHub, I am going to close this issue but please open new issue and specify the type of Kubernetes distribution you are using and Kubernetes version and error. |
I can work without the operator and deploy NFD manually for now but it'd be really nice if this had the option to deploy on vanilla kubernetes too (my setup is just a barametal kubeadm install). |
Description of problem:
After installing NFD Operator, pods keep crashing.
{"level":"info","ts":1579886681.9943285,"logger":"cmd","msg":"Go Version: go1.12.12"} {"level":"info","ts":1579886681.9943712,"logger":"cmd","msg":"Go OS/Arch: linux/amd64"} {"level":"info","ts":1579886681.9943788,"logger":"cmd","msg":"Version of operator-sdk: v0.4.0+git"} {"level":"info","ts":1579886681.9950516,"logger":"leader","msg":"Trying to become the leader."} {"level":"info","ts":1579886682.1206093,"logger":"leader","msg":"Found existing lock with my name. I was likely restarted."} {"level":"info","ts":1579886682.120643,"logger":"leader","msg":"Continuing as the leader."} {"level":"info","ts":1579886682.2016144,"logger":"cmd","msg":"Registering Components."} {"level":"info","ts":1579886682.2017787,"logger":"kubebuilder.controller","msg":"Starting EventSource","controller":"nodefeaturediscovery-controller","source":"kind source: /, Kind="} {"level":"info","ts":1579886682.2019343,"logger":"kubebuilder.controller","msg":"Starting EventSource","controller":"nodefeaturediscovery-controller","source":"kind source: /, Kind="} {"level":"info","ts":1579886682.202073,"logger":"kubebuilder.controller","msg":"Starting EventSource","controller":"nodefeaturediscovery-controller","source":"kind source: /, Kind="} {"level":"info","ts":1579886682.2021816,"logger":"kubebuilder.controller","msg":"Starting EventSource","controller":"nodefeaturediscovery-controller","source":"kind source: /, Kind="} {"level":"info","ts":1579886682.20229,"logger":"kubebuilder.controller","msg":"Starting EventSource","controller":"nodefeaturediscovery-controller","source":"kind source: /, Kind="} {"level":"error","ts":1579886682.202312,"logger":"cmd","msg":"","error":"no kind is registered for the type v1.SecurityContextConstraints in scheme \"k8s.io/client-go/kubernetes/scheme/register.go:60\"","stacktrace":"github.com/openshift/cluster-nfd-operator/vendor/github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/src/github.com/openshift/cluster-nfd-operator/vendor/github.com/go-logr/zapr/zapr.go:128\nmain.main\n\t/go/src/github.com/openshift/cluster-nfd-operator/cmd/manager/main.go:92\nruntime.main\n\t/opt/rh/go-toolset-1.12/root/usr/lib/go-toolset-1.12-golang/src/runtime/proc.go:200"}
Upon first glance, controller appears to be attempting to watch
/api/v1/securitycontextconstraints
which is not available in OpenShift 4.x.The OperatorHub controller image should be updated to watch
/apis/security.openshift.io/v1/securitycontextconstraints
.The text was updated successfully, but these errors were encountered: