Migrating EKS resources to use another lambda #33478
Unanswered
mukundjalan
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We have an infrastructure created as below and use CDK in python to manage the CDK deployments
Importer
kubectl_layer
(KubectlV29Layer
)KubectlProvider
from itkubectl_provider.service_token
as stack output:ProviderFrameworkEventLambdaArn
kubectl_provider.role_arn
as stack output:KubectlProviderRoleArn
kubectl_provider.handler_role.role_arn
as stack output:HandlerRoleArn
Deployer1
Importer
eks.KubernetesManifest
objectsDeployer2
,Deployer3
, ...,DeployerN
This setup has been working fine for us for past couple of months but we need to make certain enhancements to this so as to make it easier to accomplish this process based on the knowledge we gathered in the past year.
So, now, I want to move this setup to a better way of creating the importer stack. As I cannot use the same export value in the new stack, I created the stack as below retaining the old one until migration is complete
ImporterNew
kubectl_layer
(KubectlV29Layer
)KubectlProvider
from itkubectl_provider.service_token
as stack output:ProviderFrameworkEventLambdaArnNew
kubectl_provider.role_arn
as stack output:KubectlProviderRoleArnNew
kubectl_provider.handler_role.role_arn
as stack output:HandlerRoleArnNew
Now I want the
DeployerX
stacks to make use ofImporterNew
's output rather than the old one and later delete the stackImporter
altogether. Hence, I triedDeployerX
ImporterNew
eks.KubernetesManifest
objectsWhen synthesising I see output like
and while deployment I get error in stack deployment and deployment is rolled back
How can I achieve this migration? It is OK if the manifests are overridden as we have
overwrite=True
for all manifest objects but deletion and re-creation will not be useful as we have several resources deleting which can make our application unstable.Beta Was this translation helpful? Give feedback.
All reactions