That is correct.  If you delete non-pods they go away instantly.

On Fri, Jul 22, 2016 at 10:47 AM, Jordan Liggitt <[email protected]>
wrote:

> Actually, I think deletionTimestamp currently only appears for gracefully
> deleted resources (currently just pods), where a delete request is first
> persisted as an update, then later deleted
>
> On Jul 22, 2016, at 9:14 AM, Jordan Liggitt <[email protected]> wrote:
>
> When outputting as yaml, the metadata.deletionTimestamp is all that could
> be shown if the output is to remain a valid object definition. Is that not
> appearing?
>
> On Jul 22, 2016, at 9:12 AM, Andy Goldstein <[email protected]> wrote:
>
> While the events have that info, kubectl isn't currently coded to look at
> the event type and display it to the user to clearly indicate a deletion.
>
> On Fri, Jul 22, 2016 at 9:09 AM, Jordan Liggitt <[email protected]>
> wrote:
>
>> Watch events include the type of event, along with the object:
>> ADDED, MODIFIED, DELETED, or ERROR
>>
>> Additionally, deleted objects should have a metadata.deletionTimestamp set
>>
>>
>>
>> > On Jul 22, 2016, at 9:05 AM, Tobias Florek <[email protected]>
>> wrote:
>> >
>> > Hi.
>> >
>> > I am speaking about origin 1.2.1 behavior. If that is fixed in more
>> > recent versions, please tell me!
>> >
>> > When watching routes, one gets newly created and status-changed routes
>> > as expected. What I did not expect was getting deleted routes with no
>> > indication, that the route is going to be deleted.
>> >
>> > How can I filter/recognize the delete events without checking the route
>> > explicitly via `oc get route <the_route>`?
>> >
>> > Example:
>> >
>> > In one terminal:
>> >
>> >> oc expose <some_service> --... (to create a route to play with)
>> >> oc get routes --watch-only -o yaml
>> >
>> > In another terminal:
>> >
>> >> oc delete route <some_service>
>> >
>> > This will show the complete route in the first terminal, with no
>> > indication that the route is going to be deleted.
>> >
>> >
>> > Cheers,
>> > Tobias Florek
>> > _______________________________________________
>> > users mailing list
>> > [email protected]
>> > http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>>
>> _______________________________________________
>> users mailing list
>> [email protected]
>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>>
>
>
> _______________________________________________
> users mailing list
> [email protected]
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>
>
_______________________________________________
users mailing list
[email protected]
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Reply via email to