cloud-computing

What problem are you facing?

Inconsistent naming, --poll in providers and --poll-interval in core crossplane:

provider-aws - --poll

https://github.com/crossplane/provider-aws/blob/cb08893011212fc6858434f84695fecc0a824629/cmd/provider/main.go#L40

crossplane core - --poll-interval

https://github.com/crossplane/crossplane/blob/c0de80c1ea2102b9569754d78bea292c46e6292

Join our new Discord Channel to say Hi and get live support from the team or from the community.

Is your feature request related to a problem? Please describe.
The possibility to disable an incoming peering with liqoctl.

Describe the solution you'd like
A simple liqoctl subcommand to disable the incoming peering for this cluster, to stop the resource sharing and remove the pod scheduled by the remote cluster on the local one.

Describe the feature

Current Node Resource Controller update Kubernetes node ext resource with the predicted idle resource, all idle resources will be reallocated as ext resource which can be used by lower priority pods, especially for offline job, however this would leads the node resource to be exhausted, thus some of them would be evicted during the the execution.
So the request is to make

What would you like to be enhanced
Delete the following file.
https://github.com/cloud-barista/cb-tumblebug/blob/main/src/testclient/scripts/sequentialFullTest/deploy-weavescope-to-multi-mcis-update-noinstall.sh

Why is this needed
We do not need `deploy-weavescope-to-multi-mcis-update

Currently the machine sizes start at (and default to) m. This is fine, and a sane default for the intended use case, but not everyone needs (to pay for) 8 cores and 16GB of RAM to do something basic (like prototyping DVC/SSH features).

Right now the user can just manually specify something like aws + t2.micro ourselves but it defeats the purpose of having a generalized solution if the user