-
## Objective
Integrate new version of Pocket Network's validator - `poktrolld` with the Cosmos-SDK Kubernetes Operator.
## Origin Document
This integration will ensure seamless deployment and…
-
Meta Issue for k8s 1.31 bump
In order to bump Operator SDK to support Kubernetes 1.31 there are a few dependencies we rely on making the bump first.
This issue is meant to help track all dependenc…
-
### What happened?
I created a pytorch job which to use three pod.
when I delete a pod(worker), It will rec…
-
Meta Issue for k8s 1.30 bump
In order to bump Operator SDK to support Kubernetes 1.30 there are a few dependencies we rely on making the bump first.
This issue is meant to help track all dependenc…
-
## Bug Report
#### What did you do?
I have an Ansible Operator that needs to query resources with set-based label selector but seems the proxy/caching is not supporting this.
```
# cat p…
-
the K8s convention is to use `camalCase` and some of the fields in this API do that, right along others that use `snake_case`. This is a terrible user experience.
-
## Bug Report
#### What did you do?
Called `context.getSecondaryResources(resource)` inside `ResourceDiscriminator`.
#### What did you expect to see?
Secondary resources.
#### W…
-
- **Contributor**: @sandipanpanda - [LinkedIn](https://linkedin.com/in/sandipanpanda)
- **Mentors**: @tenzen-y, @andreyvelich, @terrytangyuan, @shravan-achar
- **Organization**: [Kubeflow](https://w…
-
Since upgrading to 5.0.0 we're noticing different behavior when it comes to starting up our operator. Sometimes we see the following health check status in our logs indicating that `Quarkus Operator …
-
Hi!
I've generated a new project using Quarkus starter, with Kotlin and Operator SDK selected, and Quarkus version `3.13.0` (the newest one). However, when building the project, I see such warning:…