Skip to content

issues Search Results · repo:ccojocar/sso-operator language:Go

Filter by

18 results
 (116 ms)

18 results

inccojocar/sso-operator (press backspace or delete to remove)

ccojocar/sso-operator
SSO Operator crashes in K8s 1.22

After upgrading cluster version to 1.22 we found SSO-operator ends up in crashing-loop with following error log: time= 2023-05-03T12:28:43Z level=error msg= failed to register the SSO CRD: the server ...
  • zhenfangwg2
  • 1
  • Opened 
    on May 3, 2023
  • #62

ccojocar/sso-operator
helm chart cannot be installed on Kubernetes >= 1.16

The helm chart uses deprecated Kubernetes APIs, and can therefore not be installed on newer Kubernetes versions. https://kubernetes.io/blog/2019/07/18/api-deprecations-in-1-16/
  • fmotrifork
  • Opened 
    on Sep 28, 2020
  • #59

ccojocar/sso-operator
Update the dependencies to a newer version

The kubernetes client-go and operator framework dependencies needs to be updated.
  • ccojocar
  • Opened 
    on May 14, 2020
  • #58

ccojocar/sso-operator
Add ability to skip proxy creation

I see there s already a step to skip the exposure of a service. Would it also be possible to skip creating a proxy? What if we just want something that creates dex clients for us?
lifecycle/stale
  • snuggie12
  • 1
  • Opened 
    on Mar 24, 2020
  • #53

ccojocar/sso-operator
Operator seems to only create one secret per namespace?

If all of the proxies use the same secret, then that means you can only have one sso per namespace? That can t be correct can it?
  • empath75
  • Opened 
    on Nov 1, 2019
  • #44

ccojocar/sso-operator
Will only use first host on ingress to configure oauth proxy

See https://github.com/jenkins-x/sso-operator/blob/c561ba6b9b3caeaf7f9c19bd9fe90f24003d85dc/pkg/proxy/proxy.go#L394 - this means that if you specify multiple ingress hosts only the first one will survive ...
lifecycle/rotten
  • pmuir
  • 4
  • Opened 
    on Oct 26, 2019
  • #43

ccojocar/sso-operator
Add some docs how to set up manually an ingress rule

The expose job can now be disable in the sso resource by setting the skipExposeService: true. This will require in addition to set up an ingress resource manually. Document how to define this ingress ...
  • ccojocar
  • 4
  • Opened 
    on Aug 22, 2019
  • #40

ccojocar/sso-operator
sso-operator fails to create sso proxy expose job if the name is more than 63 chars

Descriptions: Trying to enable sso for a preview environment, the generated name for the SSO proxy expose job is too long (more than 63 chars) and so the sso-operator fails to create the expose job. The ...
  • romainverduci
  • 2
  • Opened 
    on Mar 29, 2019
  • #24

ccojocar/sso-operator
Add ingress config options to SSO spec

I need the ability to NOT set certmanager.k8s.io/issuer annotation on the ingress. I m using a cert-manager cluster issuer with dns01 defaults set so all my ingress needs is the single kubernetes.io/tls-acme: ...
  • brunnels
  • 2
  • Opened 
    on Feb 16, 2019
  • #22

ccojocar/sso-operator
Support ingresses annotations and default config

I d love to be able to add SSO to a Ingress only by adding annotations in my ingresses. It could then use the config I saved in the initial sso-operator deployment as default to create a SSO resource (or ...
lifecycle/stale
  • aslafy-z
  • 4
  • Opened 
    on Jan 28, 2019
  • #20
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! 
Restrict your search to the title by using the in:title qualifier.
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! 
Restrict your search to the title by using the in:title qualifier.
Issue search results · GitHub