Local PV (device) provisioner leaves a stale BDC in the following case:

• On PVC request, creates a BDC
• If the system doesn't have a matching BD, then PVC request keeps retrying, and so does the NDM operator that keeps retrying
• Now if the user deletes the PVC, then Local PV (device) provisioner doesn't get the trigger to process delete, as there was no PVC.

This causes the stale BDC

Is your feature request related to a problem?
"DevSpace should use the current docker behavior for dockerignore:
Dockerfile + .dockerignore
Dockerfile + Dockerfile.dockerignore
Dockerfile.frontend + Dockerfile.frontend.dockerignore
"

Which solution do you suggest?
Delegating the dockerignore file search to Docker if possible, otherwise copying the behavior as best as possible

From my YouTube comment: https://www.youtube.com/watch?v=UoOcLXfa8EU&lc=UgwZL42zHoDLwqG-XOd4AaABAg

Can't bootstrap due to different token

Check the release notes: https://github.com/k3s-io/k3s/releases/tag/v1.21.3%2Bk3s1

⚠️ Important Upgrade Note ⚠️
If you are using K3s in a HA configuration with an external SQL datastore, and your server (control-plane) nodes were not started with t

This is the component that should be fixed.

It should be fixed as below

You can find the right styles implemented in https://dashboard.jina.ai/

💻 How t

Currently, it seems that the way you could programmatically execute Runes natively is with Rust, C or something with WASM.

As @Michael-F-Bryan mentioned before, support for other languages could be obtained through the implementation of bindings through C++.

However, it also worthy to note that there may be a decent amount of maintainance associated with each language binding because of docu