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

Extra Config's CM/Secret references to particular Backstage instance even if it is deleted #358

Open
gazarenkov opened this issue May 14, 2024 · 0 comments
Labels
jira Issue will be sync'ed to Red Hat JIRA kind/bug Categorizes issue or PR as related to a bug. priority/medium Nice to have issue. Getting it done before priority changes would be great.

Comments

@gazarenkov
Copy link
Member

Related to Pod recrearing feature: #236

Steps to reproduce:

  • Create "bs1" Backstage CR with extra CM / Secret config (with application.appConfig|extraFiles|extraEnvs)
  • Make sure Pod is recreating on configuration changes
  • Delete bs1
  • Create the same CR with other name (e g "bs2")
  • Pod auto-recreating will not work because CM/Secret is still annotated with rhdh.redhat.com/backstage-name=bs1 annotation
@gazarenkov gazarenkov added kind/bug Categorizes issue or PR as related to a bug. priority/medium Nice to have issue. Getting it done before priority changes would be great. labels May 14, 2024
@github-actions github-actions bot added the jira Issue will be sync'ed to Red Hat JIRA label May 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
jira Issue will be sync'ed to Red Hat JIRA kind/bug Categorizes issue or PR as related to a bug. priority/medium Nice to have issue. Getting it done before priority changes would be great.
Projects
None yet
Development

No branches or pull requests

1 participant