-
Hi team,
I can't get gpu operator working on my environment. I'm getting following error
`microk8s kubectl logs nvidia-container-toolkit-daemonset-55p2p -n gpu-operator-resources driver-validation`
…
-
I've set this module up and it seems to work as far as allowing all Puppet agents to use the same policy by setting it at the `auth/cert/certs/puppetserver` as documented.
Is it possible with this …
-
Kubedock Version
0.9.2
Host OS
MacOS
Host Arch
ARM
**Environment:**
**Local Cluster with k3d:**
Server Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.10+k3s1", GitCommit:…
-
### Bug report:
The restart-container-runtime init container is configured to restart the container runtime without any conditions. As a result, the pod remains in an unready state (NotReady) perpe…
-
#### Summary
Using stable channel 1.28/stable, multus daemonset cannot be started meanwhile it can be started using 1.24/stable
#### Reproduction Steps
sudo snap install microk8s --classic
micro…
-
It would be great if the tool could support creating the service bindings for kpack.
Would it also be a volume mount to the builder?
Sofar I don't know how one would add the bindings of this sort vi…
-
It would be nice to have direct support for native secrets in the Application definition.
In the following use case, when referencing a public chart, it would be very handy to have the possibility …
-
### Describe the question/issue
Experiencing seemingly a fluent-bit related bug (low frequency and sporadic) where in the FB pod is not correctly sending logs from the node. Additionally the nod…
-
I got the following error:
11 2.895 In Git.php line 453:
#11 2.895
#11 2.895 Failed to execute git cl…
-
**Description**
Secrets that I need to provide are present as exported environment variables on the build server.
Rather than having to create files on the build server (and thus risk the secrets …