Skip to content

Watch.Response with type ADDED does not provide object's data #3215

Open

Description

@mnlipp

Describe the bug

If the response received from calling GenericKubernetesApi.watch has type "ADDED", the KubernetesObject in object has only metadata. raw is empty (null). (The object's raw data is provided for type "MODIFIED")

Client Version
v19

Java Version
Java 17

To Reproduce
Call the method, add a Kubernetes object, look at the result.

Expected behavior
The (raw) data should be provided.

Activity

  1. k8s-triage-robot commented on Jun 14, 2024

    @k8s-triage-robot

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

    This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
    • Close this issue with /close
    • Offer to help out with Issue Triage

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

    /lifecycle stale

  2. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Jun 14, 2024
  3. mnlipp commented on Jun 14, 2024

    @mnlipp
    Author

    /remove-lifecycle stale

  4. removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Jun 14, 2024
  5. k8s-triage-robot commented on Sep 12, 2024

    @k8s-triage-robot

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

    This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
    • Close this issue with /close
    • Offer to help out with Issue Triage

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

    /lifecycle stale

  6. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Sep 12, 2024
  7. mnlipp commented on Sep 12, 2024

    @mnlipp
    Author

    /remove-lifecycle stale

  8. removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Sep 12, 2024
  9. k8s-triage-robot commented on Dec 11, 2024

    @k8s-triage-robot

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

    This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
    • Close this issue with /close
    • Offer to help out with Issue Triage

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

    /lifecycle stale

  10. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Dec 11, 2024
  11. mnlipp commented on Dec 14, 2024

    @mnlipp
    Author

    /remove-lifecycle stale

  12. removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Dec 14, 2024
  13. k8s-triage-robot commented on Mar 14, 2025

    @k8s-triage-robot

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

    This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
    • Close this issue with /close
    • Offer to help out with Issue Triage

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

    /lifecycle stale

  14. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Mar 14, 2025
  15. mnlipp commented on Mar 15, 2025

    @mnlipp
    Author

    /remove-lifecycle stale

  16. 7 remaining items

  17. mnlipp commented on Sep 19, 2025

    @mnlipp
    Author

    /remove-lifecycle stale

  18. removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Sep 19, 2025
  19. k8s-triage-robot commented on Feb 15, 2026

    @k8s-triage-robot

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

    This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
    • Close this issue with /close
    • Offer to help out with Issue Triage

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

    /lifecycle stale

  20. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Feb 15, 2026
  21. mnlipp commented on Feb 16, 2026

    @mnlipp
    Author

    /remove-lifecycle stale

  22. removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Feb 16, 2026
  23. k8s-triage-robot commented on May 17, 2026

    @k8s-triage-robot

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

    This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
    • Close this issue with /close
    • Offer to help out with Issue Triage

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

    /lifecycle stale

  24. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on May 17, 2026
  25. mnlipp commented on May 17, 2026

    @mnlipp
    Author

    /remove-lifecycle stale

  26. removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on May 17, 2026
  27. k8s-triage-robot commented on Oct 18, 2026

    @k8s-triage-robot

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

    This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
    • Close this issue with /close
    • Offer to help out with Issue Triage

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

    /lifecycle stale

  28. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Oct 18, 2026
  29. mnlipp commented on Oct 20, 2026

    @mnlipp
    Author

    /remove-lifecycle stale

  30. removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Oct 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions