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

--kubeconfig flag ignored on proxy command #1364

Closed
astingengo opened this issue Dec 8, 2022 · 2 comments · Fixed by #1369
Closed

--kubeconfig flag ignored on proxy command #1364

astingengo opened this issue Dec 8, 2022 · 2 comments · Fixed by #1369
Assignees

Comments

@astingengo
Copy link

astingengo commented Dec 8, 2022

v4.5.5

The init command seems to work now but tenant and proxy doesn't seems to work

L.E: I think is just proxy command BUT the image from Docker can't be pulled

Failed to pull image "minio/operator:v4.5.5": rpc error: code = Unknown desc = failed to pull and unpack image "docker.io/minio/operator:v4.5.5": failed to resolve reference │
│  "docker.io/minio/operator:v4.5.5": failed to do request: Head "https://registry-1.docker.io/v2/minio/operator/manifests/v4.5.5": dial tcp: lookup registry-1.docker.io on 127.0.0.53:53: server misbehaving 

Still looking intot that to see if is something from me regarding pulling image as if manually trying it will pull it, not via Kube

proxy command not working with --kubeconfig only

LLE: pulling the image is an issue from me, proxy command remained unresolved. Thanks

@astingengo astingengo changed the title --kubeconfig flag ignored on tenant,proxy, ... commands --kubeconfig flag ignored on proxy, ... commands Dec 8, 2022
@astingengo astingengo changed the title --kubeconfig flag ignored on proxy, ... commands --kubeconfig flag ignored on proxy command Dec 8, 2022
@dvaldivia dvaldivia removed the triage label Dec 13, 2022
@dvaldivia
Copy link
Collaborator

I think @pjuarezd fixed this on #1363 unless we are also missing the proxy command, in which case we need an additional PR

@pjuarezd
Copy link
Member

The proxy command had a second call to kubernetes api missing the parameter, merely a bug

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants