Skip to content

Allow k8s autoscaler to be installed via local terraform client, rather than remote operator. #894

@cwiggs

Description

@cwiggs

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

Currently the k8s autoscaler is installed via a remote-exec provisioner here. This works well if you are using the bastion and operator servers, but if you aren't using those servers you aren't able to deploy the autoscaler.

It would be nice to have a variable that allows you to install the autoscaler the same way but using the same machine where Terraform is running.

New or Affected Resource(s)

A variable in the autoscaler.tf file that allows you to use a local provisioner.

Questions

  • Currently The helm resource terraform provider is required and is used for a helm template with the autoscaler. However it then looks like instead of using the helm provider to install the helm package it's just applied via kubectl via remote provisioner. Is there a reason this isn't just done via the helm provider?

Thanks

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions