We have a manifest file that defines a set number of replicas and an autoscaler that scales them up. The problem we have is when we apply the manifest, it immediately scales the replicas down to the number in the manifest. This eventually is fixed by the autoscaler, but in the meantime, it's not great!

Is there a way to run a manifest and ignore the replica parameter?

We tried removing it, but then it scaled to the default count of 1.

  • This problem feels disastrous in a system that has many more replicas than the manifest calls for. I'm very surprised there isn't a better answer to this.
    – mlissner
    Jun 6, 2022 at 16:57

1 Answer 1


The application boot up might be using resources above your set utilisation target before settling down. What you can do is to either:

  • give it a bit more resource request
  • increase the threshold of the HPA utilisation target
  • increase the autoscaler interval check

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.