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

Add ability to taint a worker pool #2862

Closed
vburckhardt opened this issue Jul 13, 2021 · 3 comments · Fixed by #2803
Closed

Add ability to taint a worker pool #2862

vburckhardt opened this issue Jul 13, 2021 · 3 comments · Fixed by #2803
Labels
enhancement service/Kubernetes Service Issues related to Kubernetes Service Issues

Comments

@vburckhardt
Copy link

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 other comments that do not add relevant new information or questions, 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

The ability to taint a worker pool is missing in the terraform provider.

Corresponding IBM Cloud CLI command is
ibmcloud ks worker-pool taint set

New or Affected Resource(s)

  • ibm_container_vpc_worker_pool
  • ibm_container_worker_pool

Potential Terraform Configuration

# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file. For
# security, you can also encrypt the files using our GPG public key.

References

  • #0000
@kavya498 kavya498 added the service/Kubernetes Service Issues related to Kubernetes Service Issues label Jul 14, 2021
@kavya498
Copy link
Collaborator

#2696 #1646 #624

@kavya498 kavya498 linked a pull request Jul 14, 2021 that will close this issue
@PKehnel
Copy link

PKehnel commented Jul 27, 2021

The tainteffects naming includes the and by mistake.
Should be removed.

"NoSchedule, PreferNoSchedule, and NoExecute"

@kavya498
Copy link
Collaborator

It is fixed..
It ll be available in upcoming release..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement service/Kubernetes Service Issues related to Kubernetes Service Issues
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants