Hi, thanks for reporting.
Chances are that it’s not supported, I will look at it asap.

Feature flags are supported at the provider config level though.
Not sure how the file itself should be passed.

I haven't looked at the file mechanic in detail, but in kubernetes/kops@9bb1d3e, judging from the multi-resource yaml pkg/model/components/kubescheduler/tests/kubeschedulerconfig/cluster.yaml, it would look to me like a user-specified yaml can be applied after (?) the cluster creation 🤔

@ddelange did you try to enable the feature flag in the provider config ?

provider "kops" {
  feature_flags = [ "ClusterAddons" ]
}

It won't be enough though, I need to add addons support.

oh nice, no haven't had the time yet!

@ddelange do you think you could give a try to #893 ?

that looks great! :) I don't know when I can make time to run a real world test, but I will try to get around to it! Feel free to merge without my confirmation though ;)

I will merge once you can confirm it works ;)
I actually don't have access to an aws account to give it a try myself.

ok, I'll get back to you!

Hi guys,

what's the status of this issue?

@BartoszZawadzki check https://github.com/terraform-kops/terraform-provider-kops

@eddycharly So basically I have to use kops terraform provider in order to be able to use KubeSchedulerConfiguration ? There's no way to use it with our current kops yaml manifest?

@BartoszZawadzki TBH i'm not sure, i didn't work on it for some time. The project moved to https://github.com/terraform-kops/terraform-provider-kops. This repo is no longer active.

does it make sense to add a forwarding banner on top of README and archive the repo?

@ddelange yes, i will probably do that

@eddycharly Thanks!