Matthew

> I fixed all nodeClaims manually with a script populating the missing "reason" and "message" fields. But still, there is smth wrong with the CRD upgrade. I wonder whether we...

> > I fixed all nodeClaims manually with a script populating the missing "reason" and "message" fields. But still, there is smth wrong with the CRD upgrade. I wonder whether...

> hi im also running into issue with error > > The CustomResourceDefinition "nodepools.karpenter.sh" is invalid: status.storedVersions[1]: Invalid value: "v1": must appear in spec.versions > The CustomResourceDefinition "nodeclaims.karpenter.sh" is invalid:...

I'm having the exact same issue with the exact issue with the latest version on Obsidian (Version 1.6.5 (Installer 1.6.5)).

> @metheu could you please provide the versions of Kong and Kong ingress controller before/after the issue happens? Also, different consumers in different [Kong workspaces](https://docs.konghq.com/gateway/latest/kong-enterprise/#workspaces) not different k8s namespaces can...

@randmonkey can you please elaborate on the difference between these 2 components? We have deployed in a separate namespace(named `kong`) 2 pods with 3 containers - `ingress-controller`, `proxy` and `clear-stale-pid`(init-container)....

@randmonkey hey, did you have time to look into this? What can we do to try and diagnose the issue?