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

k8gb crashes on malformed spec section in gslb custom resource #296

Closed
somaritane opened this issue Feb 15, 2021 · 6 comments
Closed

k8gb crashes on malformed spec section in gslb custom resource #296

somaritane opened this issue Feb 15, 2021 · 6 comments
Labels
bug Something isn't working

Comments

@somaritane
Copy link
Contributor

When gslb spec contains wrong path section for host: rule e.g:

spec:
  ingress:
    rules:
    - host: host.examle.com
       https: <==== should be http instead!
         paths:
...
  strategy:
    dnsTtlSeconds: 30
    splitBrainThresholdSeconds: 300
    type: roundRobin

this leads to panic and k8g controller crash.
Following can be seen in k8gb log

E0212 07:54:49.306061       1 runtime.go:78] Observed a panic: "invalid memory address or nil pointer dereference" (runtime error: invalid memory address or nil pointer dereference)
@somaritane somaritane added the bug Something isn't working label Feb 15, 2021
@somaritane
Copy link
Contributor Author

@kuritka
Copy link
Collaborator

kuritka commented Feb 16, 2021

@ytsarev
Copy link
Member

ytsarev commented Feb 22, 2021

Shouldn't we actually handle https as well? Especially for annotated Ingress scenario

@somaritane
Copy link
Contributor Author

somaritane commented Feb 22, 2021

Shouldn't we actually handle https as well? Especially for annotated Ingress scenario

@ytsarev, are we talking about TLS handling? If yes, tls section of Ingress spec handles that, there's no such thing as https path rule.

@ytsarev
Copy link
Member

ytsarev commented Feb 22, 2021

@somaritane ok, let's not complicate it until it is really required :D

@k0da
Copy link
Collaborator

k0da commented Feb 22, 2021

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants