Change API from 'Google API Client' to 'Google Cloud Python Client'

[pablomh]

According to the 'Google API Client' GH page:

This library is considered complete and is in maintenance mode. This means
that we will address critical bugs and security issues but will not add any
new features.

This library is officially supported by Google. However, the maintainers of
this repository recommend using Cloud Client Libraries for Python, where
possible, for new code development.

So change the code accordingly to adapt it to 'Google Cloud Python Client'.

[paigerube14]

Not sure if this is part of what you added but at the end of the scenario i got this error

2024-10-23 17:56:45,901 [INFO] Node with instance ID: prubenda-4185-c8qj7-worker-b-mqtcq has been rebooted
2024-10-23 17:56:45,902 [INFO] node_reboot_scenario has been successfuly injected!
2024-10-23 17:56:46,556 [ERROR] 'namespace'

[pablomh]

Not sure if this is part of what you added but at the end of the scenario i got this error

2024-10-23 17:56:45,901 [INFO] Node with instance ID: prubenda-4185-c8qj7-worker-b-mqtcq has been rebooted
2024-10-23 17:56:45,902 [INFO] node_reboot_scenario has been successfuly injected!
2024-10-23 17:56:46,556 [ERROR] 'namespace'

I took a look and this comes from here:

krkn/krkn/utils/functions.py

Line 74 in 462c9ac

namespaces.extend(krkn_lib.utils.deep_get_attribute("namespace", scenario_config))

There's no namespace in any of the example config files (nor in the one I used and probably the one you used as well), so it complains about it.

[paigerube14]

/lgtm

[paigerube14]

@pablomh any updates on this PR? I am hitting an issue with the node scenarios on GCP and wonder if this PR will help fix it/get around it since its using a different library

#740

[pablomh]

I'll be able to keep working on it tomorrow, so keep tuned and let me know if I can help you with your issue.

[paigerube14]

/lgtm

[pablomh]

Btw, @paigerube14, have you been able to test if this PR fixes #740 for you?

I've just installed a 4.17 cluster and haven't been able to reproduce it.

[paigerube14]

Btw, @paigerube14, have you been able to test if this PR fixes #740 for you?

I've just installed a 4.17 cluster and haven't been able to reproduce it.

With these changes I also wasn't able to reproduce the issue. Thinking this fixes it!