Skip to content

/ kubernetes

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

Jump to bottom

Take kubectl apply out of Alpha and into Beta #34274

Closed
mikedanese opened this issue Oct 6, 2016 · 15 comments
Closed

Take kubectl apply out of Alpha and into Beta #34274

mikedanese opened this issue Oct 6, 2016 · 15 comments
Labels
area/app-lifecycle area/declarative-configuration area/kubectl lifecycle/rotten priority/important-soon sig/cli
Projects
UX - Kubectl Continued Development an...

Comments

@mikedanese
Copy link
Member

@mikedanese mikedanese commented Oct 6, 2016 •
edited

  • Fully document behavior
  • Prune all restmappings, not just those provided

cc @pwittrock
@MrHohn MrHohn mentioned this issue Oct 12, 2016
Merged
@MrHohn
Copy link
Member

@MrHohn MrHohn commented Oct 19, 2016 •
edited

Sorry to bother, I want to know what is the plan for "Prune all restmappings"? I think addon-manager will need this feature (at least need to also prune given additional restmappings?).
@mikedanese
Copy link
Member Author

@mikedanese mikedanese commented Oct 19, 2016

I have not started working on it. I can take a look or you can if you want.
@mikedanese mikedanese self-assigned this Oct 19, 2016
@MrHohn
Copy link
Member

@MrHohn MrHohn commented Oct 19, 2016

Sure, I can take a look at this if it is not complicated.

I wanna follow the plan you proposed before: add a --type flag to modified the visitedRESTMappings
@MrHohn MrHohn mentioned this issue Oct 20, 2016
Merged
k8s-github-robot pushed a commit that referenced this issue Nov 4, 2016
Kubernetes Submit Queue
Merge pull request #35220 from MrHohn/kubectl-apply-type
e4edd81 
Automatic merge from submit-queue

Implement --prune-whitelist(-w) flag to overwrite default whitelist for --prune

From #34274.

Updates:

As suggested, the new commits implement a default whitelist for `kubectl apply --prune`, which could be overwritten by using `--prune-whitelist`or `-w` flag. The default whitelist and example as below.

Also supports `--dry-run` for `--prune` to fix #35222.

whitelist:

```
type pruneResource struct {
    group      string
    version    string
    kind       string
    namespaced bool
}

*pruneResources = []pruneResource{
    {"", "v1", "ConfigMap", true},
    {"", "v1", "Endpoints", true},
    {"", "v1", "Namespace", false},
    {"", "v1", "PersistentVolumeClaim", true},
    {"", "v1", "PersistentVolume", false},
    {"", "v1", "Pod", true},
    {"", "v1", "ReplicationController", true},
    {"", "v1", "Secret", true},
    {"", "v1", "Service", true},
    {"batch", "v1", "Job", true},
    {"extensions", "v1beta1", "DaemonSet", true},
    {"extensions", "v1beta1", "Deployment", true},
    {"extensions", "v1beta1", "HorizontalPodAutoscaler", true},
    {"extensions", "v1beta1", "Ingress", true},
    {"extensions", "v1beta1", "ReplicaSet", true},
    {"apps", "v1beta1", "StatefulSet", true},
}
```

example:

```
$ kubectl apply -f /path/to/file --prune -l test=true \
      -w core/v1/Pod \
      -w core/v1/Service \
      -w extensions/v1beta1/Deployment 
```

@mikedanese
@bgrant0607
Copy link
Member

@bgrant0607 bgrant0607 commented Nov 17, 2016

cc @ymqytw @pwittrock
@pwittrock
Copy link
Member

@pwittrock pwittrock commented Nov 17, 2016

@MrHohn Can we close this issue?
@MrHohn
Copy link
Member

@MrHohn MrHohn commented Nov 17, 2016

@pwittrock Sure. --prune is not well documented yet, but I think #35234 is also tracking this.
@pwittrock pwittrock mentioned this issue Nov 17, 2016
Open
15 of 32 tasks complete
@MrHohn
Copy link
Member

@MrHohn MrHohn commented Nov 23, 2016

Actually I think we might want to keep this issue open. There is an Alpha Disclaimer comment in the code, which has a pointer to this issue.
Plus this --prune feature indeed needs to be refined, see comments here and here.

Could we update the contents on top and keep it open?

@pwittrock @mikedanese
@pwittrock pwittrock changed the title Polish outstanding issues with kubeclt apply --prune Take kubectl apply out of Alpha and into Beta Nov 23, 2016
@pwittrock
Copy link
Member

@pwittrock pwittrock commented Nov 23, 2016

SGTM
@xiangpengzhao
Copy link
Member

@xiangpengzhao xiangpengzhao commented Jun 24, 2017

/sig cli
@fejta-bot
Copy link

@fejta-bot fejta-bot commented Jan 6, 2018

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale
@bgrant0607
Copy link
Member

@bgrant0607 bgrant0607 commented Jan 23, 2018

/remove-lifecycle stale
@fejta-bot
Copy link

@fejta-bot fejta-bot commented Apr 23, 2018

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
@fejta-bot
Copy link

@fejta-bot fejta-bot commented May 23, 2018

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale
@fejta-bot
Copy link

@fejta-bot fejta-bot commented Jun 22, 2018

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
@akavel
Copy link

@akavel akavel commented Nov 12, 2019 •
edited

Guys, so this is now both "priority/important-soon", and "lifecycle/rotten"; can you make a grown-up decision on it and remove one of those labels? doesn't make much sense to see them both applied. The docs still contain the section warning that this is alpha functionality, and code in master branch still links to this issue! I guess maybe you want to also clean up the situation between this issue and #35234?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/app-lifecycle area/declarative-configuration area/kubectl lifecycle/rotten priority/important-soon sig/cli
Projects
UX - Kubectl Continued Development an...
Debt
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
9 participants
@akavel @mikedanese @bgrant0607 @pwittrock @MrHohn @k8s-github-robot @xiangpengzhao @k8s-ci-robot @fejta-bot