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

Fixes panic error when TLSEnabled flag is not set #48

Merged
merged 1 commit into from
Apr 28, 2022
Merged

Fixes panic error when TLSEnabled flag is not set #48

merged 1 commit into from
Apr 28, 2022

Conversation

jjaferson
Copy link
Contributor

Closes: #39

#Verification Steps

  1. install the operator
  2. create an instance of authorino with the spec below
 kubectl create namespace myapi 

kubectl -n myapi apply -f -<<EOF
apiVersion: operator.authorino.kuadrant.io/v1beta1
kind: Authorino
metadata:
  name: authorino
spec:
  replicas: 1
  clusterWide: false
  listener:
    tls:
      certSecretRef:
        name: authorino-server-cert
  oidcServer:
    tls:
      certSecretRef:
        name: authorino-oidc-server-cert
EOF
  1. Check if the status block of the authorino CR is showing an error
 kubectl get authorino authorino -n myapi -o yaml

 ...
 status:
  conditions:
  - lastTransitionTime: "2022-04-28T15:12:21Z"
    message: 'listener secret name authorino-server-cert not found, err: Secret "authorino-server-cert"
      not found'
    reason: TlsSecretNotProvided
    status: "False"
    type: Ready

@jjaferson jjaferson merged commit 1f7bfa3 into main Apr 28, 2022
@guicassolato guicassolato deleted the panic branch September 5, 2022 15:28
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

Successfully merging this pull request may close these issues.

Operator panics when a TLS cert is provided
2 participants