Unable to still using Component Config besides it be deprecated only

[camilamacedo86]

We are facing a hard time to bump Controller-Runtime 0.15.0 due the breaking changes.
We noticed that the ComponentConfig was deprecated. #895

However, it seems that it also has a bug. This means when ctrl.File is called in cmd/main.go it calls in here which registers the ComponentConfig with the scheme. Though the field has been deprecated, the ComponentConfig type should still be registered with controller-runtime.sigs.k8s.io/v1alpha1 scheme, which seems missing.

[alvaroaleman]

Sorry, I don't understand the bug. Could you provide a sample snippet of what you are trying to do?

[troy0820]

/kind support

Is this issue fixed with the above pull request to guacamole-operator? @camilamacedo86

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten

[camilamacedo86]

Hi @alvaroaleman,

The ComponentConfig was deprecated; therefore, it should still work fine until being removed and no longer supported.
However, that is not the case.

This means when ctrl.File is called in cmd/main.go it calls in here which registers the ComponentConfig with the scheme. Though the field has been deprecated, the ComponentConfig type should still be registered with controller-runtime.sigs.k8s.io/v1alpha1 scheme, which seems missing.

Anyway, I think that can be closed. It was not well adopted because we did not face complaints from Kubebuilder users, and we have already been communicating that soon we will do a MAJOR release where this option will be removed from there.

Therefore, I am closing this one