This message was deleted.
# awss
sparse-intern-71089
09/25/2023, 11:32 PMThis message was deleted.
v
victorious-church-57397
09/25/2023, 11:35 PMTbh you probably don’t want your cluster / Kubectl auto updating. I’d have that in a config file somewhere and then you can be in control of you’re updgrades when they come. Hopefully this solves your issue
q
quaint-book-39362
09/25/2023, 11:36 PMthe cluster version won't change
quaint-book-39362
09/25/2023, 11:36 PMfrom the pulumi program
quaint-book-39362
09/25/2023, 11:36 PMit will be done via aws console at some point
quaint-book-39362
09/25/2023, 11:37 PMi need this helm chart to be aware of the version and update accordingly whenever run
v
victorious-church-57397
09/25/2023, 11:38 PMWhy don’t you just hard code the kubectl version? Surely that wil differ between your local dev and CI runners etc
victorious-church-57397
09/25/2023, 11:38 PMWould be easier for you to be in control and keep it consistent
victorious-church-57397
09/25/2023, 11:39 PMWhat’s the problem you’re trying to solve and what’s been the biggest issue so far?
b
billowy-army-68599
09/25/2023, 11:43 PM
The cluster version is an output property on the cluster object, just pass it that. It doesn’t need to be the kubectl version
👍 2
q
quaint-book-39362
09/25/2023, 11:47 PMi guess you mean
eksCluster*.*versioneks.Clusterquaint-book-39362
09/25/2023, 11:49 PMthat can work. this is not the first time i've needed something like this, though. for example, i recently wanted to configure a k8s deployment where the image for it should be either a new one defined on an environment variable, else just use the current deployment's one. so i used kubectl for that inside the pulumi program, but this meant grabbing the kubeconfig json, saving that, running a shell command to obtain the current image within the program, etc.
quaint-book-39362
09/25/2023, 11:49 PMi suppose i was wondering if there was a pattern for this sort of thing
v
victorious-church-57397
09/25/2023, 11:52 PMSounds like you’re doing stuff that’s not best practise to determine this stuff, the way we handle versions is having them controlled in outputs from a config stack or having them hard coded and then gradually rolling out change by bumping them and release it to test clusters etc
victorious-church-57397
09/25/2023, 11:53 PMIf aws decide to update the eks cluster and there’s not a matching version for downstream applications that’s going to cause issues
q
quaint-book-39362
09/26/2023, 12:03 AMyeah, perhaps you're right. not sure about setting the image id in the stack config, since the pulumi program might be running in a CI env, but also in local environments during the development of the program. it would mean i'd need to keep the config file updated locally, no? or how would you handle that situation?
v
victorious-church-57397
09/26/2023, 12:29 AMYeah exactly, you either need to keep it configured locally in files or it could introduce inconsistencies in CI
q
quaint-book-39362
09/27/2023, 3:09 PMi ended up refactoring stuff to do what you recommended and keep the version tracked in the stack config. it really simplified doing things. thanks!