Manage any infrastructure your applications need directly from Kubernetes

Crossplane is an open source Kubernetes add-on that enables platform teams to assemble infrastructure from multiple vendors, and expose higher level self-service APIs for application teams to consume

Information

Category: Golang / Utilities
Watchers: 141
Star: 6.8k
Fork: 703
Last update: Mar 29, 2023

Resource links

https://github.com/crossplane/crossplane

Crossplane is an open source Kubernetes add-on that enables platform teams to assemble infrastructure from multiple vendors, and expose higher level self-service APIs for application teams to consume. Crossplane effectively enables platform teams to quickly put together their own opinionated platform declaratively without having to write any code, and offer it to their application teams as a self-service Kubernetes-style declarative API.

Both the higher level abstractions as well as the granular resources they are composed of are represented simply as objects in the Kubernetes API, meaning they can all be provisioned and managed by kubectl, GitOps, or any tools that can talk with the Kubernetes API. To facilitate reuse and sharing of these APIs, Crossplane supports packaging them in a standard OCI image and distributing via any compliant registry.

Platform engineers are able to define organizational policies and guardrails behind these self-service API abstractions. The developer is presented with the limited set of configuration that they need to tune for their use-case and is not exposed to any of the complexities of the low-level infrastructure below the API. Access to these APIs is managed with Kubernetes-native RBAC, thus enabling the level of permissioning to be at the level of abstraction.

While extending the Kubernetes control plane with a diverse set of vendors, resources, and abstractions, Crossplane recognized the need for a single consistent API across all of them. To this end, we have created the Crossplane Resource Model (XRM). XRM extends the Kubernetes Resource Model (KRM) in an opinionated way, resulting in a universal experience for managing resources, regardless of where they reside. When interacting with the XRM, things like credentials, workload identity, connection secrets, status conditions, deletion policies, and references to other resources work the same no matter what provider or level of abstraction they are a part of.

The functionality and value of the Crossplane project can be summarized at a very high level by these two main areas:

Enabling infrastructure owners to build custom platform abstractions (APIs) composed of granular resources that allow developer self-service and service catalog use cases
Providing a universal experience for managing infrastructure, resources, and abstractions consistently across all vendors and environments in a uniform way, called the Crossplane Resource Model (XRM)

Releases

Currently maintained releases, as well as the next upcoming release are listed below. For more information take a look at the Crossplane release cycle documentation.

Release	Current Patch	Release Date	EOL
v1.2	v1.2.4	Apr 27, 2021	October 2021
v1.3	v1.3.1	Jun 29, 2021	December 2021
v1.4	v1.4.1	Aug 31, 2021	February 2022
v1.5	Upcoming	Oct 26, 2021	April 2022

Getting Started

Take a look at the documentation to get started.

Get Involved

Discuss Crossplane on Slack or our developer mailing list.
Follow us on Twitter, or contact us via Email.
Join our regular community meetings.
Provide feedback on our roadmap.

The Crossplane community meeting takes place every other Thursday at 10:00am Pacific Time. Anyone who wants to discuss the direction of the project, design and implementation reviews, or raise general questions with the broader community is encouraged to join.

Crossplane is a community driven project; we welcome your contribution. To file a bug, suggest an improvement, or request a new feature please open an issue against Crossplane or the relevant provider. Refer to our contributing guide for more information on how you can help.

License

Crossplane is under the Apache 2.0 license.

134 Open More issues

Closed

API Server (and clients) becomes unresponsive with too many CRDs

What problem are you facing?

As part of the ongoing Terrajet-based providers effort, we have observed that registering 100s of CRDs has some performance impacts on the cluster. Observations from two sets of experiments are described here and here. As discussed in the results of the first experiment, Kubernetes scalability thresholds document currently does not consider #-of-CRDs (per cluster) as a dimension. However, sig-api-machinery folks suggest a maximum limit of 500 CRDs. And the reason for this suggested limit is not API call latency SLOs but rather, as we also identified in our experiments, due to the latency in the OpenAPI spec publishing. As the results of the second experiment demonstrate, the marginal cost of adding a new CRD increases as more and more CRDs exist in the cluster.

Although not considered as a scalability dimension officially yet, it looks like we need to be careful for the #-of-CRDs we install in a cluster. And with Terrajet-based providers we would like to be able to ship 100s of CRDs per provider package. Currently, for the initial releases of these providers, we are including a small subset (less than 10% of the total count) of all the managed resources we can generate. We would like to be able to ship all supported resources in a provider package.

How could Crossplane help solve your problem?

As part of the v1.Provider, v1.ProviderRevision, v1.Configuration and v1.ConfigurationRevision specs, we could have a new configuration field that tells the GVKs of package objects to be installed onto the cluster. To behave backwards-compatible, if this new API is not used, all objects defined in the package manifest get installed. If the new field has a non-zero value, then it's enabled and only selected objects get installed. In order to make the UX around installing packages using the new configuration field easier, we can also add new options for the install provider and install configuration commands of the Crossplane kubectl plugin.

As described in the experiment results, when a large #-of-CRDs are registered in a relatively short period of time, the background task that prepares the OpenAPI spec to be published from the /openapi/v2 endpoint may cause a spike in the API server's CPU utilization, and this may saturate the CPU resources allocated to the API server. Similar to what controller-runtime client does, we may also consider implementing a throttling mechanism in the package revision controller to prevent this. However, because of the reasons discussed above and in the experiment results (especially the latency introduced in OpenAPI spec publishing), it looks like we will need a complementary mechanism like the one suggested above in addition to a throttling implementation in the package revision reconciler.

enhancement performance package

opened Oct 21, 2021 by ulucinar 53

Closed

Stack ClusterRoles and Parent + RBAC Labelling

Description of your changes

This PR implements many, not all, of the changes recommended in @lukeweber's cluster roles to support self-service updates, PR #1008, which extends the Stack Security & Isolation design.

The majority of this work can be viewed as managing Stack, Environment (Cluster-wide), and Namespace specific ClusterRoles along with labels to take advantage of AggregationRules.

During the implementation of this PR, we became aware of problems settings ownership across permission scopes on Kubernetes resources.

The design for Parent/Child resource labelling, having recently been merged, became the underpinning for our approach to remedy the cross-scope ownership problem on CRD resources.

As this PR introduces several more child resources to Stacks, it became necessary to follow the same labelling practice and fix additional owner references to clusterroles and clusterrolebindings which this PR was touching. Stacks now delete their ClusterRoles and ClusterRoleBindings, detected using parent labels, through a finalizer, since ownerReferences (and garbage collection) can not cross permission scopes.

Similarly, StacksInstalls are now made to delete their Stack resources (through parent label matching) before removing the CustomResourceDefinitions. This is to avoid the condition where the Stack controller loses the ability to watch its owned resources, which results in the Stack being unable to clear its finalizer.

This PR closes the following issues:

#1049 clusterrole for namespaced stack deployments
#1054 ClusterStackInstalls should create stack+version specific clusterroles for personas
#1099 create stack version specific clusterroles for aggregation
#1015 CRDs should be labeled with the namespaces of their stacks for namespaced stacks
#1048 CRDs should be labeled with stack scope and stack names
#1053 install base ClusterRoles for cluster and namespace admin, edit, and view personas
#1050 create default clusterroles for environment, ns, and admin
#1113 create admin/edit/view clusterroles for stack namespaces
#1111 create a crossplane:master group on install
#752 - closed by assigning parent labels on remaining stack created resources
#1121 - closed by not setting ownerref on cluster resources from namespaced resources

