Invalid details from https://pkg.go.dev/k8s.io/kops/pkg/apis/kops#AWSSpec

[s3than]

When attempting to update a cluster with the API details from here

https://pkg.go.dev/k8s.io/kops/pkg/apis/kops#AWSSpec

The following error is returned when attempting to replace

no kind "Cluster" is registered for version "kops.k8s.io/v1alpha3" 

Or if switching to kops.k8s.io/v1alpha2

json: cannot unmarshal object into Go struct field ClusterSpec.spec.cloudProvider of type string

Is there a method of using the updated Spec as yet?

[johngmyers]

The v1alpha3 apiversion is not released yet.

[johngmyers]

And the pkg.go.dev link you gave is for the internal API, which is different than v1alpha2. You want https://pkg.go.dev/k8s.io/kops/pkg/apis/kops/v1alpha2#AWSSpec

[s3than]

Clicking on the link in this doc page

https://kops.sigs.k8s.io/cluster_spec/

Goes straight to https://pkg.go.dev/k8s.io/kops/pkg/apis/kops#ClusterSpec

From there clicking CloudProvider -> AWSSpec gives the details above..

If appropriate I'm happy to provide a PR to change that link to https://pkg.go.dev/k8s.io/kops/pkg/apis/kops/v1alpha2#ClusterSpec

So that clarifies the docs side.

@johngmyers Thanks for the update

[johngmyers]

One possible reference would be https://github.com/kubernetes/kops/tree/master/k8s/crds

I don't know if that's published anywhere that makes it pretty. The pkg.go.dev link does have that same information, but it also has a bunch of noise.

[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

[k8s-triage-robot]

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

This bot triages 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:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

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

This bot triages 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:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned

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.