cluster-api-provider-ibmcloud icon indicating copy to clipboard operation
cluster-api-provider-ibmcloud copied to clipboard

Add kubebuilder tags to disallow users from changing spec field values once set.

Open Karthik-K-N opened this issue 1 year ago • 5 comments

/kind feature /area provider/ibmcloud

Describe the solution you'd like [A clear and concise description of what you want to happen.]

Currently in a PowerVS cluster once the values for zone or vpc.region or resource group name is set, its expected not to change over the lifetime of cluster but there is no strict enforcement for it.

Example of setting immutability can be seen here

Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.]

Karthik-K-N avatar May 09 '24 04:05 Karthik-K-N

/assign @Shilpa-Gokul

Shilpa-Gokul avatar May 14 '24 05:05 Shilpa-Gokul

As discussed lets hold this for a while and will consider for next release.

Karthik-K-N avatar May 14 '24 06:05 Karthik-K-N

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 avatar Aug 15 '24 05:08 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

k8s-triage-robot avatar Sep 14 '24 05:09 k8s-triage-robot

/remove-lifecycle rotten

Amulyam24 avatar Sep 17 '24 06:09 Amulyam24