You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Actually, the expected behavior is that the application should be possible to delete regardless of any invalid elements in the spec. However the expected behavior describe above is still true
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 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-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
The text was updated successfully, but these errors were encountered: