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

Take kubectl apply out of Alpha and into Beta #34274

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

Comments

Assignees
No one assigned
Labels
area/app-lifecycle area/declarative-configuration area/kubectl lifecycle/rotten priority/important-soon sig/cli
Projects
Debt in UX - Kubectl Continued Development and Support
Milestone
No milestone
8 participants
@mikedanese @MrHohn @bgrant0607 @pwittrock @xiangpengzhao @fejta-bot @k8s-github-robot @k8s-ci-robot
@mikedanese
Copy link
Member

commented Oct 6, 2016 •
edited

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

cc @pwittrock

@k8s-github-robot k8s-github-robot added area/controller-manager team/ux labels Oct 6, 2016

@MrHohn MrHohn referenced this issue Oct 12, 2016

Merged

Upgrade addon-manager with kubectl apply #34513

@pwittrock pwittrock added the priority/backlog label Oct 13, 2016

@MrHohn

This comment has been minimized.

Sign in to view
Copy link
Member

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 mikedanese added priority/important-soon and removed priority/backlog labels Oct 19, 2016

@mikedanese

This comment has been minimized.

Sign in to view
Copy link
Member Author

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

This comment has been minimized.

Sign in to view
Copy link
Member

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 referenced this issue Oct 20, 2016

Merged

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

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 
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
e4edd81

@bgrant0607 bgrant0607 added area/app-lifecycle area/kubectl and removed area/controller-manager labels Nov 17, 2016

@bgrant0607

This comment has been minimized.

Sign in to view
Copy link
Member

commented Nov 17, 2016

cc @ymqytw @pwittrock
@pwittrock

This comment has been minimized.

Sign in to view
Copy link
Member

commented Nov 17, 2016

@MrHohn Can we close this issue?
@MrHohn

This comment has been minimized.

Sign in to view
Copy link
Member

commented Nov 17, 2016

@pwittrock Sure. --prune is not well documented yet, but I think #35234 is also tracking this.

@pwittrock pwittrock referenced this issue Nov 17, 2016

Open

kubectl apply umbrella issue tracker #35234

15 of 32 tasks complete
@MrHohn

This comment has been minimized.

Sign in to view
Copy link
Member

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

This comment has been minimized.

Sign in to view
Copy link
Member

commented Nov 23, 2016

SGTM

@bgrant0607 bgrant0607 added the area/declarative-configuration label Dec 8, 2016

@k8s-github-robot k8s-github-robot added the needs-sig label May 31, 2017

@xiangpengzhao

This comment has been minimized.

Sign in to view
Copy link
Member

commented Jun 24, 2017

/sig cli

@k8s-ci-robot k8s-ci-robot added the sig/cli label Jun 24, 2017

@k8s-github-robot k8s-github-robot removed the needs-sig label Jun 24, 2017

@bgrant0607 bgrant0607 removed the team/ux (deprecated - do not use) label Sep 28, 2017

@bgrant0607 bgrant0607 unassigned mikedanese Sep 28, 2017

@fejta-bot

This comment has been minimized.

Sign in to view
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale label Jan 6, 2018

@bgrant0607

This comment has been minimized.

Sign in to view
Copy link
Member

commented Jan 23, 2018

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale label Jan 23, 2018

@fejta-bot

This comment has been minimized.

Sign in to view
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale label Apr 23, 2018

@fejta-bot

This comment has been minimized.

Sign in to view
Copy link

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

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten and removed lifecycle/stale labels May 23, 2018

@fejta-bot

This comment has been minimized.

Sign in to view
Copy link

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

@k8s-ci-robot k8s-ci-robot closed this Jun 22, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.