Additional details are provided in most commit messages and the issues linked above.

Testing

The following commands are useful for seeing this PR in action

examining the effect of environment persona clusterroles

$ kubectl create clusterrolebinding marques-has-crossplane-env-view --clusterrole crossplane-env-view --user [email protected]
clusterrolebinding.rbac.authorization.k8s.io/marques-has-crossplane-env-view created
$ kubectl auth can-i --list [email protected]

examining the effect of environment persona clusterroles after installing a cluster scoped stack

$ kubectl crossplane stack generate-install --cluster crossplane/stack-gcp:v0.3.1 stack-gcp | kubectl -n crossplane-system apply -f - 
$ kubectl auth can-i --list [email protected]

$ kubectl delete clusterrole marques-has-crossplane-env-view

examining the effect of environment persona clusterroles after installing a namespaced scoped stack

$ kubectl create namespace precipice
$ kubectl crossplane stack generate-install crossplane/stack-wordpress:master stack-wordpress | kubectl -n precipice apply -f - 
$ kubectl auth can-i --list [email protected]

$ kubectl create rolebinding marques-has-crossplane-ns-precipice-view --clusterrole crossplane:ns:precipice:view --user [email protected] --namespace precipice
$ kubectl auth can-i --list [email protected] --namespace default
$ kubectl auth can-i --list [email protected] --namespace precipice

$ kubectl delete rolebinding marques-has-crossplane-ns-precipice-view

examining the effect of binding the crossplane-admin role

$ kubectl create clusterrolebinding marques-has-crossplane-admin --clusterrole crossplane-admin  --user [email protected]
clusterrolebinding.rbac.authorization.k8s.io/marques-has-crossplane-admin created
$ kubectl auth can-i --list [email protected] 
# notice Crossplane core, Wordpress, GCP, StackInstall, ClusterStackInstall, Stacks, Secrets, and ConfigMaps types
$ kubectl auth can-i [email protected] create secret
$ kubectl auth can-i [email protected] delete wordpressinstance --namespace precipice

$ kubectl delete clusterrole marques-has-crossplane-admin

examining the capabilities of the preinstalled group binding crossplane:masters

$ kubectl auth can-i --list --as-group=crossplane:masters --as-group=system:authenticated --as=nobodyspecial

examining the labels applied for RBAC roles and resource relationship mapping

$ kubectl get -A  -lcore.crossplane.io/parent-name=stack-gcp  clusterrole,stack,stackinstall,clusterstackinstall,deployment,clusterrolebinding,rolebinding,role,job,pod

examining the labels available for assigning personas

$ kubectl get clusterrole -l core.crossplane.io/scope=environment
$ kubectl get clusterrole -l core.crossplane.io/scope=namespace

demonstrating admins granting roles to other admins

$ kubectl create rolebinding demo-crossplane-onboarded-ns-admin --clusterrole crossplane:ns:precipice:admin --user [email protected] --namespace precipice [email protected]
rolebinding.rbac.authorization.k8s.io/demo-crossplane-onboarded-ns-admin created

$ kubectl create clusterrolebinding demo-crossplane-onboarded-admin --clusterrole crossplane-env-admin --user [email protected] [email protected]
clusterrolebinding.rbac.authorization.k8s.io/demo-crossplane-onboarded-admin created

Checklist

I have:

[ ] Run make reviewable to ensure this PR is ready for review.
[ ] Ensured this PR contains a neat, self documenting set of commits.
[ ] Updated any relevant documentation, examples, or release notes.
[ ] Updated the RBAC permissions in clusterrole.yaml to include any new types.

opened Nov 13, 2019 by displague 34

Closed

Host aware stack manager

Description of your changes

This PR resolves the issue https://github.com/crossplaneio/crossplane/issues/1038 by implementing the design proposed with one-pager in https://github.com/crossplaneio/crossplane/pull/1138.

How has this code been tested?

By deploying host cluster - tenant kubernetes setup presented in one-pager.

Checklist

[x] Update Makefile for preparing helm charts (using existing yamls)
[x] Unit Tests
- [x] Adapt existing unit tests
- [x] Add new unit tests
[x] Add comments to code
[x] Test and make sure regular installation works as before
[x] Run make reviewable to ensure this PR is ready for review.
[x] Ensured this PR contains a neat, self documenting set of commits.
[x] Updated any relevant documentation and examples.
[ ] Reported all new error conditions into the log or as an event, as appropriate.

For more about what we believe makes a pull request complete, see our definition of done.

opened Dec 27, 2019 by turkenh 33

Closed

Consolidation of CRD Scaling Issues

What problem are you facing?

Previously in https://github.com/crossplane/terrajet/issues/47, #2649 and https://github.com/kubernetes/kubernetes/issues/105932, we have observed high resource consumption in the Kubernetes API Server when over 500 CRDs are installed. Especially with local kind clusters, installing provider-jet-aws with over 700 CRDs could render the cluster unresponsive on machines with relatively low CPU resources, due to the high CPU consumption. And with the managed Kubernetes offerings such as GKE, EKS and AKS, with varying levels dependent on the cluster configurations, we had observed API service disruptions as we installed 100s or 1000s of CRDs. While discussing those issues as the Crosplane community, we had tried a couple of different workarounds detailed in #2649, such as installing CRDs in smaller batches and giving the API Server some time to finish aggregating their OpenAPI specs.

Meanwhile after getting in touch with the upstream Kubernetes maintainers, we learned that they already were working on https://github.com/kubernetes/kube-openapi/pull/251, which would introduce lazy marshalling for the aggregated OpenAPI specs of the installed CRDs served from the /openapi/v2 endpoint. Collecting profiling data and builing kind images with that PR and testing them in local kind clusters, we observed substantial improvements in peak resource consumption. However, as discussed in #2649 there were still some open points left:

Discovery client throttles itself (client-side throttling) while discovering the exposed API, if its cache is unestablished (first time discovery) or is invalidated (subsequent discoveries)
Metrics collected from the API server reveal a continued memory consumption of ~ 2.75 GiB for ~600 CRDs and memory consumption increases with the number of CRDs

Although we could not actually observe the effects of the aggregated OpenAPI spec lazy-marshalling optimization in a managed Kubernetes offering [1], we expected it to alleviate control plane service disruptions. Starting with Kubernetes versions v1.20.13, v1.21.7, v1.22.4, v1.23.0 this fix is available and as of this writing:

v1.23.1 and v1.22.4 are available for most GKE regions via the rapid GKE release channel, and
v1.22.4 and v1.21.7 are available for most AKS regions.

This allowed us to test the hypothesis with the lazy-marshalling optimization and we have recently made a number of tests with the managed Kubernetes offerings. Please note that the following are reports from single experiments, and only server-side issues are reported. For all clusters even if there is no API service disruption, we always experience client-side throttling.

Related issues

[ ] #2869

GKE Zonal

On a GKE v1.23.1 zonal cluster with three worker nodes of type e2-medium, it took 56 min for the ProviderRevision to acquire the Healthy condition for a provider-jet-aws installation with 763 CRDs. During this period, the cluster needed at least one repair, and there was over 50 min of service disruption. After a slight confusion regarding worker-node HA and control-plane HA, this thread suggests using regional clusters for control-plane high availability, and states that control-plane service disruptions are expected for zonal GKE clusters as GKE is scaling the managed control-plane under load. However, as discussed next, the situation with a regional cluster was not good either.

GKE Regional

