qiaozp comments

Results 117 comments of


                                            qiaozp

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.

This restriction has been removed.

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'm not sure the version. But it is removed. Check the release note please.

Add `creationTimestamp` to the allow-listed set of properties of embedded ObjectMeta to prevent API warnings

For anyone seeing this, here's a code snippet that suppresses the warning. Take it or modify as your need. ```golang package log import ( "strings" "k8s.io/client-go/rest" "sigs.k8s.io/controller-runtime/pkg/log" ) var (...

[Feature Request]: Ship CUDA-enabled builds (-DUSE_CUDA=ON) for correct GPU-NIC topology detection

Hey guys, new to the community. After a non-comprehensive test on our cluster, I found with CUDA-enabled builds SGLang could significantly improve the throughput and latency. For now I build...

[Feature Request]: Ship CUDA-enabled builds (-DUSE_CUDA=ON) for correct GPU-NIC topology detection

@xiaguan Thank you for the PR! We would give it a try. Another question, the wheel release is DMA-BUF based GDR or nvidia-peermem based? I'm asking this because we can...

Fix: Upgrade from deprecated macos runners

Seems like setup-docker only support amd64, is there a alternative way or upgraded version?

Feat: allow specify input/output in override policy

We can solve the "Pass value in multicluster" situation described in the [KEP](https://github.com/kubevela/kubevela/blob/master/design/vela-core/cloud-resource-data-passing.md). However. the cost is we have to allow `ref-objects` to load object from cluster instead of ApplicationRevision....