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

Automatic restart naming conflict in single application #226

Closed
lobis opened this issue Feb 6, 2025 · 1 comment · Fixed by #227
Closed

Automatic restart naming conflict in single application #226

lobis opened this issue Feb 6, 2025 · 1 comment · Fixed by #227
Assignees

Comments

@lobis
Copy link
Contributor

lobis commented Feb 6, 2025

When deploying rucio as a single application such as:

type: application

dependencies:
- name: rucio-server
  repository: https://rucio.github.io/helm-charts

- name: rucio-server
  repository: https://rucio.github.io/helm-charts
  alias: rucio-auth

- name: rucio-daemons
  repository: https://rucio.github.io/helm-charts

- name: rucio-ui
  repository: https://rucio.github.io/helm-charts

Some entities such as cronjobs, role bindings, etc. all share the same name prepended by the helm release. This is a problem in this pattern as there will be a naming conflict resulting in some of these entities not being created or possibly an error.

I will make a PR prepending some additional string to fix this.

@lobis
Copy link
Contributor Author

lobis commented Feb 6, 2025

Also related to #217

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging a pull request may close this issue.

1 participant