A v1.23.1 cluster was provisioned in the us-east1 region with one e2-medium node in each availability zone, with a total of 3 worker nodes in 3 zones. Although it took only ~ 150 s for the ProviderRevision to acquire the Healthy condition for the [email protected] installation, the regional GKE cluster went through the repairing mode at least three times afterwards. In between these "RUNNING" and "RECONCILING" states of the regional cluster, we have observed different kinds of errors in response to the kubectl commands run, notably connection errors and I/O timeouts while reaching the API server. It took over an hour for the cluster to stabilize. However, the control-plane was intermittently available for short periods during this period.

EKS

When we performed these tests, none of the Kubernetes versions consuming the lazy-marshalling optimization were available for EKS clusters. However, we used a v1.21.5-eks-bc4871b 3-worker node cluster to test a [email protected] installation. Grafana dashboards indicate a control-plane with two members from the very beginning before provider-jet-aws package is installed into the system. It took the ProviderRevision about 2 min to acquire the Healthy condition. The cluster stayed stable after the provider installation. A reexamination of the Grafana dashboards after 3 hours reveals that the two-member control-plane was scaled up and down during this period. Apart from the client-side throttling issues, control-plane is stable with a provider-jet-aws installation.

AKS

A v1.22.4 cluster was provisioned with two worker nodes. It took ~112 s for the ProviderRevision to acquire the Healthy condition for a [email protected] installation. The cluster stayed stable after the provider installation. Also installed [email protected] on this cluster making the total CRD count 1430. It took 91 s for provider-jet-azure's ProviderRevision to acquire the Healthy condition. It takes ~ 40 s for the discovery client to refresh its cache. And we observe some pod restarts due to timeouts. But the cluster stays stable. However, adding [email protected] as a third provider has finally "breaks" the cluster. Crossplane is having a hard time installing the package.

We also repeated these experiments with a two worker node AKS v1.20.13 with similar results: It took 107 s for the ProviderRevision to acquire the Healthy condition. The cluster stayed stable after the provider installation. Reaching a total of 780 CRDs, the cluster has no severe issues. Client-side throttling kicks in as expected.

We also need a deeper understanding on which metrics are being employed by the Cloud providers when deciding to scale up their control planes. Usual metrics are CPU/memory consumption and/or utilization of the control-plane components but they could as well be depending on metrics such as the number of installed CRDs and/or API Server response time SLIs, etc.

Another dimension where we need clarification is why we observe control plane service disruptions when the managed control plane is scaling up. It's perfectly expected, at some point as we continue adding more CRDs to the cluster, the control plane will need to scale up but if it has high-availability features, then why are we not isolated from the effects?

We are now at a point where there are several upstream Kubernetes issues and PRs, Crossplane issues and discussions happening at different places, which makes it hard to figure out the exact problems and root causes. Also under #2649, there is still some discussion going on. This motivates us to open this issue so that we can decide how to move on.

[1]: Currently, we are not aware of a configuration option or another mechanism that would allow us to replace the kube-openapi with a custom build for an AKS/EKS/GKE cluster.

How could Crossplane help solve your problem?

We can have a one-pager that includes:

The set of problems we are still observing like the continuos memory consumption and client-side throttling issues with the discovery client. We also need a deeper understanding of these issues and their mechanics.
A deeper understanding of how Cloud providers are scaling their Kubernetes control planes and which metrics they are depending on. And also a deeper understanding on why we experience service disruptions even with HA control planes when installing 1000s of CRDs. We can achieve this understanding by opening issues to the Cloud providers for them to investigate and having discussions with them.
A definition for the ideal state like reasonable response times on certain kubectl requests (cached and uncached) when there are 100s of CRDs and memory usage per 100s CRDs.
It would be helpful to have scalability goal(s) for Crossplane in terms of the number of (active) managed resource types (CRDs) to support in a cluster with an appropriate size. This can be input for a Crossplane scalability guide and/or for advocating Crossplane use-cases when CRD scalability thresholds are being discussed upstream, etc.
The tooling to quickly reproduce the cases and test the progress against the ideal state. Go/Bash tools to run these tests for a given cluster and report the comparison. References to all known issues and PRs about the topic.

This would help all stakeholders to see all the data we have, reproduce the problems quickly and make more informed decisions about how to move forward. The tooling could be part of the Kubernetes Conformance tests at one point but it’s not in the scope of this issue.

Another goal we should work towards is to get CRDs as a scalability dimension in the Kubernetes thresholds document as discussed here.

enhancement

opened Feb 11, 2022 by ulucinar 29

Closed

Design: Add proposal to patch from a generic datasource

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 a new resource EnvironmentConfig.

It is not the goal of this design document to provide a way for patching from any Kubernetes object (aka generic referencers).

CC @negz

Related to https://github.com/crossplane/crossplane/issues/2099

Implementation: https://github.com/crossplane/crossplane/pull/3007

I have:

[x] Read and followed Crossplane's [contribution process].
[ ] Run make reviewable to ensure this PR is ready for review.
[ ] Added backport release-x.y labels to auto-backport this PR if necessary.

How has this code been tested

n.a.

design

opened Mar 24, 2022 by MisterMX 26

Closed

Stack managed ClusterRoles to support self-service

Stack manager and by extension Crossplane currently assumes that RBAC will be configured by an admin as an experience largely left to the reader, but each stack-install changes the available CRDs that a particular persona need to access, thus creating work and friction to our extension story for stacks. For a truly self-service model, a person who installs a stack, should then be able to consume the resources that were installed as part of the machinery of Crossplane.

Kubernetes provides the concept of built-in roles, like cluster-admin, admin, edit, view, that provides a clear role to bind to for expected behavior and I think Crossplane should provide the same to make secure integration with crossplane even easier.

Cluster / Namespace scoped stacks + stack-manager provides a very clean way to implement a concise consumption and permissioning model around all crossplane installed resources using automatic role aggregation provided by Kubernetes.

Additional updates were made to reflect that we no longer have multiple environments in different namespaces, as infrastructure scoped resources have moved to the Cluster scope. In the same respect, Cluster stacks and their installation should no longer be namespaced, instead living in the cluster scope as well as part of the infrastructure.

Description of your changes

Checklist

I have:

[ ] Run make reviewable to ensure this PR is ready for review.
[ ] Ensured this PR contains a neat, self documenting set of commits.
[ ] Updated any relevant documentation, examples, or release notes.
[ ] Updated the RBAC permissions in clusterrole.yaml to include any new types.

design

opened Oct 29, 2019 by lukeweber 25

Open

Consider authoring blog posts for each release

What problem are you facing?

We have not been posting blog posts about each release to https://blog.crossplane.io/ recently. This has hurt discoverability and socializing all the new work we've been doing in each great release.

How could Crossplane help solve your problem?

We should consider updating our release process to include a blog post that wraps up the key features, improvements, in each focus area for each release.

enhancement docs project management release

opened Mar 28, 2023 by jbw976 0

Open

feat: logical composition validation [1/3]

Description of your changes

Implements part 1 of 3 of what's described in https://github.com/crossplane/crossplane/pull/3756. This PR only adds a Validating Webhook for Compositions, only performing "Logical" checks. Following PRs will address Schema based validation as implemented in the design document. A few things are for future needs in the following PRs.

I have:

[x] Read and followed Crossplane's contribution process.
[x] Run make reviewable to ensure this PR is ready for review.
[x] Added backport release-x.y labels to auto-backport this PR if necessary.

How has this code been tested

Unit tests added and manually tested.

opened Mar 28, 2023 by phisco 0

Open

Crossplane connection secrets and DR scenario

What problem are you facing?

We would like to run DR scenario using velero on namespace with 2 claims deployed via fluxcd

Our current setup

