Skip to content

feat: refactor ingress controller build / push process #81

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

Closed
qdzlug opened this issue Feb 2, 2022 · 1 comment
Closed

feat: refactor ingress controller build / push process #81

qdzlug opened this issue Feb 2, 2022 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@qdzlug
Copy link
Contributor

qdzlug commented Feb 2, 2022

Is your feature request related to a problem? Please describe.
The current process is tied to the use of ECR as a container registry.

Describe the solution you'd like
The build process should handle:

  • Build / pull plus enabled IC
  • Build / pull standard IC
  • Build / pull upstream IC (potentially?)

Additionally, it should be able to use any registry for pushing the resulting artifact(s).

This solution should also include necessary connectors for the IC deployment process (see #80 for details on some of the issues there)

Describe alternatives you've considered
Currently using the JWT and the NGINX corp repo, but this doesn't include all use cases.

Additional context
None.

@qdzlug
Copy link
Contributor Author

qdzlug commented Aug 31, 2022

This is closed by #167

@qdzlug qdzlug closed this as completed Aug 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant