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

Duplicate annotations field in deployment in the Helm Chart #9082

Closed
vliska opened this issue Jun 6, 2023 · 1 comment
Closed

Duplicate annotations field in deployment in the Helm Chart #9082

vliska opened this issue Jun 6, 2023 · 1 comment

Comments

@vliska
Copy link

vliska commented Jun 6, 2023

Describe the bug

Can't install 3.2.0 helmrelease of apim3 in fluxcd (or any tool that actually validates the helm chart/rendered manifests prior installation) due to:

Helm upgrade failed: error while running post render on files: map[string]interface {}(nil): yaml: unmarshal errors:
line 36: mapping key "annotations" already defined at line 28

it's due to duplicate annotations section in ui-deployment.yaml: https://github.com/gravitee-io/helm-charts/blob/master/apim/3.x/templates/ui/ui-deployment.yaml#L55 https://github.com/gravitee-io/helm-charts/blob/master/apim/3.x/templates/ui/ui-deployment.yaml#L82

Whole section with common annotations is present twice (probably copy+paste error).

To Reproduce

Try to install apim3 via e.g. flux or

Expected behaviour

A clear and concise description of what you expected to happen.

Current behaviour

Can't install apim3 version 3.2.0 via helm chart.

Environment

helm 3.x fluxcd 2.0.0-rc.5

What is the impacted version?

3.2.0

Potential impacts

Can't install gravitee apim3.

@vliska vliska changed the title apim3 - duplicate field annotations in deployment [helm] apim3 - duplicate field annotations in deployment Jun 6, 2023
@vliska vliska changed the title [helm] apim3 - duplicate field annotations in deployment [helm chart] apim3 - duplicate field annotations in deployment Jun 7, 2023
@gaetanmaisse
Copy link
Contributor

Thanks for the PR @vliska, we are currently moving the APIM Helm Charts into the api-management repository (that will be public again in the next couple of weeks), so merging your PR might take some extra time. In any case, we will take care of it by the end of next week!

sebdevaux added a commit to gravitee-io/gravitee-api-management that referenced this issue Jun 8, 2023
sebdevaux added a commit to gravitee-io/gravitee-api-management that referenced this issue Jun 8, 2023
sebdevaux added a commit to gravitee-io/gravitee-api-management that referenced this issue Jun 8, 2023
sebdevaux added a commit to gravitee-io/gravitee-api-management that referenced this issue Jun 8, 2023
gaetanmaisse pushed a commit to gravitee-io/gravitee-api-management that referenced this issue Jun 8, 2023
gaetanmaisse pushed a commit to gravitee-io/gravitee-api-management that referenced this issue Jun 8, 2023
gaetanmaisse pushed a commit to gravitee-io/gravitee-api-management that referenced this issue Jun 8, 2023
@exalate-issue-sync exalate-issue-sync bot changed the title [helm chart] apim3 - duplicate field annotations in deployment Duplicate annotations field in deployment in the Helm Chart Jun 8, 2023
Okhelifi pushed a commit to gravitee-io/gravitee-api-management that referenced this issue Jun 8, 2023
gaetanmaisse added a commit to gravitee-io/gravitee-api-management that referenced this issue Jun 8, 2023
gaetanmaisse added a commit to gravitee-io/gravitee-api-management that referenced this issue Jun 8, 2023
gaetanmaisse added a commit to gravitee-io/gravitee-api-management that referenced this issue Jun 8, 2023
sebdevaux added a commit to gravitee-io/gravitee-api-management that referenced this issue Jun 9, 2023
gaetanmaisse added a commit to gravitee-io/gravitee-api-management that referenced this issue Jun 16, 2023
gaetanmaisse added a commit to gravitee-io/gravitee-api-management that referenced this issue Jun 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants