-
Hi,
We are creating the ARGO module (Raspberry Pico footprint) based on nRF9151 SOC
https://wizcube.eu/argo.html
We also planning a new wizcube module code name M10LR01-01 PCB
On board a mini-P…
-
Checklist:
Argo roll out image version : v1.7.0
Kong Version: 3.5
Argo roll out app version: 2.37.2
**Describe the bug**
**To Reproduce**
1. Install argo roll out
2. Install ko…
-
# Summary
The API's gRPC support is not often used and not worth the maintenance according to various maintainers. Some currently used gRPC libraries are also deprecated need upgrading, like `grpc-…
-
The alert rules in CKF charms are using multiple values for severity label, e.g. `Warning`, `warning`, `high`, etc. Some even do not have severity label.
These should be aligned for all CKF charms…
-
### Is there an existing issue for this?
- [X] I have searched the existing issues
### What happened?
I recently migrated to Gateway API from Ingress and noticed this following behaviour: an additi…
-
It appears we're among the first to test out this plugin with linkerd and grpcroutes so I thought I'd share some knowledge which might help others.
We're running a custom build (just from trunk) ho…
-
# Summary
In our environment, the service mesh used is linkerd.
Linkerd is not officially supported by Argo Rollouts. However, Linkerd provided a way to use Argo Rollouts with it. I added a link b…
-
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`.
…
-
When I try to open the folder in devcontainer, feature "Node.js (via nvm), yarn and pnpm" (ghcr.io/devcontainers/features/node) failed to install!
logs follows:
```
[+] Building 442.3s (17/18) …
-
Currently kubectl get rollout only display exposed rollout status as columns, however it is vital to display the status of all involved objects as well, e.g. pods, traffic routings objects. So kruise-…