search

kubernetes / client-go

Go client for Kubernetes.
Apache License 2.0
9.12k stars 2.95k forks source link

Missing Kubernetes Labels for Nodes in GKE Cluster after Enabling Image Streaming Feature #1342

Closed Seelam-Ramesh-Reddy closed 2 months ago

Seelam-Ramesh-Reddy commented 7 months ago

After enabling the Image Streaming feature in our Google Kubernetes Engine (GKE) cluster, we've observed that Kubernetes labels for nodes are going missing. This issue seems to be consistently reproducible and affects the proper functioning of our cluster.

Steps to Reproduce:

Enable the Image Streaming feature in the GKE cluster. Observe that Kubernetes labels for nodes are missing or not applied as expected. Expected Behavior: Kubernetes labels for nodes should be retained and applied correctly even after enabling the Image Streaming feature.

Label Name: pool:defaultpool

Actual Behavior: After enabling the Image Streaming feature, Kubernetes labels for nodes are missing or not applied as expected.

ruiwen-zhao commented 7 months ago

Hi @Seelam-Ramesh-Reddy , image streaming is a GKE specific feature, so i would recommend creating a support ticket against GKE.

Or if you can provide some more details and repro steps, we can take a look.

k8s-triage-robot commented 4 months ago

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

This bot triages un-triaged issues according to the following rules:

You can:

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

/lifecycle stale

k8s-triage-robot commented 3 months ago

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

This bot triages un-triaged issues according to the following rules:

You can:

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

/lifecycle rotten

k8s-triage-robot commented 2 months ago

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

This bot triages issues according to the following rules:

You can:

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

/close not-planned

k8s-ci-robot commented 2 months ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes/client-go/issues/1342#issuecomment-2320285203): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages 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: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.