This message was deleted.

Before:

new kubernetes.apiextensions.CustomResource("test", {
  apiVersion: "<http://cloud.google.com/v1beta1|cloud.google.com/v1beta1>",
  kind: "BackendConfig",
  metadata: {
    name: "backendconfig",
    namespace: "test-namespace",
  },
  spec: {
    timeoutSec: 300,
  },
}, {})

After (changing v1beta1 to v1 with alias option):

new kubernetes.apiextensions.CustomResource("test", {
  apiVersion: "<http://cloud.google.com/v1|cloud.google.com/v1>",
  kind: "BackendConfig",
  metadata: {
    name: "backendconfig",
    namespace: "test-namespace",
  },
  spec: {
    timeoutSec: 300,
  },
}, {
  aliases: [{ type: "kubernetes:<http://cloud.google.com/v1beta1:BackendConfig|cloud.google.com/v1beta1:BackendConfig>" }],
})

and I got

* the Kubernetes API server reported that "test-namespace/backendconfig" failed to fully initialize or become live: <http://BackendConfig.cloud.google.com|BackendConfig.cloud.google.com> "backendconfig" is invalid: apiVersion: Invalid value: "<http://cloud.google.com/v1|cloud.google.com/v1>": must be <http://cloud.google.com/v1beta1|cloud.google.com/v1beta1>

Does changing the apiVersion field directly work?

Thanks for the response. Yes. Changing apiVersion field with

kubectl

instead of Pulumi works.

Sorry, I meant changing the apiVersion here:

new kubernetes.apiextensions.CustomResource("test", {
  apiVersion: "<http://cloud.google.com/v1|cloud.google.com/v1>",

@bored-table-20691 You meant without

aliases

option?

That would be my expectation - I don’t think changing resource version is a change you can do “in place” really, though I could be wrong.

I want to bump apiVersion in-place. Kubernetes API supports this, as I succeeded with

kubectl

. Also, Pulumi Kubernetes supports this for some built-in resources. https://github.com/pulumi/pulumi-kubernetes/pull/798

I see - thanks for clarifying. Unfortunately, I don’t have anything useful to add 🙂

This would be good to know as k8s 1.22 will require lots of these changes iirc

I am wondering why Pulumi Kubernetes calls

v1beta1

API instead of

v1

API even I specify

v1

manifest. Looks apiextentions.CustomResource honors previous API version in the state.