Skip to content

Update existing ManagedServiceAccount resources when the user changes the tokenValidity on the mesh #120

Description

@yxun

Currently, if the ManagedServiceAccount exists in a managed cluster namespace, we skip following updates from the mesh controller reconciliation.
If the user changes the tokenValidity field value on the mesh CR spec, we should update the existing ManagedServiceAccount resource(s)' spec value instead of using the old value.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions