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.

Sign up for GitHub

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

Jump to bottom

Ingress ServiceBackendPort: "use-annotation" got "string", expected "integer" #581 #43

Open
cbuto opened this issue Apr 29, 2022 · 1 comment · May be fixed by #60
Open

Ingress ServiceBackendPort: "use-annotation" got "string", expected "integer" #581 #43

cbuto opened this issue Apr 29, 2022 · 1 comment · May be fixed by #60
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@cbuto
Copy link
Collaborator

cbuto commented Apr 29, 2022

From @cpboyd (helm/chartmuseum#581)

From https://artifacthub.io/packages/helm/chartmuseum/chartmuseum#extra-paths:

helm install my-chartmuseum chartmuseum/chartmuseum \
  --set ingress.enabled=true \
  --set ingress.hosts[0].name=chartmuseum.domain.com \
  --set ingress.extraPaths[0].service=ssl-redirect \
  --set ingress.extraPaths[0].port=use-annotation \

This, however, results in the following error:

Error: INSTALLATION FAILED: unable to build kubernetes objects from release manifest: error validating "": error validating data: ValidationError(Ingress.spec.rules[0].http.paths[0].backend.service.port.number): invalid type for io.k8s.api.networking.v1.ServiceBackendPort.number: got "string", expected "integer"

Replacing use-annotation with an integer works, but it'd be nice to simply refer to port defined in the policy.
@cbuto cbuto added enhancement New feature or request good first issue Good for newcomers labels Apr 29, 2022
@cbuto cbuto mentioned this issue Apr 29, 2022
Closed
@cbuto
Copy link
Collaborator Author

cbuto commented Apr 29, 2022

Thanks again for bring this up @cpboyd, this is related to #37.

@mike7515 are you still interested in working on a fix for this? thanks!

@cpboyd cpboyd mentioned this issue May 3, 2022
Closed
@cpboyd cpboyd linked a pull request Feb 3, 2023 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Milestone
No milestone
1 participant
@cbuto