operator
operator copied to clipboard
knative
Combined operator for Knative.
**Describe the bug** Having a generic shortname for [Subscription CRD](https://github.com/knative/eventing/blob/main/config/core/resources/subscription.yaml#L247) like `sub` is prone to ambiguity which isn't handled very well by kubectl or other clients. We came across a...
## In what area(s)? > /area autoscale ## What version of Knative? > 0.11.x ``` kn version Version: v1.11.0 Build Date: 2023-07-27 07:42:56 Git Revision: b7508e67 Supported APIs: * Serving...
**Problem** I use node taints to define which nodes my pods reside on. The Helm chart does not allow me to set Tolerations for the Operator deployment, so therefore, the...
https://knative.dev/docs/install/operator/knative-with-operators/#install-the-knative-operator is a bit outdated. Findings: - Table at the top references operator version 1.13, current version is 1.14.x - Chapter: Verify your Knative Operator installation: `kubectl apply -f https://github.com/knative/operator/releases/download/knative-v1.14.1/operator.yaml`...
fix wrong version on main (https://cloud-native.slack.com/archives/C04LY4Y3EHF/p1729776009449449?thread_ts=1729763678.995479&cid=C04LY4Y3EHF) -ReToCode /cc knative/operations-wg-leads /assign knative/operations-wg-leads Produced by: knative-extensions/knobots/actions/update-deps
**Problem** It would be nice if the knative feature flags could be configurable through the `KnativeServing` CRD. https://knative.dev/docs/serving/configuration/feature-flags/ **[Persona:](https://github.com/knative/eventing/blob/main/docs/personas.md)** System Operator **Exit Criteria** Feature flags can be configured by the...
**Describe the bug** I am trying to find a version of the Knative Operator that can upgrade to the latest versions of KnativeServing. We want to move from 1.11.0 ->...
This is a continuation of my comments under https://github.com/knative/operator/issues/1525. **Problem** The `knative-operator` is not released to any Helm Chart Repository. The Helm Charts exist in the artifacts but there is...
Since the operator already packages a helm chart and includes it in the releases, why not also publish it to a helm repo? it could even be a github page....
