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

Kail gets sad with oidc auth providers such as CoreOS tectonic uses #4

Closed
SEJeff opened this issue Aug 30, 2017 · 4 comments
Closed

Comments

@SEJeff
Copy link

SEJeff commented Aug 30, 2017

kubectl is definitely configured correctly:

$ kubectl get pods
NAME                                           READY     STATUS    RESTARTS   AGE
awacs-server-prod-rqworker-2710497568-7gfml    1/1       Running   0          1h
awacs-server-prod-web-751514954-1gkt5          2/2       Running   0          1h
awacs-server-prod-web-751514954-kd9hn          2/2       Running   0          1h
awacs-server-prod-web-751514954-xqvnh          2/2       Running   0          1h
awacs-server-qa-rqworker-1613750792-7z589      1/1       Running   0          1h
awacs-server-qa-web-434843186-ljgc0            2/2       Running   0          1h
awacs-server-qa-web-434843186-x270d            2/2       Running   0          1h
awacs-server-qa-web-434843186-x6tm7            2/2       Running   0          1h
awacs-splunk-agent-prod-web-1225906819-1fzhw   2/2       Running   0          1h
awacs-splunk-agent-prod-web-1225906819-q6xcn   2/2       Running   0          1h
awacs-splunk-agent-prod-web-1225906819-wczqd   2/2       Running   0          1h
awacs-splunk-agent-qa-web-214160008-g7f89      2/2       Running   0          2h
awacs-splunk-agent-qa-web-214160008-sck9p      2/2       Running   0          2h
awacs-splunk-agent-qa-web-214160008-x1vck      2/2       Running   0          2h

The current kubectl config:

$ kubectl config view --minify
apiVersion: v1
clusters:
- cluster:
    certificate-authority-data: REDACTED
    server: https://[CENSORED]:443
  name: tectonic
contexts:
- context:
    cluster: tectonic
    namespace: awacs
    user: tectonic-oidc
  name: tectonic
current-context: tectonic
kind: Config
preferences: {}
users:
- name: tectonic-oidc
  user:
    auth-provider:
      config:
        client-id: tectonic-kubectl
        client-secret: [CENSORED]
        extra-scopes: groups
        id-token: [CENSORED}
        idp-certificate-authority-data: [CENSORED]
        idp-issuer-url: https://[CENSORED]/identity
        refresh-token: [CENSORED]
      name: oidc
$ kail --context=tectonic --deploy awacs-server-qa
kail: error: Error configuring kubernetes connection: No Auth Provider found for name "oidc"
$ kail --deploy awacs-server-qa
kail: error: Error configuring kubernetes connection: No Auth Provider found for name "oidc"
@boz
Copy link
Owner

boz commented Aug 30, 2017

Bummer.

The fix is probably similar to #1.

Thanks for the report!

@SEJeff
Copy link
Author

SEJeff commented Aug 30, 2017

@boz the deployments are indeed extensions, but I think this is lower level in that it can't even auth to the cluster.

$ kubectl get deploy -o yaml | grep apiVersion:
apiVersion: v1
- apiVersion: extensions/v1beta1
- apiVersion: extensions/v1beta1
- apiVersion: extensions/v1beta1
- apiVersion: extensions/v1beta1
- apiVersion: extensions/v1beta1
- apiVersion: extensions/v1beta1

@boz
Copy link
Owner

boz commented Aug 30, 2017

@SEJeff : the extensions issue is #3, so you got that too. sadface.

I think/hope the auth issue is similar to #1 which had a simple fix: #2 (need to import a package to support that auth method).

@boz
Copy link
Owner

boz commented Aug 31, 2017

This does look like it just needs another import. See coreos/tectonic-forum#99 kubernetes/kubernetes#41532

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

No branches or pull requests

2 participants