kapp should support CiliumIdentity
resources out of the box
#748
Labels
bug
This issue describes a defect or unexpected behavior
carvel accepted
This issue should be considered for future work and that the triage process has been completed
priority/important-soon
Must be staffed and worked on currently or soon.
What steps did you take:
I am using [Cilium](https://cilium.io] and I deployed a simple app with a Deployment and a Service.
What happened:
When I delete the app, kapp gets stuck on waiting for the
CiliumIdentity
resource to get deleted by the cluster.What did you expect:
I expected
kapp delete
to succeed.Anything else you would like to add:
When we create a an app using kapp which has a pod resource (like Deployment), then the ownership labels are injected into the Pods and the ReplicaSets as well, and into the
CiliumIdentity
resource in case of GKE autopilot cluster. While deleting the app, sinceCiliumIdentity
is a cluster owned resource, kapp waits for the cluster to delete it, but these resources are not deleted immediately so kapp gets stuck waiting for the cluster to delete them.Slack thread: https://kubernetes.slack.com/archives/CH8KCCKA5/p1683315623187379
Environment:
kapp --version
):/etc/os-release
):kubectl version
)Vote on this request
This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.
👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"
We are also happy to receive and review Pull Requests if you want to help working on this issue.
The text was updated successfully, but these errors were encountered: