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

Operator fails to find "harbor" named instance resources #100

Open
Hell-Fire opened this issue Oct 15, 2022 · 1 comment
Open

Operator fails to find "harbor" named instance resources #100

Hell-Fire opened this issue Oct 15, 2022 · 1 comment
Labels
bug Something isn't working

Comments

@Hell-Fire
Copy link

If you create an instance called "harbor", the harbor helm chart drops the "$RELEASENAME-harbor" behaviour for naming, and instead just uses the release name, so resources end up being "harbor-core" instead of "harbor-harbor-core".

Deploying the operator by chart, relevant values.yaml passed to the operator:

    instances:
    - name: harbor
      type: manual
      helmChart:
        release: harbor

I'm not sure this should actually be fixed/worked around by the operator, since the upstream chart is the one causing the behaviour, but it might be unlikely to change upstream as the logic on the name calculation is non-trivial. The upstream chart does offer overrides to that logic there (fullnameOverride, nameOverride), so perhaps it's worth using those to enforce what the operator installs ends up at names that the api_client.go library is expecting it to be.

Kubernetes Server version: v1.24.3+k3s1

@Hell-Fire Hell-Fire added the bug Something isn't working label Oct 15, 2022
@Hell-Fire
Copy link
Author

Ahh, ignore the helmChart part in my example, it doesn't get used in the operator helm chart, but instance name does.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant