go-vela / vela-kaniko

Docker Plugin using Kaniko for Vela (Target's official Pipeline Automation Framework)

vela-kaniko

Vela plugin designed for building and publishing Docker images.

Internally, the plugin is a wrapper around the kaniko CLI.

Documentation

For installation and usage, please visit our docs.

Contributing

We are always welcome to new pull requests!

Please see our contributing docs for further instructions.

Support

We are always here to help!

Please see our support documentation for further instructions.

Copyright and License

Copyright 2019 Target Brands, Inc.

Apache License, Version 2.0

vela-kaniko's Issues

Improve test coverage

Description

What is your idea?

Improve test coverage to > 90%

NOTE: This includes nested packages!

Value

Why is this important? Who does it impact? Will this make something better, faster, etc?

• Reduces technical debt
• Decrease the potential for bugs

Definition of Done

What is the end goal of this story?

The plugin and all nested pkgs have > 90% test coverage

Effort (Optional)

Estimated effort to complete this story? (Best Guess e.g. 1-2 days)

N/A

Issue with building a docker image that includes symlinks

Description

There is an issue from kaniko when building a docker image that includes symlinks. This is fixed in 0.19.0 version of kaniko

Value

Will allow images that are utilizing symlinks to be build by vela

Effort

<1 Day

Add the ability to use the target flag

Description

What is your idea?

Add the ability to use the target flag in kaniko

Flag documentation:
https://github.com/GoogleContainerTools/kaniko/#--target

Value

Why is this important? Who does it impact? Will this make something better, faster, etc?

Customers using the docker CLI may be using the --target we need to add support for kaniko's equivalent flag.

Definition of Done

What is the end goal of this story?

The flag is useable in the plugins

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update all non-major dependencies (codecov/codecov-action, github/codeql-action)

Detected dependencies

dockerfile

Dockerfile

• alpine 3.19.1@sha256:c5b1261d6d3e43071626931fc004f70149baeba2c8ec672bd4f27761f8e1ad6b
• gcr.io/kaniko-project/executor v1.22.0-debug@sha256:7b3699e9e105521075812cd3f3f4c62c913cb5cd113c929975502022df3bcf60

Dockerfile.example

• alpine 3.19.1@sha256:c5b1261d6d3e43071626931fc004f70149baeba2c8ec672bd4f27761f8e1ad6b
• alpine 3.19.1@sha256:c5b1261d6d3e43071626931fc004f70149baeba2c8ec672bd4f27761f8e1ad6b

github-actions

.github/workflows/build.yml

• actions/checkout v4.1.1@b4ffde65f46336ab88eb53be808477a3936bae11
• actions/setup-go v5.0.0@0c52d547c9bc32b1aa3301fd7a9cb496313a4491

.github/workflows/codeql-analysis.yml

• actions/checkout v4.1.1@b4ffde65f46336ab88eb53be808477a3936bae11
• github/codeql-action v3.24.9@1b1aada464948af03b950897e5eb522f92603cc2
• github/codeql-action v3.24.9@1b1aada464948af03b950897e5eb522f92603cc2
• github/codeql-action v3.24.9@1b1aada464948af03b950897e5eb522f92603cc2

.github/workflows/prerelease.yml

• actions/checkout v4.1.1@b4ffde65f46336ab88eb53be808477a3936bae11
• actions/setup-go v5.0.0@0c52d547c9bc32b1aa3301fd7a9cb496313a4491
• elgohr/Publish-Docker-Github-Action v5@eb53b3ec07136a6ebaed78d8135806da64f7c7e2

.github/workflows/publish.yml

• actions/checkout v4.1.1@b4ffde65f46336ab88eb53be808477a3936bae11
• actions/setup-go v5.0.0@0c52d547c9bc32b1aa3301fd7a9cb496313a4491
• elgohr/Publish-Docker-Github-Action v5@eb53b3ec07136a6ebaed78d8135806da64f7c7e2

.github/workflows/reviewdog.yml

• actions/checkout v4.1.1@b4ffde65f46336ab88eb53be808477a3936bae11
• actions/setup-go v5.0.0@0c52d547c9bc32b1aa3301fd7a9cb496313a4491
• reviewdog/action-golangci-lint v2.6.1@00311c26a97213f93f2fd3a3524d66762e956ae0
• actions/checkout v4.1.1@b4ffde65f46336ab88eb53be808477a3936bae11
• actions/setup-go v5.0.0@0c52d547c9bc32b1aa3301fd7a9cb496313a4491
• reviewdog/action-golangci-lint v2.6.1@00311c26a97213f93f2fd3a3524d66762e956ae0

.github/workflows/test.yml

• actions/checkout v4.1.1@b4ffde65f46336ab88eb53be808477a3936bae11
• actions/setup-go v5.0.0@0c52d547c9bc32b1aa3301fd7a9cb496313a4491
• codecov/codecov-action v4.1.1@c16abc29c95fcf9174b58eb7e1abf4c866893bc8

.github/workflows/validate.yml

• actions/checkout v4.1.1@b4ffde65f46336ab88eb53be808477a3936bae11
• actions/setup-go v5.0.0@0c52d547c9bc32b1aa3301fd7a9cb496313a4491

gomod

go.mod

• go 1.21
• github.com/Masterminds/semver/v3 v3.2.1
• github.com/go-vela/types v0.23.3
• github.com/joho/godotenv v1.5.1
• github.com/sirupsen/logrus v1.9.3
• github.com/spf13/afero v1.11.0
• github.com/urfave/cli/v2 v2.27.1

---

• Check this box to trigger a request for Renovate to run again on this repository

Add the ability to use the registry mirror flag

Description

What is your idea?

Add the ability to use the registry-mirror flag in kaniko

Flag documentation:
https://github.com/GoogleContainerTools/kaniko#--registry-mirror

Value

Why is this important? Who does it impact? Will this make something better, faster, etc?

Allow users to pull from a different mirror other than the default --registry-mirror

Definition of Done

What is the end goal of this story?

The flag is useable in the plugins

Update urfave/cli to v2

Description

What is your idea?

Update our urfave/cli library to the v2 functionality.

https://github.com/urfave/cli#using-v2-releases

Value

Why is this important? Who does it impact? Will this make something better, faster, etc?

• Reduce technical debt

Definition of Done

What is the end goal of this story?

This repo is using the v2 branch of the urfave/cli library.

Effort (Optional)

Estimated effort to complete this story? (Best Guess e.g. 1-2 days)

N/A

Action Required: Fix Renovate Configuration

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: undefined. Note: this is a nested preset so please contact the preset author if you are unable to fix it yourself.

Auto Tagging should create multiple tags for semver releases

Description

Currently, auto_tag, when applied during a tag event, will simply tag the container with BUILD_TAG, but it would be nice if it would create a series of tags based on the tag provided, if it is recognized as a semantic version number.

Example: If BUILD_TAG is v2.1.24, the following tags would be created (the "v", if present, will be stripped):

• 2.1.24
• 2.1
• 2
• latest

Value

This will allow container users to "subscribe" to a particular version scope, depending on their comfort level, and receive updates without knowing exact patch numbers, for example.

Definition of Done

The auto_tag parameter should cause tagging to behave as described above.

Effort (Optional)

1 day

Add the ability to use the label flag

Description

What is your idea?

Add the ability to use the label flag in kaniko

Flag documentation:
https://github.com/GoogleContainerTools/kaniko/#--label

Value

Why is this important? Who does it impact? Will this make something better, faster, etc?

Customers using the docker CLI may be adding custom labels to their images the --label will allow us to have support for kaniko's equivalent flag.

Definition of Done

What is the end goal of this story?

The flag is useable in the plugins