K8 Unit tests

[Philip-21]

Description

This PR fixes #

Notes for Reviewers

Signed commits

• Yes, I signed my commits.

All unit tests for k8 packages in Meshkit

K8 unit tests for describe package continuation from pr #306 and #287

[Philip-21]

@Revolyssup pls I will need the Pr to be reviewed, I feel I am really missing something in the code to make the test case work .
As you had said earlier, i created and initialized a test.yml file to be used as my meshclient.
When running the testcase it gave this error message ,
“A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.”

@Aisuko mentioned using a controller-runtime to create a response.
I'll need your review on this to continue working with the Pr

[Aisuko]

@Revolyssup pls I will need the Pr to be reviewed, I feel I am really missing something in the code to make the test case work . As you had said earlier, i created and initialized a test.yml file to be used as my meshclient. When running the testcase it gave this error message , “A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.”

@Aisuko mentioned using a controller-runtime to create a response. I'll need your review on this to continue working with the Pr

Yes, we have done this in meshery-operator as you mentioned above. For meshery/mshkit. It would be better if we can get some suggestions from @Revolyssup. As I mentioned before, please get a confirmation of the solution, after that it is good to go.

[Aisuko]

Please check the CI issues

[Philip-21]

Please check the CI issues

i have checked the ci issues it has to do with the response errors i mentioned earlier, i have pinged @Revolyssup i am still waiting for his reply and suggestions

[Revolyssup]

@Philip-21 You dont need to use ctx here as the prefix. Use the address given in test.yml

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[Aisuko]

Hi, @Philip-21 Are you still working on it?

[Philip-21]

Hi, @Philip-21 Are you still working on it?

Yes, i will create time and look into this

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue is being automatically closed due to inactivity. However, you may choose to reopen this issue.