we have defined Composition & CompositeResourceDefinition for provisioning RDSInstance (MySQLInstance /XMySQLInstance)
we have defined Composition & CompositeResourceDefinition for provisioning database, read-only user, read-and-write user, permissions/grants on RDSInstance by leveraging sql provider (Setup/ XSetup)
We try to always set crossplane.io/external-name patch with <namespace>-<claimName> naming convention - this allows us import back resource (with deletionPolicy set to Orphan)
in crossplane-poc ns we deploy MySQLInstance & Setup claims with fluxcd
velero will backup only crossplane connection secrets
- ManagedResources connection secrets from crossplane-system ns
- CompositeResources connection secrets from crossplane-system ns
- Claim's connection secrets from claim ns (crossplane-poc)

DR scenario

MySQLInstance & Setup claims get deployed to crossplane-poc ns anc crossplane creates connection secrets (passwords for RDSInstance & database users are auto-generated by providers)
we run velero backup create ...
we delete both claims from crossplane-poc namespace
fluxcd automatically deploys again both MySQLInstance & Setup claims (before running velero)
- this will create CompositeResource's and ManagedResource's will have different name than previously
- passwords will be missing in connection secrets
we run velero backup restore ...
- it will recover connection secrets for CompositeResource's and ManagedResource's but won't replace existing ones as they have now different name
- it will overwrite Claim connection secret which is desired state (one recreated by FLUX has missing passwords)

Challenges

after deleting claim's fluxcd will redeploy them automatically before we running velero backup restore
due to that we end-up with duplicated orphaned connection secrets

How could Crossplane help solve your problem?

Is there any recommendation from crossplane side to tackle DR scenario when crossplane claims are deployed via FLUX? Adding possibility to set a name for CompositeResource connection secret could help

enhancement

opened Mar 27, 2023 by mateusz-lubanski-sinch 0

Open

feat: In `match` transform, allow fallback to input

This would be useful to make conditional transformations to an input but, if nothing matches, keep the input unmodified As it is, anything that goes through this transform is squashed

Usecase:

One case this is useful is for the newer_noncurrent_versions attribute: https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_bucket_lifecycle_configuration#newer_noncurrent_versions. It actually takes in a string rather than a number. When the attribute should not be set, it has to be an empty string, not "0", which fails because the value has to be higher than 0

So with this new match feature, I can transform my composition parameter to be replaced by an empty string when it's zero, but keep all other values:

                   -  type: FromCompositeFieldPath
                      fromFieldPath: spec.parameters.keepNonCurrentVersions
                      toFieldPath: spec.forProvider.rule[0].noncurrentVersionExpiration[0].newerNoncurrentVersions
                      transforms:
                        - parameters:
                            toType: string
                          type: convert
                        - fallbackToInput: true
                          patterns:
                            - literal: "0"
                              result: ""
                              type: literal
                          type: match

I have:

[x] Read and followed Crossplane's [contribution process].
[x] Run make reviewable to ensure this PR is ready for review.
[ ] Added backport release-x.y labels to auto-backport this PR if necessary.

How has this code been tested

Unit tests + deployed in my cluster and tested with the case shown above ⏫

opened Mar 27, 2023 by julienduchesne 1

Open

Unexpected behavior with Composite Functions

Discussed in https://github.com/crossplane/crossplane/discussions/3905

^{Originally posted by jaylevin March 23, 2023} I have been experimenting with composite functions for the past week and have been experiencing some unexpected behavior that I would like to confirm with the community is actually unexpected.

I have a composition function very similar to the example in the documentation. It adds an annotation to a specific resource in the functionio["desired"]["resources"] object. I have a conditional case to check if the annotation already exists in the desired resource, and if it doesn't it adds it. If the annotation already exists, I also add a message to the results array to help with debugging.

The function looks something like this:


    # basic function to add an annotation if it does not exist
    try:
        for r in functionIO["desired"]["resources"]:
            result_normal(functionIO, f"resource: {r}")
            if r["name"] == "environment":
                if "resource" not in r:
                    continue
                if "metadata" not in r["resource"]:
                    r["resource"]["metadata"] = {}
                if "annotations" not in r["resource"]["metadata"]:
                    r["resource"]["metadata"]["annotations"] = {}

                ANNOTATION_NAME = "test-annotation"
                if ANNOTATION_NAME not in r["resource"]["metadata"]["annotations"]:
                    # should only run once per resource
                    result_normal(functionIO, "desired resource does not have annotation, one will be added!")
                    r["resource"]["metadata"]["annotations"][ANNOTATION_NAME] = "test"
                else:
                    result_normal(functionIO, "desired resource has annotation, skipping!")
                break
    except Exception as e:
        result_normal(functionIO, f"exception: {str(e)}")

The problem I am running into is the desired object does not seem to be saved between function executions.

For example:

The function runs the first time and adds the annotation to the desired object and returns.
Reconcile happens and the annotation is added to the composed resource.
The function runs a second time, and once again, the desired resource in the FunctionIO object does not have the annotation. I would expect that the desired object being passed to the function would contain the changes that were made in the previous function execution. Is this not the intended behavior, or is this a bug? Should I be checking the observed resource instead of the desired resource?

I have tried using Crossplane v1.11.1, v1.11.2, and the latest build on the master branch (crossplane-1.12.0-rc.0.213.g2a65adbb.tgz)

opened Mar 27, 2023 by jaylevin 0

Open

feat: ClampMin and ClampMax math transforms

Usecase:

For building cloud-agnostic bucket lifecycle policies, I have a parameter called expireObjectsDays. I use the value 0 of that parameter to disable object expiry. In AWS, I use a match transform to set the status of the lifecycle policy to Disabled when the days parameter is zero: https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_bucket_lifecycle_configuration#status

However, I also have a patch on the actual days attribute. Right now, I haven't found an easy way of setting a minimum of 1 while also keeping the original value if it was already higher. It would be easily done with a clamp:

                    - type: FromCompositeFieldPath
                      fromFieldPath: spec.parameters.expireObjectsDays
                      toFieldPath: spec.forProvider.rule[0].expiration[0].days
                      transforms:
                        - type: math
                          math:
                            type: ClampMin
                            clampMin: 1

I called the transforms clampMin and clampMax because it's clearer what it does rather than min and max (does it clamp to that value OR find the max between the input and given param?)

I have:

[x] Read and followed Crossplane's [contribution process].
[x] Run make reviewable to ensure this PR is ready for review.
[ ] Added backport release-x.y labels to auto-backport this PR if necessary.

How has this code been tested

Unit tests + deployed in my cluster and tested with the case shown above ⏫

opened Mar 27, 2023 by julienduchesne 1

v1.10.3(Mar 10, 2023)

v1.10.3 bumps the crossplane-runtime version, in order to address a Crossplane vulnerability, caused by https://github.com/crossplane/crossplane-runtime/security/advisories/GHSA-vfvj-3m3g-m532. These vulnerabilities were discovered thanks to the fuzz tests added to the Crossplane project by Ada Logics as part of a security audit sponsored by the CNCF.

What's Changed

Update gcr.io/distroless/static Docker digest to 450981e (release-1.10) by @renovate in https://github.com/crossplane/crossplane/pull/3699
Update gcr.io/distroless/static Docker digest to d2e0993 (release-1.10) by @renovate in https://github.com/crossplane/crossplane/pull/3734
Update gcr.io/distroless/static Docker digest to d02be0e (release-1.10) by @renovate in https://github.com/crossplane/crossplane/pull/3767
Update gcr.io/distroless/static Docker digest to 3c57678 (release-1.10) by @renovate in https://github.com/crossplane/crossplane/pull/3810
[Release 1.10] Bump crossplane-runtime to v1.19.2 by @phisco in https://github.com/crossplane/crossplane/pull/3841

