Skip to content
This repository has been archived by the owner on Oct 28, 2024. It is now read-only.

📖 Update docs/README.md with virtualcluster flavor #141

Open
christopherhein opened this issue Jun 17, 2021 · 6 comments
Open

📖 Update docs/README.md with virtualcluster flavor #141

christopherhein opened this issue Jun 17, 2021 · 6 comments
Assignees
Labels
kind/documentation Categorizes issue or PR as related to documentation. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Milestone

Comments

@christopherhein
Copy link
Contributor

User Story

As an operator I would like to use clusterctl to deploy a VC backed CAPN by following the quickstart so I don't need to have tribal knowledge.

Detailed Description

After #136 is merged and a release is cut we should make sure we update the readme to reflect deploying CAPN + VC as an option.

/kind documentation
/milestone v0.1.x

@k8s-ci-robot k8s-ci-robot added this to the v0.1.x milestone Jun 17, 2021
@k8s-ci-robot k8s-ci-robot added the kind/documentation Categorizes issue or PR as related to documentation. label Jun 17, 2021
@nobody4t
Copy link

/assign

@christopherhein
Copy link
Contributor Author

hey @dongwangdw we probably need to make sure we have #129 and #130 done for this to be done properly just an FYI as this might be on hold.

@nobody4t
Copy link

@christopherhein
OK. Thanks for the info. It seems there are couples of items should be achived before this one.
I will have my eye on this.

@christopherhein
Copy link
Contributor Author

Update to use released binary - curl -L https://github.com/kubernetes-sigs/cluster-api/releases/download/v0.4.0/clusterctl-linux-amd64 -o clusterctl

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 27, 2021
@christopherhein
Copy link
Contributor Author

/remove-lifecycle stale
/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Sep 27, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/documentation Categorizes issue or PR as related to documentation. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Development

No branches or pull requests

4 participants