We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I'm creating a cdk8s Chart in an aws-cdk project, using the following dependencies versions:
"aws-cdk-lib": "^2.0.0", "cdk8s": "^2.0.0", "constructs": "^10.0.0",
Using an aws-cdk Construct as the parent scope for the Chart, I'm getting: 'Error: cannot find a parent chart (directly or indirectly)'
import { Construct } from 'constructs'; import { App as AwsApp, Stack } from 'aws-cdk-lib'; import { Cluster, KubernetesVersion } from 'aws-cdk-lib/aws-eks'; import { App as K8sApp, Chart } from 'cdk8s'; class MyStack extends Stack { constructor(scope: Construct, id: string) { super(scope, id); const cluster = new Cluster(this, 'Cluster', { version: KubernetesVersion.V1_21 }); cluster.addCdk8sChart('Test1', new Chart(this, 'Test1')); // <--- NOT WORKS cluster.addCdk8sChart('Test2', new Chart(new K8sApp(), 'Test2')); // <--- WORKS } } new MyStack(new AwsApp(), 'MyStack');
Which is the intent of Ecosystem Interoperability if the parent scope of a cdk8s Construct can't be an aws-cdk Construct?
The text was updated successfully, but these errors were encountered:
@Hazzard17h Yeah, currently passing in an AWS CDK construct as the scope will not work.
I agree this is a bit confusing with regards to interop. There are many levels to that interop support.
We unfortunately still haven't reached level 3.
Sorry, something went wrong.
No branches or pull requests
I'm creating a cdk8s Chart in an aws-cdk project, using the following dependencies versions:
Using an aws-cdk Construct as the parent scope for the Chart, I'm getting: 'Error: cannot find a parent chart (directly or indirectly)'
Which is the intent of Ecosystem Interoperability if the parent scope of a cdk8s Construct can't be an aws-cdk Construct?
The text was updated successfully, but these errors were encountered: