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.

Sign up for GitHub

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

Jump to bottom

✨ [VC] Support Releasing Manifests & Tagging for VC code base #130

Open
christopherhein opened this issue Jun 15, 2021 · 2 comments
Open

✨ [VC] Support Releasing Manifests & Tagging for VC code base #130

christopherhein opened this issue Jun 15, 2021 · 2 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Milestone
v0.1.x

Comments

@christopherhein
Copy link
Member

User Story

As a user I would like to use blessed manifests for deploying VC for so that I can expect a stable release.

Detailed Description

Right now only CAPN is deployed/setup when make release is run, this work pairs after #129 to add full release support.

Anything else you would like to add:

Removing ClusterVersion from VC should be done prior to this work.

/kind feature
/milestone v0.1.x
@k8s-ci-robot k8s-ci-robot added this to the v0.1.x milestone Jun 15, 2021
@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Jun 15, 2021
This was referenced Jun 16, 2021
Merged
Merged
Open
@christopherhein christopherhein mentioned this issue Sep 8, 2021
Closed
@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 13, 2021
@christopherhein
Copy link
Member 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 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Milestone
v0.1.x
Development

No branches or pull requests
3 participants
@christopherhein @k8s-ci-robot @k8s-triage-robot