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

chore: make usage of vcluster convert config more clear #1980

Merged

Conversation

johannesfrey
Copy link
Contributor

What issue type does this pull request address? (keep at least one, remove the others)

/kind enhancement

What does this pull request do? Which issues does it resolve? (use resolves #<issue_number> if possible)
resolves ENG-4188

Please provide a short message that should be published in the vcluster release notes
Made the usage of vcluster convert config more clear

What else do we need to know?
Backport to v20?!

Copy link

netlify bot commented Jul 24, 2024

Deploy Preview for vcluster-docs canceled.

Built without sensitive environment variables

Name Link
🔨 Latest commit 7616745
🔍 Latest deploy log https://app.netlify.com/sites/vcluster-docs/deploys/66a278bccc00fe00080371b4

@johannesfrey johannesfrey force-pushed the vclusterctl-convert-long-message branch from 399a1fe to 7616745 Compare July 25, 2024 16:09
@FabianKramm FabianKramm merged commit 622849e into loft-sh:main Jul 26, 2024
60 checks passed
@heiko-braun heiko-braun added the backport-to-v0.20 backport this PR to v0.20 branch label Jul 30, 2024
@loft-bot
Copy link

💚 All backports created successfully

Status Branch Result
v0.20

Questions ?

Please refer to the Backport tool documentation and see the Github Action logs for details

heiko-braun added a commit that referenced this pull request Jul 30, 2024
[v0.20] Merge pull request #1980 from johannesfrey/vclusterctl-convert-long-message
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-to-v0.20 backport this PR to v0.20 branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants