-
## Bug Report
**What did you do?**
When a new version of CR is introduced, the new version is marked as `served: true` while old version will be marked `served: false` in the CRD. When a version i…
-
invalidation issues for the GVKs we watch, or there's something non-deterministic
happening under-the-hood when lifecycling through helm's implementation. To reproduce,
run this check against an exi…
-
Hi,
I am facing an issue with the OLM packaging and ArgoCD. I am applying the cert-manager Subscription with ArgoCd in a dedicated Application and deployment completes fine. The issue is that the App…
-
In order to reduce the scope of what we are forced to support until a v2 release of OLM, should we proactively reject helm charts that ultimately include chart hooks in their manifests?
Supporting …
-
### Steps to reproduce
Sometimes, we'll see calls get stuck in the 'connecting' state and take 30 seconds or sometimes several minutes to connect. We observe the following:
* Client A sends and i…
-
Update all pods
Analyzing dependencies
Downloading dependencies
Installing AFNetworking (3.2.1)
Installing DGCollectionViewLeftAlignFlowLayout (1.0.4)
Installing DTCoreText (1.6.23)
Installing D…
-
## Configuration
## How to scope MutatingWebhookConfiguration to another namespace?
**What did you do?**
I have created a MutatingWebhook with the operator-sdk CLI, deployed it manually whi…
-
OLM requires the ClusterServiceVersion's `spec.version` field to be valid semver (parsable with `blang/semver.Parse()`). For example,
In opm:
- to generate a [semver-based package manifest in repl…
-
## Bug Report
**What did you do?**
I installed the olm in a k8s cluster. Then I created an OperatorGroup specifying only the kfox namespace in the kfox namespace. I then subscribed to the elasti…
-
We currently use `operator-registry` tools to build an operator registry (catalog) containing the Kabanero operator, and some other operators that we copy from community-operators. To build the regis…