Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

[requirement] Enhance the ingress resource to support the old and new API #8

Open
cmoulliard opened this issue Jun 21, 2022 · 0 comments

Comments

@cmoulliard
Copy link
Contributor

Requirement

Enhance the ingress resource to support the old deprecated API and the new

As the bitnami common.capabilities.ingress.apiVersion function is able to return the appropriate apiVersion for ingress which could be:

  • extensions/v1beta1,
  • networking.k8s.io/v1beta1
  • networking.k8s.io/v1 (latest supported)

then additional logic will be needed to support to populate the correct Backend or PathType sections of the Ingress.spec

Notable changes concerning the new API are:

  • spec.backend is renamed to spec.defaultBackend
  • The backend serviceName field is renamed to service.name
  • Numeric backend servicePort fields are renamed to service.port.number
  • String backend servicePort fields are renamed to service.port.name
  • pathType is now required for each specified path. Options are Prefix, Exact, and ImplementationSpecific. To match the undefined v1beta1 behavior, use ImplementationSpecific.
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant