As someone already mentioned, it's a pitty that you didn't cover the networking part. Your videos really add value to remembering how to tackle certain matters.
that wow moment, when we're still in doubt, but it confirmed✅ with our solutiin.. 😂.... awsome senior we want more examples where can we get these typenof questions. please let me know.
you did not cover the troubleshooting for networking part which is crucial to get through one of the troubleshooting problems. Anyway, other parts for troubleshooting are good. Keep it up !
In the question mention, don't make any changes in resources. But you changed the resource in dc. After it's produced output. So it's correct solution? Please explain
I agree, I was waiting for another way to tackle the issue without changing the deploy configuration. I think, applying a project limit range would be a good solution for that
You make change in the resources, even if it was indicated not to do so
As someone already mentioned, it's a pitty that you didn't cover the networking part. Your videos really add value to remembering how to tackle certain matters.
that wow moment, when we're still in doubt, but it confirmed✅ with our solutiin.. 😂.... awsome senior we want more examples where can we get these typenof questions. please let me know.
you did not cover the troubleshooting for networking part which is crucial to get through one of the troubleshooting problems. Anyway, other parts for troubleshooting are good. Keep it up !
Is knowledge of NetworkPolicies enough to fix it?
In the question mention, don't make any changes in resources. But you changed the resource in dc. After it's produced output. So it's correct solution? Please explain
I agree, I was waiting for another way to tackle the issue without changing the deploy configuration. I think, applying a project limit range would be a good solution for that