Skip to content
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

Migrate docs to cdk8s v2 #872

Closed
4 tasks
iliapolo opened this issue Mar 7, 2022 · 0 comments · Fixed by #923
Closed
4 tasks

Migrate docs to cdk8s v2 #872

iliapolo opened this issue Mar 7, 2022 · 0 comments · Fixed by #923
Assignees
Labels
documentation Improvements or additions to documentation effort/medium 1 week tops priority/p1 Should be on near term plans

Comments

@iliapolo
Copy link
Member

iliapolo commented Mar 7, 2022

We should start externalizing v2 of cdk8s-core since it our path forward for interoping with other CDK's out there (e.g the aws-cdk v2).

What to do

@iliapolo iliapolo changed the title Migrate to cdk8s-core v2 where needed Migrate to cdk8s-core v2 Mar 7, 2022
@iliapolo iliapolo added documentation Improvements or additions to documentation effort/medium 1 week tops priority/p1 Should be on near term plans labels Mar 8, 2022
@iliapolo iliapolo added this to To do in Release Candidate | cdk8s-plus via automation Mar 8, 2022
@iliapolo iliapolo changed the title Migrate to cdk8s-core v2 Migrate docs to cdk8s-core v2 Mar 8, 2022
@iliapolo iliapolo changed the title Migrate docs to cdk8s-core v2 Migrate docs to cdk8s v2 Mar 8, 2022
@iliapolo iliapolo moved this from To do to In progress in Release Candidate | cdk8s-plus May 21, 2022
@mergify mergify bot closed this as completed in #923 May 24, 2022
Release Candidate | cdk8s-plus automation moved this from In progress to Done May 24, 2022
mergify bot pushed a commit that referenced this issue May 24, 2022
@iliapolo iliapolo self-assigned this Jan 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation effort/medium 1 week tops priority/p1 Should be on near term plans
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

1 participant