Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow patching of objects belonging to an existing bundle objects on cluster #672

Open
varshaprasad96 opened this issue Aug 3, 2023 · 1 comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@varshaprasad96
Copy link
Member

Enable patching of resources on cluster after a bundle deployment (and bundle) has been created.

Users would like to be able to add a label to existing resources on cluster belonging to a bundle. Currently, it errors out with:

- lastTransitionTime: "2023-08-03T11:44:06Z"
      message: 'rendered manifests contain a resource that already exists. Unable
        to continue with update: Namespace "default" in namespace "" exists and cannot
        be imported into the current release: invalid ownership metadata; label validation
        error: missing key "app.kubernetes.io/managed-by": must be set to "Helm";
        annotation validation error: missing key "meta.helm.sh/release-name": must
        be set to "reference-addon"; annotation validation error: missing key "meta.helm.sh/release-namespace":
        must be set to "rukpak-system"'
      reason: ErrorGettingReleaseState
      status: "False"
      type: Installed
@varshaprasad96 varshaprasad96 changed the title Allow patching of objects existing bundle objects on cluster Allow patching of objects belonging to an existing bundle objects on cluster Aug 3, 2023
@github-actions
Copy link

github-actions bot commented Oct 3, 2023

This issue has become stale because it has been open 60 days with no activity. The maintainers of this repo will remove this label during issue triage or it will be removed automatically after an update. Adding the lifecycle/frozen label will cause this issue to ignore lifecycle events.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

1 participant