Max
Max
**Describe the bug** The `headComment` operator does not work correctly if I run it for multiple documents in a file. The same goes for `footComment`. Version of yq: 4.14.2 Operating...
### Description of your changes This design proposal aims to provide a solution for adding a third data source for composition patches next to claim/composite and composed resource by introducing...
### Description of your changes This modifies the implementation for map transforms to allow mapping to any kind of JSON value (string, number, bool, slice, object). The API changes are...
### What problem are you facing? Currently, if you create a claim in Crossplane, a composition is selected and all defined resources are rendered using parameters from the claim. In...
### What problem are you facing? Crossplane composite resource names are generated by the kube API server through setting `generatedName` to `-`. The server will append a random string as...
### Description of your changes Design: https://github.com/crossplane/crossplane/pull/3008 Fixes: #2099 This adds a new cluster scope CRD `EnvironmentConfig` that is similar to a standard `ConfigMap` but allows storing arbitrary values instead...
### Description of your changes Fixes #2850 * Add `Synced` condition that can be used to track reconcile errors (similar to managed resources in providers) * Add an additional printer...
### Description of your changes This adds the ability to generate custom composite names by passing a mini helm template via the new XRD field `spec.composite.name.template`. Fixes #3120 To ensure...
### What problem are you facing? Similar to #2887, #2698 and #2588. Currently, Crossplane's map transform does only allow mapping to string values. It should support any kind of valid...
### What problem are you facing? We use a custom Docker registry to deploy Crossplane and its providers. Currently, `meta.pkg.crossplane.io/Configuration` provides no way to overwrite provider package configurations, such as...