Full Changelog: https://github.com/crossplane/crossplane/compare/v1.10.2...v1.10.3

Source code(tar.gz)
Source code(zip)

v1.11.2(Mar 9, 2023)

v1.11.2 bumps the crossplane-runtime version, in order to address a Crossplane vulnerability, caused by https://github.com/crossplane/crossplane-runtime/security/advisories/GHSA-vfvj-3m3g-m532. These vulnerabilities were discovered thanks to the fuzz tests added to the Crossplane project by Ada Logics as part of a security audit sponsored by the CNCF.

What's Changed

Update gcr.io/distroless/static Docker digest to 3c57678 (release-1.11) by @renovate in https://github.com/crossplane/crossplane/pull/3811
[Backport release-1.11] chore: bump crossplane-runtime to v0.19.2 by @phisco in https://github.com/crossplane/crossplane/pull/3838

Full Changelog: https://github.com/crossplane/crossplane/compare/v1.11.1...v1.11.2

Source code(tar.gz)
Source code(zip)

v1.9.2(Mar 9, 2023)

v1.9.2 bumps the crossplane-runtime version, in order to address a Crossplane vulnerability, caused by https://github.com/crossplane/crossplane-runtime/security/advisories/GHSA-vfvj-3m3g-m532. These vulnerabilities were discovered thanks to the fuzz tests added to the Crossplane project by Ada Logics as part of a security audit sponsored by the CNCF.

What's Changed

