-
Notifications
You must be signed in to change notification settings - Fork 39
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
Error when installing m3db operator in Docker for Desktop #310
Comments
Hey @pat-wong-affirm, thanks for reaching out. It looks like we haven't cut a release since merging #302, which makes the operator compatible with Kubernetes 1.21+. Can you try using the |
unfortunately, got the same error when using image tag it's possible this error is specific to Docker for Desktop, as another team member was able to get the operator working in an EKS cluster |
I am having this issue as well |
I am also seeing this and I am also trying to deploy it on Docker for Desktop |
could this be because the api server in the desktop environment is not running as localhost? main.go sets masterURL to be 127.0.0:8001, but in the desktop environment you have: kubectl cluster-info I tried adding to bundle.yaml |
I was able to get the operator to start by passing in: (I believe only -manage-crd=false is really needed to get it to start) I do see the same errors from the controller as documented earlier periodically, but it does stay running. Trying to stand up a m3db cluster though, fails with this error: |
the m3db-operator seems to use interfaces that are no longer supported (k8s v1.22+): see: storageos/cluster-operator#348 Server Version: version.Info{Major:"1", Minor:"22" |
Would a fix be to change that to |
Hi,
Partly, I have a diff to 4 files that changes v1beta1 to v1, but I haven't
had a chance to build and test it yet
…On Tue, Mar 29, 2022 at 9:19 PM kendrickclark ***@***.***> wrote:
Would a fix be to change that to ApiextensionsV1()
—
Reply to this email directly, view it on GitHub
<#310 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAALESIJB7UFEHYSILVW3DLVCO2ZRANCNFSM5MIPM3HA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Tried to do a build with my changes, but found that the .ci directory is empty, so the build fails because it cannot find go-build-ldflags.sh and common.mk Any reason they are not in the source tree? Answered my own question - found the scripts in the m3db/ci-scripts repo |
@larsf Any luck there? |
schallert , Unfortunately this does not resolve the issue. |
Kubernetes version i am also facing similar issue on eks while installing operator using following command.
error:
|
using operator image tag 0484dcc instead of 1.13.0 works for me. but it seems it has some security issues. wish it will gets resolved with 1.14.0 |
Thanks for opening an issue for the M3DB Operator! We'd love to help you, but we need the following information included
with any issue:
master
, please include the gitSHA logged when the operator first starts.
manifest = https://raw.githubusercontent.com/m3db/m3db-operator/master/bundle.yaml
docker image tag =
quay.io/m3db/m3db-operator:latest
also tried with docker image tag being
v0.13.0
, same resultkubectl version
.MacOS - Docker For Desktop - built-in kubernetes
Install the m3db operator
Operator pod would be in
Running
stateThe text was updated successfully, but these errors were encountered: