User tried to delete app in Console, but nothing happened.
https://nav-it.slack.com/archives/C5KUST8N6/p1725951754452269
Running kubectl describe app ds-api we saw the following event
Application.nais.io "ds-api" is invalid: spec.gcp.sqlInstances[0].tier: Invalid value: "": spec.gcp.sqlInstances[0].tier in body should match 'db-.+'
So the tier was missing, and spec was invalid.
This resulted in kubectl delete app ds-api hanging indefinitely.
When removing the failing spec, the application was deleted as expected.
Another similar issue:
https://nav-it.slack.com/archives/C5KUST8N6/p1724998208664699
Expected behavior:
The invalid spec should never have been accepted in the first place, or changes made to naiserator regarding tier (if this was done after this spec was already accepted) should have cleaned this up.
Edit: ☝️ https://nav-it.slack.com/archives/C01DE3M9YBV/p1724141273103439 seems to have introduced this
User tried to delete app in Console, but nothing happened.
https://nav-it.slack.com/archives/C5KUST8N6/p1725951754452269
Running
kubectl describe app ds-apiwe saw the following eventApplication.nais.io "ds-api" is invalid: spec.gcp.sqlInstances[0].tier: Invalid value: "": spec.gcp.sqlInstances[0].tier in body should match 'db-.+'So the tier was missing, and spec was invalid.
This resulted in
kubectl delete app ds-apihanging indefinitely.When removing the failing spec, the application was deleted as expected.
Another similar issue:
https://nav-it.slack.com/archives/C5KUST8N6/p1724998208664699
Expected behavior:
The invalid spec should never have been accepted in the first place, or changes made to naiserator regarding tier (if this was done after this spec was already accepted) should have cleaned this up.
Edit: ☝️ https://nav-it.slack.com/archives/C01DE3M9YBV/p1724141273103439 seems to have introduced this