Convert Kaniko template to CI component

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Collaborate/take over this issue

Summary

The purpose of this issue is to convert the current Kaniko template to a component to be shared in the Catalog.

Proposal

Converting this template into a component and releasing it to the catalog to be shared with the community.

NOTE: If there is a group at GitLab that can or wants to maintain this component, it could be considered as a candidate to move into https://gitlab.com/components.

Confirm purpose and User Reception (how does this benefit the user?)

By having this component available, it allows others to use it in their pipeline and additionally, they can contribute to future improvements to the component itself.

Work to Be Done

This is the list of work required to completely replace the existing Kaniko template with a component. These is future work that could be done as well to further push the envelopes (optional image pushing, image build layer caching, supplying custom registry credentials, the ability to customize K8s resource allocations and exporting generated variable values as a dotenv report are a few that come to mind.)

• Basic /Dockerfile building and pushing.
• Custom image tagging logic.
• Optional build file auto-discovery.
• Additional Kaniko CLI parameter passing.