qiaozp comments

Results 117 comments of


                                            qiaozp

error message

I think maybe it's better to open a section in the last say "Trouble Shooting". WDYT @wonderflow

Resource consumption by python are not limited

@EtiennePerot Thanks for replying! We have found the problem thanks to @charlie0129. It ends up with that we didn't configure gvisor to use systemd-cgroup which is our cgroup manager in...

Feat: support custom annotations

Hi @dadav We are using helm-based ArgoCD application, and we build a platform helping us to dispatch those apps. When filling values of applications, there're fields like: ``` modelWeight: //...

If a backend is specified, an error in the `preCheck` during deletion will result in the backend becoming null

The reason of "the object has been modified" may be k8sClient got outdated Configuration in controller's cache. That is to say, someone update the object but somehow the controller didn't...

If a backend is specified, an error in the `preCheck` during deletion will result in the backend becoming null

> After IsErrBlockDeletion, what should we do next? > > Should we retry by putting it back in the queue? > return ctrl.Result{Requeue: true}, nil If return err is not...

Have configuration resources A and B that both configure the same backend，when configuration resource A is deleted, if there are other configuration resources like B referencing this backend, the terraformDestroy method should not be executed.

Then how to deal with the Configuration which has been marked as deleted (by set DeleteTimestamp)?

Have configuration resources A and B that both configure the same backend，when configuration resource A is deleted, if there are other configuration resources like B referencing this backend, the terraformDestroy method should not be executed.

So if we create the same configuration again, how this behavior will effect the consistency? Is is possible to patially delete the state in the backend?

Have configuration resources A and B that both configure the same backend，when configuration resource A is deleted, if there are other configuration resources like B referencing this backend, the terraformDestroy method should not be executed.

How do you think if we disallow user to specify the same backend as others. By adding a validation.

Have configuration resources A and B that both configure the same backend，when configuration resource A is deleted, if there are other configuration resources like B referencing this backend, the terraformDestroy method should not be executed.

That's a good idea! I've convert it to a kubevela issue. Before "shared-component" I think adding validation to prevent user from creating the same Configuration is not reasonable because you...

Have configuration resources A and B that both configure the same backend，when configuration resource A is deleted, if there are other configuration resources like B referencing this backend, the terraformDestroy method should not be executed.

I just realized specifying `componentNames` in shared-resource policy may solve your problem. Can you check that? @wujiuye