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
[aws-eks] document how to define dependencies between k8s resources #4291
Comments
Can be fixed by adding cloudformation dependecies - https://docs.aws.amazon.com/cdk/api/latest/python/aws_cdk.core.README.html#dependencies to be closed |
Yes, dependencies can be used to specify order between resources. We should add some example in the EKS module's README that demonstrates this. |
Can anyone please help me, I have been trying this thing for 5 days. I have a custom resource in AWS YAML format, which I want to create in AWS CDK. I am able to add condition and ServiceToken using AWS CDK CfnCustomResource but I can't add properties. Please help me to find out the solution. YAML Template
Corresponding AWS CDK typescript code which is working.
I want to add properties of YAML template, how could I do it. Please help me........ |
@lkoniecz @eladb What if there's dependencies in the manifest yaml itself? As you already know, k8s itself recommend to have all the related objects in a yaml. So there's some case one manifest contains several objects with dependencies. For instance, cloudwatch agent's quickstart has namespace deployment as the very first step for its manifest. I wonder what you guys think of dealing with this. |
@yjw113080 I found no other way than splitting the yaml into dependend pieces, in my case, namaspace into one file and all namespaced objects into the other. |
@eladb can you provide an example of how to do this? I am trying to create a dependency between namespace and helm chart. |
@FarshadNiayesh I ran into a similar situation and provided an example on how to create a dependency between two helm charts. But it would also work to provide a dependency between the namespace & chart: #7592 (comment) |
Kubernetes resources are not deployed in the order they were added via add_resource method. If one of them is a namespace, for instance, others fail with a namespace not found error.
Reproduction Steps
Error Log
Environment
Other
This is 🐛 Bug Report
The text was updated successfully, but these errors were encountered: