Skip to content
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.

Cluster sets NodeVersion even if removeDefaultNodePool is true #68

Open
sthomson-wyn opened this issue Jul 29, 2022 · 1 comment
Open
Labels
bug Something isn't working

Comments

@sthomson-wyn
Copy link

What happened?

If you create a cluster with "removeDefaultNodePool" crossplane will automatically set the NodeVersion field

This results in an error when I attempt to delete (and I assume this would happen for any change):

node_version can only be specified if remove_default_node_pool is not true

How can we reproduce it?

  1. Create a cluster with removeDefaultNodePool: true
  2. Try to delete it

What environment did it happen in?

Crossplane version: 1.81
Provider version: v0.2.0-preview

@sthomson-wyn sthomson-wyn added the bug Something isn't working label Jul 29, 2022
@sthomson-wyn
Copy link
Author

Note that this also prevents reconciliation, which is pretty bad

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant