search

openshift / oauth-proxy

A reverse proxy that provides authentication with OpenShift via OAuth and Kubernetes service accounts
MIT License
261 stars 136 forks source link

Is there an updated location for the published image of this project? #231

Closed nate-duke closed 1 year ago

nate-duke commented 2 years ago

The README.md references registry.svc.ci.openshift.org/ci/oauth-proxy:v1 which doesn't resolve:

$ podman pull registry.svc.ci.openshift.org/ci/oauth-proxy:v1
Trying to pull registry.svc.ci.openshift.org/ci/oauth-proxy:v1...
  Get "https://registry.svc.ci.openshift.org/v2/": dial tcp: lookup registry.svc.ci.openshift.org: no such host
Error: Error initializing source docker://registry.svc.ci.openshift.org/ci/oauth-proxy:v1: error pinging docker registry registry.svc.ci.openshift.org: Get "https://registry.svc.ci.openshift.org/v2/": dial tcp: lookup registry.svc.ci.openshift.org: no such host

Is it perhaps on quay.io somewhere? If so is it public or locked up behind a license?

nate-duke commented 2 years ago

i did find: https://quay.io/repository/openshift/origin-oauth-proxy but this seems to be missing the v3.11 era tags. e.g. openshift-ansible has at least the openshift_logging_defaults role that refers to v1.1.0

https://github.com/openshift/openshift-ansible/blob/release-3.11/roles/openshift_logging_defaults/defaults/main.yml#L12

openshift-bot commented 2 years ago

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

nate-duke commented 2 years ago

/remove-lifecycle stale

openshift-bot commented 2 years ago

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

openshift-bot commented 2 years ago

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten /remove-lifecycle stale

nate-duke commented 2 years ago

/remove-lifecycle rotten

nate-duke commented 2 years ago

/remove-lifecycle stale

openshift-bot commented 2 years ago

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

openshift-bot commented 1 year ago

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten /remove-lifecycle stale

openshift-bot commented 1 year ago

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen. Mark the issue as fresh by commenting /remove-lifecycle rotten. Exclude this issue from closing again by commenting /lifecycle frozen.

/close

openshift-ci[bot] commented 1 year ago

@openshift-bot: Closing this issue.

In response to [this](https://github.com/openshift/oauth-proxy/issues/231#issuecomment-1287543744): >Rotten issues close after 30d of inactivity. > >Reopen the issue by commenting `/reopen`. >Mark the issue as fresh by commenting `/remove-lifecycle rotten`. >Exclude this issue from closing again by commenting `/lifecycle frozen`. > >/close 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.
nate-duke commented 10 months ago

thanks bot! this is still a problem btw, those ansible playbooks stil refer to image: docker.io/openshift/oauth-proxy:v1.1.0