kubernetes-sigs/cluster-api-provider-gcp

Feature request: list default available failure domains for CAPG cluster

faiq opened this issue · 8 comments

faiq commented

/kind feature

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

As a cluster administrator, I'd like a list of available failure domains for the GCP Cluster I have created and for that to be reflected in the cluster status.

Other Cluster API provider such as CAPA and CAPZ provide this functionality see:

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

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

faiq commented

/remove-lifecycle stale

/assign

/assign

@faiq this feature has already been implemented
check :

func (s *ClusterScope) FailureDomains() clusterv1.FailureDomains {

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

Since this feature has already been implemented, closing this. Feel free to reopen if there's any additional context to be added.

/close

@SubhasmitaSw: Closing this issue.

In response to this:

Since this feature has already been implemented, closing this. Feel free to reopen if there's any additional context to be added.

/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.