Add target to deploy a namespace-scoped operator.

[fjammes]

Add a Makefile target (i.e. make ns-deploy) and related kustomize configuration files to deploy a namespace-scoped operator. This target would automate the feature documented here: https://sdk.operatorframework.io/docs/building-operators/golang/operator-scope/#changing-the-permissions-to-namespaced.

I have implemented a prototype for it and I can open a PR if needed.

It does not require a particular kubernetes version.

/kind feature

[camilamacedo86]

We think that it is a common need so please feel free to push a PR with your idea to solve that. However, we are not sure if it would be better addressed via a makefile target. Let's check your proposal and go forward from there. WDYT?

[Adirio]

Small note: the most that can be solved with kustomize patches the better.

[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

[fjammes]

/remove-lifecycle stale

[fjammes]

Hi @camilamacedo86, here is my proposal "#2254"
The current idea is to run command below in the operator repository:

# generate <OPERATOR_REPO_DIR>/manifests/operator-ns-scoped.yaml
make yaml-ns-scoped
# And then set namespace and deploy manually
sed 's/<NAMESPACE>/my-namespace' manifests/operator-ns-scoped.yaml | kubectl apply -f -

I agree this is not perfect but this first step works fine on my side.

[camilamacedo86]

Hi @fjammes,

The idea is nice. But the implementation does not seem accurate. Please, check my comment #2254 (review)

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[camilamacedo86]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

• Confirm that this issue is still relevant with /triage accepted (org members only)
• Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

[TAM360]

/assign