[Backport release-1.9] docs: fix FromValue example of XR connection details by @github-actions in https://github.com/crossplane/crossplane/pull/3328
[Backport release-1.9] Add note recommending usage of SPDX License Identifiers by @github-actions in https://github.com/crossplane/crossplane/pull/3353
[Backport release-1.9] Docs: fix CombineFromComposite patch example by @github-actions in https://github.com/crossplane/crossplane/pull/3359
Backport Hugo docs to v1.9 by @plumbis in https://github.com/crossplane/crossplane/pull/3367
change version from float to string to fix site version menu by @plumbis in https://github.com/crossplane/crossplane/pull/3379
[release-1.9] Update documentation with new package repos and links to search by @hasheddan in https://github.com/crossplane/crossplane/pull/3388
[release-1.9] Fix missing getting started section in docs by @hasheddan in https://github.com/crossplane/crossplane/pull/3390
[Backport 3440 to release 1.9] CLI install script: prefix variables by @pbenas in https://github.com/crossplane/crossplane/pull/3447
Update v1.9 docs content to conform to new docs.crossplane.io by @plumbis in https://github.com/crossplane/crossplane/pull/3484
[Backport release-1.9] Add missing word by @github-actions in https://github.com/crossplane/crossplane/pull/3494
[release-1.9] Rename docs repo (#3502) by @hasheddan in https://github.com/crossplane/crossplane/pull/3504
[Backport release-1.9] Docs: Fiz docs about readinessChecks in the MatchInteger code snippet… by @github-actions in https://github.com/crossplane/crossplane/pull/3526
[Backport release-1.9] Restore packagePullPolicy Always polling behavior by @github-actions in https://github.com/crossplane/crossplane/pull/3585
[release-1.9] Do not publish docs to documentation repo by @hasheddan in https://github.com/crossplane/crossplane/pull/3579
[Backport release-1.9] Fix 404 on Helm chart icon by @github-actions in https://github.com/crossplane/crossplane/pull/3591
Pin dependencies (release-1.9) by @renovate in https://github.com/crossplane/crossplane/pull/3654
Update gcr.io/distroless/static Docker digest to 5bda5a4 (release-1.9) by @renovate in https://github.com/crossplane/crossplane/pull/3655
Update gcr.io/distroless/static Docker digest to 450981e (release-1.9) by @renovate in https://github.com/crossplane/crossplane/pull/3698
Update gcr.io/distroless/static Docker digest to d2e0993 (release-1.9) by @renovate in https://github.com/crossplane/crossplane/pull/3732
Update gcr.io/distroless/static Docker digest to d02be0e (release-1.9) by @renovate in https://github.com/crossplane/crossplane/pull/3766
Update gcr.io/distroless/static Docker digest to 3c57678 (release-1.9) by @renovate in https://github.com/crossplane/crossplane/pull/3809
[Release 1.9] bump crossplane-runtime to 0.16.1 by @lsviben in https://github.com/crossplane/crossplane/pull/3839

New Contributors

@lsviben made their first contribution in https://github.com/crossplane/crossplane/pull/3839

Full Changelog: https://github.com/crossplane/crossplane/compare/v1.9.1...v1.9.2

Source code(tar.gz)
Source code(zip)

v1.11.1(Feb 24, 2023)

v1.11.1 contains a fix for Composition Functions causing extra resources to be created (#3774), applies the --pollInterval CLI argument to the Claim and Composite reconcilers (#3773), and adds the Composite Kind and APIVersion information to the kubectl get output columns for Compositions and CompositionRevisions. Additional dependency and CI updates are also included.

What's Changed

Update gcr.io/distroless/static Docker digest to 450981e (release-1.11) by @renovate in https://github.com/crossplane/crossplane/pull/3700
Update debian:bookworm-slim Docker digest to ffd3e96 (release-1.11) by @renovate in https://github.com/crossplane/crossplane/pull/3727
Update gcr.io/distroless/static Docker digest to d2e0993 (release-1.11) by @renovate in https://github.com/crossplane/crossplane/pull/3738
Update debian:bookworm-slim Docker digest to 199482f (release-1.11) by @renovate in https://github.com/crossplane/crossplane/pull/3729
Update debian:bookworm-slim Docker digest to 72cc75f (release-1.11) by @renovate in https://github.com/crossplane/crossplane/pull/3768
Update gcr.io/distroless/static Docker digest to d02be0e (release-1.11) by @renovate in https://github.com/crossplane/crossplane/pull/3769
[Release 1.11] Bump runtime to v0.19.1 by @turkenh in https://github.com/crossplane/crossplane/pull/3787
[Backport release-1.11] Add compositeTypeRef kind and apiVersion to Composition output columns by @github-actions in https://github.com/crossplane/crossplane/pull/3780
[release-1.11] Bump Ubuntu version to 22.04 in CI by @turkenh in https://github.com/crossplane/crossplane/pull/3803
[Backport release-1.11] Apply pollInterval to Claim and Composite reconcilers by @github-actions in https://github.com/crossplane/crossplane/pull/3773
[Backport release-1.11] Use NewAPIPatchingApplicator in PTF composite by @github-actions in https://github.com/crossplane/crossplane/pull/3797

Full Changelog: https://github.com/crossplane/crossplane/compare/v1.11.0...v1.11.1

Source code(tar.gz)
Source code(zip)

v1.11.0(Jan 31, 2023)

Release v1.11.0 is a regularly scheduled quarterly release that includes many exciting features that have been highly requested by the Crossplane community, such as Composition Functions, EnvironmentConfig, and promoting CompositionRevisions to beta.

Additionally, this v1.11.0 release includes a major documentation rewrite based on direct feedback from Crossplane users, and also focuses on stability fixes and design investigations.

New Features

Composition Function support introduced in alpha by @negz in https://github.com/crossplane/crossplane/pull/2886. You are now able to write your own custom composition logic, in any programming language of your choice, to augment Crossplane’s built-in patching and transform capabilities.
EnvironmentConfig support introduced in alpha by @MisterMX in https://github.com/crossplane/crossplane/pull/3007. It’s now possible to patch resources within a Composition by using configuration data from the general runtime environment, as opposed to being constrained to information available within a single composite resource.
Promoted CompositionRevisions to v1beta1 and are now enabled by default by @ezgidemirel in https://github.com/crossplane/crossplane/pull/3453. CompositionRevisions have been improved with feedback from the community and are now stabilized and ready for general production usage.
The Crossplane documentation website has been redesigned to give users of Crossplane a better educational experience, whether they are new to the project or more advanced. Check out the new docs site at https://docs.crossplane.io/ and let us know your feedback in the docs repo!

Notable Updates

This will be the last release to be published to Docker Hub, future releases will use xpkg.upbound.io instead by @nullable-eth in https://github.com/crossplane/crossplane/pull/3568
ControllerConfing API has been deprecated by @hasheddan in https://github.com/crossplane/crossplane/pull/3678
Lock API v1alpha1 has been dropped by @negz in https://github.com/crossplane/crossplane/pull/3479
CompositionRevisions' names are built adding a partial hash suffix by @ezgidemirel in https://github.com/crossplane/crossplane/pull/3391

What's Changed

Empty commit for after v1.10 by @muvaf in https://github.com/crossplane/crossplane/pull/3368
Add new steps for docs by @plumbis in https://github.com/crossplane/crossplane/pull/3372
Add support for deleteCompositePolicy by @bobh66 in https://github.com/crossplane/crossplane/pull/3321
Validate docs content in CI and support one-command local dev by @hasheddan in https://github.com/crossplane/crossplane/pull/3375
Update documentation with new package repos and links to search by @hasheddan in https://github.com/crossplane/crossplane/pull/3373
Fix compositionRevision update conflict by @ezgidemirel in https://github.com/crossplane/crossplane/pull/3376
Consume latest crossplane-runtime's fake.Composite to prevent panics caught by CNCF fuzzing tests by @ulucinar in https://github.com/crossplane/crossplane/pull/3394
Update crossplane chart README.md with correct pull secret value by @hasheddan in https://github.com/crossplane/crossplane/pull/3400
Only match steering committee files in root by @hasheddan in https://github.com/crossplane/crossplane/pull/3401
helm tolerations map > list by @apj0nes in https://github.com/crossplane/crossplane/pull/3412
More granular comparison of Roles annotations during reconciliation. by @jmprusi in https://github.com/crossplane/crossplane/pull/3409
Set crossplane user agent on package requests by @hasheddan in https://github.com/crossplane/crossplane/pull/3405
Change 'Compute' to 'Computing' in CNCF by @nickbeaugie in https://github.com/crossplane/crossplane/pull/3424
Ensure stable sorting of object references on package revisions by @hasheddan in https://github.com/crossplane/crossplane/pull/3426
Updated readme: Added v1.11 and removed v.1.7 from supported releases by @shazib-summar in https://github.com/crossplane/crossplane/pull/3411
[helm chart] Set GOMAXPROCS and GOMEMLIMIT based on resource limits by @epk in https://github.com/crossplane/crossplane/pull/3432
Change the composition name to production by @mplzik in https://github.com/crossplane/crossplane/pull/3434
Explicitly setting release namespace on resources by @AaronME in https://github.com/crossplane/crossplane/pull/3437
feat(chart): Allow prepopulating cache from ConfigMap by @MisterMX in https://github.com/crossplane/crossplane/pull/3438
Add reference policy concept to documentation by @sergenyalcin in https://github.com/crossplane/crossplane/pull/3439
CLI install script: prefix variables by @pbenas in https://github.com/crossplane/crossplane/pull/3440
Create composition revision names with partial hash by @ezgidemirel in https://github.com/crossplane/crossplane/pull/3391
Add a design document for 'Composition Functions' by @negz in https://github.com/crossplane/crossplane/pull/2886
Implement composition revision selector by @ezgidemirel in https://github.com/crossplane/crossplane/pull/3450
Docs: Terrajet => Upjet by @luebken in https://github.com/crossplane/crossplane/pull/3404
Enable mergeOptions for composition revisions by @eloo-abi in https://github.com/crossplane/crossplane/pull/3364
feat(transform): Add match transform by @MisterMX in https://github.com/crossplane/crossplane/pull/3314
Only update frontmatter on minor releases by @hasheddan in https://github.com/crossplane/crossplane/pull/3430
Update Doc Argo CD Configuration by @clementblaise in https://github.com/crossplane/crossplane/pull/3428
Enable the revive and nolintlint linters. by @negz in https://github.com/crossplane/crossplane/pull/3462
fix broken link to helm provider by @csantanapr in https://github.com/crossplane/crossplane/pull/3464
Promote CompositionRevision to v1beta1 by @ezgidemirel in https://github.com/crossplane/crossplane/pull/3453
Correct spelling in Composition Functions design doc by @tobru in https://github.com/crossplane/crossplane/pull/3473
fix all broken links in install-configure by @csantanapr in https://github.com/crossplane/crossplane/pull/3470
Update build submodule to remove Go check by @hasheddan in https://github.com/crossplane/crossplane/pull/3488
Update CompositionRevision guide and remove CURRENT marker by @ezgidemirel in https://github.com/crossplane/crossplane/pull/3481
Update master docs content to conform to new docs.crossplane.io by @plumbis in https://github.com/crossplane/crossplane/pull/3486
Add missing word by @plumbis in https://github.com/crossplane/crossplane/pull/3489
Switch Nathan for Ezgi in reviewers by @negz in https://github.com/crossplane/crossplane/pull/3496
Fix enabling external secret stores in guide by @hasheddan in https://github.com/crossplane/crossplane/pull/3499
Rename docs repo by @plumbis in https://github.com/crossplane/crossplane/pull/3502
Remove notices that Composition Revision related fields are alpha by @negz in https://github.com/crossplane/crossplane/pull/3471
Use goverter to automatically generate conversion code by @negz in https://github.com/crossplane/crossplane/pull/3479
remove duplicate / partial paragraph in installation docs by @emilkje in https://github.com/crossplane/crossplane/pull/3474
Fix out of sync code generation and always run check-diff by @hasheddan in https://github.com/crossplane/crossplane/pull/3508
Update build submodule with docs hot reloading by @hasheddan in https://github.com/crossplane/crossplane/pull/3512
Update build submodule with fixes for docs generation by @hasheddan in https://github.com/crossplane/crossplane/pull/3513
fix(transforms): add match to kubebuilder enum by @pysysops in https://github.com/crossplane/crossplane/pull/3515
Update docs styling guidelines for code blocks by @plumbis in https://github.com/crossplane/crossplane/pull/3497
Move all Patch and Transform logic to the XR controller by @negz in https://github.com/crossplane/crossplane/pull/3472
Docs: Fiz docs about readinessChecks in the MatchInteger code snippet… by @rafaeldomi in https://github.com/crossplane/crossplane/pull/3524
Add agent-inject to crossplane itself by @jonnylangefeld in https://github.com/crossplane/crossplane/pull/3521
Add a docs issue template to auto tag doc bugs by @plumbis in https://github.com/crossplane/crossplane/pull/3460
Ignore Zone.Identifier files. Resolves #3535 by @plumbis in https://github.com/crossplane/crossplane/pull/3536
Add a tutorial doc for composition revisions by @ezgidemirel in https://github.com/crossplane/crossplane/pull/3501
feat(compositions): Support patching from Environment by @MisterMX in https://github.com/crossplane/crossplane/pull/3007
Update docs guide to cover recent functions by @plumbis in https://github.com/crossplane/crossplane/pull/3537
Use serviceAccountName for Service Account creation by @micnncim in https://github.com/crossplane/crossplane/pull/2880
Fix get namespace error message by @hasheddan in https://github.com/crossplane/crossplane/pull/3557
feat: Added commonLabel to label resources applied via Configuration by @akesser in https://github.com/crossplane/crossplane/pull/3556
Add commentary for spec.serviceAccountName in ControllerConfig by @micnncim in https://github.com/crossplane/crossplane/pull/3559
docs: fix typo by @phisco in https://github.com/crossplane/crossplane/pull/3561
fix: bump dependencies to fix CVEs by @phisco in https://github.com/crossplane/crossplane/pull/3563
Infra changes to move docs out by @plumbis in https://github.com/crossplane/crossplane/pull/3538
Add links to docs issues, support requests by @negz in https://github.com/crossplane/crossplane/pull/3564
Restore packagePullPolicy Always polling behavior by @hasheddan in https://github.com/crossplane/crossplane/pull/3581
feat(transform): Add ToJson string conversion by @MisterMX in https://github.com/crossplane/crossplane/pull/3458
Update release date for v1.11.0 by @hasheddan in https://github.com/crossplane/crossplane/pull/3587
Regenerate Composition CRD by @hasheddan in https://github.com/crossplane/crossplane/pull/3589
Fix 404 on Helm chart icon by @undera in https://github.com/crossplane/crossplane/pull/3588
Fix constant reconciles on inactive package revisions by @hasheddan in https://github.com/crossplane/crossplane/pull/3582
publish to upbound marketplace by @nullable-eth in https://github.com/crossplane/crossplane/pull/3568
Remove docs dir and move packages & meta CRDs to cluster dir by @hasheddan in https://github.com/crossplane/crossplane/pull/3597
Fix flaky unit test by using approximate time comparison by @hasheddan in https://github.com/crossplane/crossplane/pull/3599
Support running Containerized Composition functions by @negz in https://github.com/crossplane/crossplane/pull/3465
ci: renovate configuration by @phisco in https://github.com/crossplane/crossplane/pull/3575
Update gcr.io/distroless/static Docker digest to 11364b4 (master) by @renovate in https://github.com/crossplane/crossplane/pull/3610
Update module github.com/containerd/containerd to v1.6.12 [SECURITY] (master) by @renovate in https://github.com/crossplane/crossplane/pull/3606
Pin dependencies (master) by @renovate in https://github.com/crossplane/crossplane/pull/3607
Update all non-major github action (master) by @renovate in https://github.com/crossplane/crossplane/pull/3618
ci: set renovate to also handle go digests by @phisco in https://github.com/crossplane/crossplane/pull/3616
ci: set xfn base image tag too by @phisco in https://github.com/crossplane/crossplane/pull/3613
Update actions/cache action to v3 (master) by @renovate in https://github.com/crossplane/crossplane/pull/3623
feat(transform): Allow converting string to float as resource.Quantity by @MisterMX in https://github.com/crossplane/crossplane/pull/3316
Update actions/checkout action to v3 (master) by @renovate in https://github.com/crossplane/crossplane/pull/3624
Update actions/setup-go action to v3 (master) by @renovate in https://github.com/crossplane/crossplane/pull/3626
Update actions/stale action to v7 (master) by @renovate in https://github.com/crossplane/crossplane/pull/3627
Update codecov/codecov-action action to v3 (master) by @renovate in https://github.com/crossplane/crossplane/pull/3630
Update actions/upload-artifact action to v3 (master) by @renovate in https://github.com/crossplane/crossplane/pull/3629
Update docker/login-action action to v2 (master) by @renovate in https://github.com/crossplane/crossplane/pull/3632
Update docker/setup-buildx-action action to v2 (master) by @renovate in https://github.com/crossplane/crossplane/pull/3633
feat(transform): Add hash string conversion by @MisterMX in https://github.com/crossplane/crossplane/pull/3498
ci: remove 1.8 from renovate's target branches by @phisco in https://github.com/crossplane/crossplane/pull/3637
Add @phisco to reviewers by @negz in https://github.com/crossplane/crossplane/pull/3640
Pin to Go 1.19.5 by @hasheddan in https://github.com/crossplane/crossplane/pull/3639
Update docker/setup-qemu-action action to v2 (master) by @renovate in https://github.com/crossplane/crossplane/pull/3635
Update fkirc/skip-duplicate-actions action to v5 (master) by @renovate in https://github.com/crossplane/crossplane/pull/3636
Update github/codeql-action action to v2 (master) by @renovate in https://github.com/crossplane/crossplane/pull/3642
Update gcr.io/distroless/static Docker digest to c79ef2d (master) by @renovate in https://github.com/crossplane/crossplane/pull/3643
Resurrect contributing docs and README banner by @negz in https://github.com/crossplane/crossplane/pull/3634
Update golangci/golangci-lint-action action to v3 (master) by @renovate in https://github.com/crossplane/crossplane/pull/3645
fuzzing: run fuzzers in CI by @AdamKorcz in https://github.com/crossplane/crossplane/pull/3553
Make CodeQL part of the CI workflow, reduce Fuzzing to 5 mins from 10 by @negz in https://github.com/crossplane/crossplane/pull/3644
Update zeebe-io/backport-action action to v1 (master) by @renovate in https://github.com/crossplane/crossplane/pull/3647
Update xt0rted/slash-command-action action to v2 (master) by @renovate in https://github.com/crossplane/crossplane/pull/3648
Update google/oss-fuzz digest to 700fd90 (master) by @renovate in https://github.com/crossplane/crossplane/pull/3649
Use the same version of upload-artifact everywhere by @negz in https://github.com/crossplane/crossplane/pull/3650
Update gcr.io/distroless/static Docker digest to 5bda5a4 (master) by @renovate in https://github.com/crossplane/crossplane/pull/3652
Have CodeQL job use the Go dep and build cache by @negz in https://github.com/crossplane/crossplane/pull/3653
chore: renovate handling golangci-lint version in makefile by @phisco in https://github.com/crossplane/crossplane/pull/3651
Update dependency golangci/golangci-lint to v1.50.1 (master) by @renovate in https://github.com/crossplane/crossplane/pull/3657
Tell golangci-lint action not to try to cache by @negz in https://github.com/crossplane/crossplane/pull/3658
ci: configure renovate to ignore oss-fuzz action updates by @phisco in https://github.com/crossplane/crossplane/pull/3663
ci: add trivy filesystem scan job by @phisco in https://github.com/crossplane/crossplane/pull/3665
Add fuzzer in Xcrd package by @AdamKorcz in https://github.com/crossplane/crossplane/pull/3445
Bump crossplane-runtime, controller-runtime, and kubernetes deps by @negz in https://github.com/crossplane/crossplane/pull/3659
Pin aquasecurity/trivy-action action to 9ab158e (master) by @renovate in https://github.com/crossplane/crossplane/pull/3672
Update github/codeql-action digest to 3ebbd71 (master) by @renovate in https://github.com/crossplane/crossplane/pull/3673
Mark ControllerConfing API as deprecated by @hasheddan in https://github.com/crossplane/crossplane/pull/3678

New Contributors

@ezgidemirel made their first contribution in https://github.com/crossplane/crossplane/pull/3376
@apj0nes made their first contribution in https://github.com/crossplane/crossplane/pull/3412
@jmprusi made their first contribution in https://github.com/crossplane/crossplane/pull/3409
@nickbeaugie made their first contribution in https://github.com/crossplane/crossplane/pull/3424
@shazib-summar made their first contribution in https://github.com/crossplane/crossplane/pull/3411
@mplzik made their first contribution in https://github.com/crossplane/crossplane/pull/3434
@eloo-abi made their first contribution in https://github.com/crossplane/crossplane/pull/3364
@clementblaise made their first contribution in https://github.com/crossplane/crossplane/pull/3428
@csantanapr made their first contribution in https://github.com/crossplane/crossplane/pull/3464
@emilkje made their first contribution in https://github.com/crossplane/crossplane/pull/3474
@pysysops made their first contribution in https://github.com/crossplane/crossplane/pull/3515
@rafaeldomi made their first contribution in https://github.com/crossplane/crossplane/pull/3524
@jonnylangefeld made their first contribution in https://github.com/crossplane/crossplane/pull/3521
@micnncim made their first contribution in https://github.com/crossplane/crossplane/pull/2880
@akesser made their first contribution in https://github.com/crossplane/crossplane/pull/3556
@undera made their first contribution in https://github.com/crossplane/crossplane/pull/3588
@nullable-eth made their first contribution in https://github.com/crossplane/crossplane/pull/3568
@AdamKorcz made their first contribution in https://github.com/crossplane/crossplane/pull/3553

Full Changelog: https://github.com/crossplane/crossplane/compare/v1.10.0...v1.11.0

Source code(tar.gz)
Source code(zip)

v1.10.2(Jan 19, 2023)

The v1.10.2 release includes fixes for restoring the documented packagePullPolicy: Always behavior (https://github.com/crossplane/crossplane/pull/3581) as well as a follow-up fix to https://github.com/crossplane/crossplane/pull/3426 for constantly enqueued reconciles for ProviderRevisions marked as Inactive (https://github.com/crossplane/crossplane/pull/3582). There were also numerous documentation fixes and minor dependency updates.

What's Changed

[Backport release-1.10] CLI install script: prefix variables by @github-actions in https://github.com/crossplane/crossplane/pull/3446
[Backport release-1.10] fix broken link to helm provider by @github-actions in https://github.com/crossplane/crossplane/pull/3469
[Backport release-1.10] fix all broken links in install-configure by @github-actions in https://github.com/crossplane/crossplane/pull/3478
Update v1.10 docs content to conform to new docs.crossplane.io by @plumbis in https://github.com/crossplane/crossplane/pull/3485
[Backport release-1.10] Add missing word by @github-actions in https://github.com/crossplane/crossplane/pull/3495
[Backport release-1.10] Fix enabling external secret stores in guide by @github-actions in https://github.com/crossplane/crossplane/pull/3500
[release-1.10] Rename docs repo (#3502) by @hasheddan in https://github.com/crossplane/crossplane/pull/3503
[Backport release-1.10] remove duplicate / partial paragraph in installation docs by @github-actions in https://github.com/crossplane/crossplane/pull/3507
[release-1.10] Fix docs generation and always run check-diff by @hasheddan in https://github.com/crossplane/crossplane/pull/3510
[Backport release-1.10] Docs: Fiz docs about readinessChecks in the MatchInteger code snippet… by @github-actions in https://github.com/crossplane/crossplane/pull/3527
[Backport release-1.10] Add agent-inject to crossplane itself by @github-actions in https://github.com/crossplane/crossplane/pull/3528
chore: bump dependencies due to CVEs by @phisco in https://github.com/crossplane/crossplane/pull/3572
[Backport release-1.10] Restore packagePullPolicy Always polling behavior by @github-actions in https://github.com/crossplane/crossplane/pull/3586
[release-1.10] Do not publish docs to documentation repo by @hasheddan in https://github.com/crossplane/crossplane/pull/3578
[Backport release-1.10] Fix 404 on Helm chart icon by @github-actions in https://github.com/crossplane/crossplane/pull/3592
[Backport release-1.10] Fix constant reconciles on inactive package revisions by @github-actions in https://github.com/crossplane/crossplane/pull/3593

Full Changelog: https://github.com/crossplane/crossplane/compare/v1.10.1...v1.10.2

Source code(tar.gz)
Source code(zip)

🐶 Kubernetes CLI To Manage Your Clusters In Style!

DevSpace - The Fastest Developer Tool for Kubernetes ⚡ Automate your deployment workflow with DevSpace and develop software directly inside Kubernetes.

A Kubernetes operator to manage ThousandEyes tests

Kubernetes integration with Spring Cloud Discovery Client, Configuration, etc...

Manage any infrastructure your applications need directly from Kubernetes

OpenYurt - Extending your native Kubernetes to edge

A standard infrastructure environment for Kubernetes

General-purpose web UI for Kubernetes clusters

AWS Controllers for Kubernetes (ACK) is a project enabling you to manage AWS services from Kubernetes

Tanzu Community Edition is a fully-featured, easy to manage, Kubernetes platform for learners and users.

Find security vulnerabilities, compliance issues, and infrastructure misconfigurations early in the development cycle of your infrastructure-as-code with KICS by Checkmarx.

AppScale is an easy-to-manage serverless platform for building and running scalable web and mobile applications on any infrastructure.

Pulumi - Modern Infrastructure as Code. Any cloud, any language 🚀

PolarDB-X Operator is a Kubernetes extension that aims to create and manage PolarDB-X cluster on Kubernetes.

The Central Kubernetes Management Platform For Any Infrastructure

Running Terraform in Kubernetes as a controller

Manage Lets Encrypt certificates for a Kubernetes cluster.

A toolkit for creating and managing declarative, self-healing infrastructure.

Gyro is a command-line tool for creating, updating, and maintaining cloud infrastructure. Gyro makes infrastructure-as-code possible.

Detect compliance and security violations across Infrastructure as Code to mitigate risk before provisioning cloud native infrastructure.

KEDA is a Kubernetes-based Event Driven Autoscaling component. It provides event driven scale for any container running in Kubernetes

Share this repo

Related Repos

Utilities

268

A collection of convenient SQL for monitoring Postgres database health.

pg_insights Convenient SQL for monitoring Postgres database health. This repository is inspired by commands from Heroku's pg_extras repository. How to

Utilities

Command-line tool to organize large directories of media files recursively by date, detect...

go-media-organizer Command-line tool written in Go to organise all media files in a directory recursively by date, detecting duplicates. Features Orga

Utilities

1.5k

Automatically update your Windows hosts file with the WSL2 VM IP address

Utilities

Go implementation of the venerable dropwatch utility

dropspy dropspy is a (POC-quality) reworking of the C-language dropwatch tool in Go, with some extra features. This is currently potato code and I mak

Utilities

first swing at dapptools that ended in failure

fmuldiv I wanted to try writing the fixed point math algos for multiplication and division in pure assembly, then call them from within solidity. The

Utilities

2.9k

微信、支付宝、PayPal、QQ 的 Golang 版本SDK

微信、支付宝、PayPal 的Go版本SDK。【极简、易用的聚合支付SDK】

Utilities

133

Fully featured, spec-compliant HTML5 server-sent events library

go-sse Lightweight, fully spec-compliant HTML5 server-sent events library. Table of contents go-sse Table of contents Installation and usage Implement

Utilities

6.8k

Manage any infrastructure your applications need directly from Kubernetes

Crossplane is an open source Kubernetes add-on that enables platform teams to assemble infrastructure from multiple vendors, and expose higher level self-service APIs for application teams to consume

Utilities

784

Go library providing algorithms optimized to leverage the characteristics of modern CPUs