-
Is there any reason to run the components as statefulsets? `taiga-front`, `taiga-gateway` and `taiga-protected` can be deployed as regular `Deployment`s I assume that the lifecycle guarantees of a s…
-
### Component(s)
extension/encoding/jsonlogencoding
### Is your feature request related to a problem? Please describe.
My use-case is to get data from the Kubernetes API, the data I am receiv…
-
Currently, the default overview section set is effectively hard-coded and therefore entirely unconfigurable. It consists of StatefulSets and Deployments, which is encapsulated in the `overview` "secti…
-
Instead of just containers, pods and nodes, it would be nice to also have views for deployments, daemonsets, statefulsets, etc...
-
**Is your feature request related to a problem? Please describe**.
As we are moving towards containers and wanted to deploy databases/monitoring/observability tools in Azure Container Apps.
As…
-
StatefulSets don't support volume expansion, but a manual procedure (which could be automated though) allows to do it nonetheless. We should add that procedure on the documentation website so that K8s…
-
I am trying to contain the statefulsets to exactly three (and no more) each running on their own node using:
```yaml
spec:
replicas: 3
# use latest-tag to force imagePullPolicy: always
im…
-
Recently we encountered the problem that Operator is not recreating the `StatefulSets` when performing a rolling update for the Druid version.
We receive:
> Failed to update [druid-routers:Statefu…
-
Issue description:
Installed "rancher-logging 100.0.1+up3.15.0" chart on a K3s v1.21.4 cluster imported in Rancher 2.6.0 Management server and getting errors the Deployments, DaemonSets and StatefulS…
-
### Helm Chart Version
all
### What step the error happened?
On deploy
### Revelant information
Helm Hooks are an antipattern:
* declarative configuration becomes imperative
* I'm trying to…