Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changing from k8s.autoscaling.v2beta1.HorizontalPodAutoscaler to k8s.autoscaling.v2beta2.HorizontalPodAutoscaler fails the first time every time #1047

Open
nesl247 opened this issue Mar 25, 2020 · 1 comment
Labels
kind/bug Some behavior is incorrect or out of spec

Comments

@nesl247
Copy link

nesl247 commented Mar 25, 2020

Problem description

We have many projects using k8s.autoscaling.v2beta1.HorizontalPodAutoscaler. When we updated them to use k8s.autoscaling.v2beta2.HorizontalPodAutoscaler, pulumi did not do a replace. Instead, it does an apiVersion update.

Unfortunately, the first time it tries to do this fails every time.

Errors & Logs

Updating (LinioIT/development):
     Type                                               Name                               Status                  Info
     pulumi:pulumi:Stack                                sellercenter-vtex-api-development  **failed**              1 error
 ~   └─ kubernetes:autoscaling:HorizontalPodAutoscaler  sellercenter-vtex-api              **updating failed**     [diff: ~apiVersion,spec]; 1 error

Diagnostics:
  kubernetes:autoscaling:HorizontalPodAutoscaler (sellercenter-vtex-api):
    error: 1 error occurred:
    	* the Kubernetes API server reported that "sellercenter-vtex-api-bv9xt1oy/sellercenter-vtex-api-pwvwhxsb" failed to fully initialize or become live: HorizontalPodAutoscaler.autoscaling "sellercenter-vtex-api-pwvwhxsb" is invalid: [spec.metrics[0].external.metric.name: Required value: must specify a metric name, spec.metrics[0].external.target.averageValue: Required value: must set either a target value for metric or a per-pod target]

  pulumi:pulumi:Stack (sellercenter-vtex-api-development):
    error: update failed
@lblackstone
Copy link
Member

This could be a result of #991

Need more investigation to see if these apiVersions are incompatible and should not be aliased.

@lblackstone lblackstone removed their assignment Jul 13, 2023
@lblackstone lblackstone added the kind/bug Some behavior is incorrect or out of spec label Jul 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Some behavior is incorrect or out of spec
Projects
None yet
Development

No branches or pull requests

2 participants