✨ : Generate Dockerfile from declarative plugin

[viveksyngh]

We need to copy the channels directory in the Dockerfile, particularly
now that we're running with non-root permissions and it is no longer a
one-liner.

Signed-off-by: Vivek Singh svivekkumar@vmware.com

[k8s-ci-robot]

Hi @viveksyngh. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[camilamacedo86]

Thank you for your contribution 🥇

A few questions were added could you please check?

Also, note that we need to run make generate to generate the samples in the testata dir with the changes performed for each PR.

[camilamacedo86]

/ok-to-test

[camilamacedo86]

Hi @viveksyngh that is great.
It shows for me that we have just a nit https://github.com/kubernetes-sigs/kubebuilder/pull/2507/files#r811398584. Otherwise it shows great for me.

Let's try to ping @justinsb as well.

[camilamacedo86]

I can see that the methods complained in the API diff are present in

kubebuilder/pkg/plugins/golang/declarative/v1/api.go

Lines 73 to 77 in af24fad

	func (p *createAPISubcommand) InjectConfig(c config.Config) error {
	p.config = c
	return nil
	}

So

/lgtm
/approved

[camilamacedo86]

/approved

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: camilamacedo86, viveksyngh

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [camilamacedo86]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[camilamacedo86]

Forcing this one since it. shows an issue in the API check: #2507 (comment)