Viswajith Venugopal

> It's not clear to me if kube launched the pod with low memory, or merely failed to launch at all due to the invalid configuration. It seems like the...

Hi @tspearconquest, thanks for filing this issue. I will admit I've never seen a deployment definition without a pod spec. How does that work? If you `kubectl create` that, will...

But how does it know what image to create, for example?

Ohh, got it. I was really confused. 😅 Here's a very minimal example I put together. In this example, `kube-linter` does _not_ flag the service as a dangling service. You...

Can you help me modify this example so as to reproduce the problem you're seeing?

Hmm, it should understand that it is part of the same context, and it does. I just tested it that way: ``` viswa:~/kube-linter-demo/yamls/temp (docker-desktop)$ ls dep.yaml svc.yaml viswa:~/kube-linter-demo/yamls/temp (docker-desktop)$ cat...

> Your svc.yaml contains the deployment a second time... Ah, my bad. I just fixed and retried. Same result though... ``` viswa:~/kube-linter-demo/yamls/temp (docker-desktop)$ ls dep.yaml svc.yaml viswa:~/kube-linter-demo/yamls/temp (docker-desktop)$ cat dep.yaml...

Aha! Yes, that is indeed working as expected. Your use-case is valid, though, so let's figure out how to solve for it. Some background: `kube-linter` currently assumes that all YAMLs...

Hmm, what would that look like in this case? It feels like that would require a lot more effort than option 1? To clarify, with option 1, I'm envisioning that...

Hi @tspearconquest, sorry, there hasn't. I expect to be done with this by the end of this week.