Concierge should support OpenShift clusters
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 739
- Forks
- 85
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 1
Description
Given I have an Openshift 4.x cluster
When I install the Pinniped Concierge following website docs
Then I see that it installs correctly
And I see that the CredentialIssuer enters a successful status
And when I configure a Concierge-based login
Then the login succeeds
Notes
Is your feature request related to a problem? Please describe.
Pinniped should work on OpenShift clusters.
Describe the solution you'd like
The location of the signing key is different in OpenShift clusters. We should simply be able to get it from the Kube API at a specific location without needing to run a pod (there is an operator that runs the KCM static pods and it has all the secrets in the Kube API before rendering the static pod manifests).
- How will this project improvement be tested?
Run it on OpenShift and make sure auth works.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Concierge installation flow described in the website docs and trace how the CredentialIssuer obtains the signing key. Investigate the Kubernetes API location used by OpenShift and how the current pod-based lookup differs. Done means Concierge installs on an OpenShift 4.x cluster, the CredentialIssuer reaches a successful status, and Concierge-based login succeeds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- authentication, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100