Shared Resource

    So there are basically two requirements for application creating resources:

    1. The resource must not exist before the application creating it. It exists, there will be a resource conflict error.
    2. The resource is expected to be only manageable through its creator. Others should not be able to modify it or edit it.

    While dispatching resources, the application will

    1. Check if resource exists. If exists, check its labels. If and app.oam.dev/namespace equals to the application’s name and namespace, it means this resource is previously created by the same application and the dispatching operation now will become an update operation. The two labels identify the owner of the resource.
    2. If resource exists, but no label found, then this resource is created before this application. At this time, the application will report a resource conflict error.
    3. If resource exists, and the labels point to another application, then this resource is managed by other applications. At this time, the current application will also report a resource conflict error. With these checks, different applications cannot manage the same resource.

    However, there are scenarios that these two requirements are not met. One of the scenarios is sharing across different Applications.

    For example, each application wants to create a ConfigMap, but their ConfigMaps are the same.

    To achieve that, KubeVela application could utilize the shared-resource policy to make it possible.

    When one resource is created as sharing resource, one special annotation app.oam.dev/shared-by will be added to the resource. It will record the sharer of the resource in time order. The application that firstly creates the resource will set its owner labels to itself.

    When another application comes and wants to share the resource, it will check if the resource is sharable, aka there is at least one sharer in the sharer annotation.

    If it is sharable, it will add itself to the sharer annotation, but not modify the content of the resource.

    With this mechanism, only the owner of the resource can modify the resource (including updating and state-keeping). Other sharer can only see that resource.

    When the owner of the resource is gone (application is deleted or do not use this resource anymore), it will give the owner of the application to the next sharer. If no sharer exists, it will finally delete that resource.

    See the following figures for details.

    1. apiVersion: core.oam.dev/v1beta1
    2. kind: Application
    3. metadata:
    4.   name: app2
    5. spec:
    6.   components:
    7.     - name: ns2
    9.         objects:
    10.           - apiVersion: v1
    11.             kind: Namespace
    12.             metadata:
    13.               name: example
    14.     - name: cm2
    15.       type: k8s-objects
    16.       properties:
    17.         objects:
    18.           - apiVersion: v1
    19.             kind: ConfigMap
    20.               name: cm2
    21.               namespace: example
    22.             data:
    23.               key: value2
    24.   policies:
    25.     - name: shared-resource
    26.       type: shared-resource
    27.       properties:
    28.         rules:
    29.           - selector:
    30.               resourceTypes: ["Namespace"]

    The above two applications will dispatch the same namespace “example”. They will create two different ConfigMap inside namespace “example” respectively.

    Both application use the shared-resource policy and declared the namespace resource as shared. In this way, there will be no conflict for creating the same namespace. If the shared-resource policy is not used, the second application will report error after it finds that the namespace “example” is managed by the first application.

    The namespace will only be recycled when both applications are removed.

    1. When multiple applications share the same resource, the first one who creates it can make updates to its content. The others cannot modify it. Once the first application does not use it anymore (for example, the first application is deleted), then the second one will become the owner, which means it is now able to modify the content. This will not take effect immediately. But when StateKeep happens, or application re-runs its workflow (for example, it is updated), it will set the resource content to be its desired state.