Enable webhooks and cert-manager for CAPI operator

[wfernandes]

User Story

As a develper, I would like to enable webhooks and cert-manager for the CAPI operator so that I can add validation and defaulting rules for the CAPI provider objects.

Detailed Description

When I run

make release-manifests 
kubectl apply -f cmd/clusterctl/config/assets/cert-manager.yaml
kubectl apply -f out/operator-components.yaml

I want to see validation and mutating webhooks and associated services and certs created for the CAPI operator.

Anything else you would like to add:

This is still part of the initial scaffolding of the CAPI operator.

/kind feature
/area api
/area operator

[k8s-ci-robot]

@wfernandes: The label(s) area/operator cannot be applied, because the repository doesn't have them

In response to this:

User Story

As a develper, I would like to enable webhooks and cert-manager for the CAPI operator so that I can add validation and defaulting rules for the CAPI provider objects.

Detailed Description

When I run

make release-manifests 
kubectl apply -f cmd/clusterctl/config/assets/cert-manager.yaml
kubectl apply -f out/operator-components.yaml

I want to see validation and mutating webhooks and associated services and certs created for the CAPI operator.

Anything else you would like to add:

This is still part of the initial scaffolding of the CAPI operator.

/kind feature
/area api
/area operator

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.

[vincepri]

/area operator

[k8s-ci-robot]

@vincepri: The label(s) area/operator cannot be applied, because the repository doesn't have them

In response to this:

/area operator

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.

[wfernandes]

/assign
/lifecycle active

[fabriziopandini]

/remove-area api
/area operator
/milestone v0.4.0

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten

[k8s-triage-robot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/close

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.