-
Hello, I'm trying to understand why the NodeFeature resource is owned by DaemonSet Pods.
We've been using 0.4.0 and noticed that 0.16.x brings a ton of architectural changes. These changes seem to …
-
_The template below is mostly useful for bug reports and support questions. Feel free to remove anything which doesn't apply to you and add more information where it makes sense._
_**Important Note…
-
**Describe the bug**
`omsagent-win` always claims half a core.
When the `omsagent` addon profile is enabled the daemonset that's installed for Linux nodes uses a reasonable resource profile.
**…
-
Checklist:
* [x] I've searched in the docs and FAQ for my answer: https://bit.ly/argocd-faq.
* [x] I've included steps to reproduce the bug.
* [x] I've pasted the output of `argocd version`.
…
-
## In what area(s)?
> /area runtime
/area operator
> /area placement
> /area docs
> /area test-and-release
## Describe the feature
For every dapr sidecar that gets created…
-
**Describe the bug**
No limits or requests are set for any Trident pods except the operator pod. This is bad practice, as an issue in Trident could take down the cluster.
**Environment**
Prov…
-
The `instance-manager` NetworkPolicy tries to select pods with `longhorn.io/component: instance-manager`:
https://github.com/longhorn/longhorn/blob/091256437632f5a0532eafef6462d26381cd2807/chart/te…
-
Not necessarily in this PR, but I think some customers will need to set an `imagePullSecrets` here from an optional `{{ .imagePullSecret }}` in the config
_Originally posted by @dbkegley in https:…
-
Pod running as a Daemon Set is usually responsible for some operations on the node. With new releases of node components the environment for those operations can happen. Since usually DS is updated to…
piosz updated
6 years ago
-
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the…