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

Pulumi LKE improvements - Basic use cases #593

Open
janakg opened this issue May 8, 2024 · 1 comment
Open

Pulumi LKE improvements - Basic use cases #593

janakg opened this issue May 8, 2024 · 1 comment
Labels
awaiting-upstream The issue cannot be resolved without action in another repository (may be owned by Pulumi). kind/enhancement Improvements or new features

Comments

@janakg
Copy link

janakg commented May 8, 2024

Hello Team!

Thanks for maintaining an active Github repo for pulumi and linode.
We have started using LKE for deploying some of our compute workloads. It would be great if these features are prioritized as they are basic to Kube clusters

  1. A way to label the nodes created via LKE. e.g.:: prefix can be given as es-lke-node-
  2. A way to add tags to nodes created via LKE. As there is no other way to differentiate in the Linodes listing. Today we are seeing 100's of nodes without label and tag and it is impossible to make sense out of it in Linodes listing page in console.
  3. A way to label the ingress (NodeBalancer) and volumes created during deployment. Or post creation changing the config based on the ids is also fine. I could see one for NodeBalancerConfig, can i use it to update the label alone.
  4. There is no way to delete the default pool of a cluster, as we always want to use the NodePool for more control. removeDefaultPool can be an option in cluster creation

Most importantly [1] & [2] - has to work during autoscaling as well.

Please let me know if these are feasible or happy to learn the limitations.

Thanks

@janakg janakg added kind/enhancement Improvements or new features needs-triage Needs attention from the triage team labels May 8, 2024
@VenelinMartinov
Copy link

Hey @janakg, thanks for the suggestions! Unfortunately this is probably not the right place for them.

The pulumi linode provider is a wrapper around the terraform linode provider: https://github.com/linode/terraform-provider-linode maintained by linode themselves. We try to faithfully expose all of the functionality there for pulumi users.

You should raise the suggestions as feature requests on the upstream provider - they have the expertise to implement these.

As soon as they are available in the tf provider, we try to bring them over, usually within less then a week.

Thank you!

@VenelinMartinov VenelinMartinov removed the needs-triage Needs attention from the triage team label May 10, 2024
@mikhailshilkov mikhailshilkov added the awaiting-upstream The issue cannot be resolved without action in another repository (may be owned by Pulumi). label May 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting-upstream The issue cannot be resolved without action in another repository (may be owned by Pulumi). kind/enhancement Improvements or new features
Projects
None yet
Development

No branches or pull requests

3 participants