kubernetes / apiserver

Library for writing a Kubernetes-style API server.
Apache License 2.0
647 stars 400 forks source link

OIDC errors #88

Closed sohnaeo closed 1 year ago

sohnaeo commented 1 year ago

Hi ,

I have enabled OIDC in api-server, it is working fine and user can get authenticated fine through OIDC but getting below errors in the logs, am not sure what are these for? Google didnt help much

E0929 11:12:31.421256 1 oidc.go:335] oidc authenticator: initializing plugin: 404 Not Found: E0929 11:12:41.421781 1 oidc.go:335] oidc authenticator: initializing plugin: 404 Not Found: E0929 11:12:51.422139 1 oidc.go:335] oidc authenticator: initializing plugin: 404 Not Found: E0929 11:13:01.422124 1 oidc.go:335] oidc authenticator: initializing plugin: 404 Not Found: E0929 11:13:11.421506 1 oidc.go:335] oidc authenticator: initializing plugin: 404 Not Found: E0929 11:13:21.422327 1 oidc.go:335] oidc authenticator: initializing plugin: 404 Not Found:

Below are my OIDC parameters in kube-apiserver.yml

- --oidc-client-id=k8s-user - --oidc-groups-claim=groups - --oidc-issuer-url=https://xxxxxxxxxxxx/openam/oauth2/k8s-custer - --oidc-username-claim=subname

k8s-triage-robot commented 1 year ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 1 year ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot commented 1 year ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

k8s-ci-robot commented 1 year ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes/apiserver/issues/88#issuecomment-1445357108): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages issues according to the following rules: >- After 90d of inactivity, `lifecycle/stale` is applied >- After 30d of inactivity since `lifecycle/stale` was applied, `lifecycle/rotten` is applied >- After 30d of inactivity since `lifecycle/rotten` was applied, the issue is closed > >You can: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.