You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
This commit adds the ability to deploy the k8s cluster autoscaler using
local-exec rather than remote-exec. Using local-exec is helpful when
you don't use the operator/bastion features of this module. Now if you
set cluster_autoscaler_remote_exec variable to false terraform will run
a `kubectl apply` command on the same machine where you are running
Terraform.
More info in this issue: oracle-terraform-modules#894
Signed-off-by: Chris Wiggins([email protected])
Community Note
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
Thanks
The text was updated successfully, but these errors were encountered: