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

Unable to authenticate private repository #75379

Open
ddebrecenijr opened this Issue Mar 14, 2019 · 3 comments

Comments

Projects
None yet
3 participants
@ddebrecenijr
Copy link

ddebrecenijr commented Mar 14, 2019

What happened:
Attempting to use secrets to authenticate for my deployments on a local cluster does not work correctly.
Using imagePullSecrets does not appear to do anything, whether creating it directly from docker/config.json or inputting credentials manually.

What you expected to happen:
Secrets should authenticate private repositories as described in documentation.

How to reproduce it (as minimally and precisely as possible):
Setup minimal cluster via kubeadm running Ubuntu Server master and Windows Server node.

Anything else we need to know?:
Nodes are all Windows based.

Environment:

  • Kubernetes version (use kubectl version):
    Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.3", GitCommit:"2bba0127d85d5a46ab4b778548be28623b32d0b0", GitTreeState:"clean", BuildDate:"2018-05-21T09:17:39Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"windows/amd64"}
    Server Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.4", GitCommit:"c27b913fddd1a6c480c229191a087698aa92f0b1", GitTreeState:"clean", BuildDate:"2019-02-28T13:30:26Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}
  • Cloud provider or hardware configuration: Virtual Machines
  • OS (e.g: cat /etc/os-release): Master: Ubuntu Server 18.04, Nodes: Windows Server 1809
  • Kernel (e.g. uname -a): Linux 4.15.0-46-generic
  • Install tools: kubeadm
  • Others:
    /sig node
    /sig windows
@neolit123

This comment has been minimized.

Copy link
Member

neolit123 commented Mar 17, 2019

Install tools: kubeadm

kubeadm is not supported on Windows ATM.
can you provide feedback of how are you setting this up using kubeadm?

Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.3", GitCommit:"2bba0127d85d5a46ab4b778548be28623b32d0b0", GitTreeState:"clean", BuildDate:"2018-05-21T09:17:39Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"windows/amd64"}

the client is way outdated compared to the server. try upgrading to 1.13.

@ddebrecenijr

This comment has been minimized.

Copy link
Author

ddebrecenijr commented Mar 18, 2019

The versioning is my bad, the master and all nodes are on v1.13.4. The client was my kubectl version that I was using for cli commands.
As for kubeadm, I followed the guidelines outlined here by Microsoft Docs, I am using a host-gw flannel network, for creating the secrets I followed both ways outlined and my private repository is the standard docker registry image, i think like registry:2.7 or something like that.
Out of curiosity, where are you finding that kubeadm is not supported for Windows? From my understanding (still new to this), kubeadm is the only tool available right now for supporting windows nodes to join clusters via #53553

@neolit123

This comment has been minimized.

Copy link
Member

neolit123 commented Mar 18, 2019

thanks for the details,

it was mentioned to me recently that kubeadm no longer works correctly on Windows nodes, but i have no means to test this ATM.

...it used to work a couple of years ago.

here is the tracking issue for kubeadm to get this working correctly again in 1.15 (hopefully):
kubernetes/kubeadm#1393

if you find kubeadm / windows problems, please report them in that ticket.

Attempting to use secrets to authenticate for my deployments on a local cluster does not work correctly. Using imagePullSecrets does not appear to do anything, whether creating it directly from docker/config.json or inputting credentials manually.

seems like SIG Windows will have to respond to the original issue about the registry and imagePullSecrets.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.