Tagging of Kuryr-created resources

Registered by Michal Dulko on 2019-02-12

If we consider a K8s cluster running on OpenStack VM's, which is a perfect use case for Kuryr-Kubernetes, we can easily imagine creating multiple clusters in a single OpenStack public or private cloud. In such use case those K8s clusters may come and go. As Kuryr is creating some OpenStack resources, such as networks, subnets, floating IP's or SG's, it's useful to have a way of identifying those Kuryr-created resources to delete them along with the K8s cluster that used them.

A way to achieve that would be to use Neutron tags to tag Kuryr-created resources with a configurable tag.

Blueprint information

Status:
Started
Approver:
Antoni Segura Puimedon
Priority:
Undefined
Drafter:
Michal Dulko
Direction:
Needs approval
Assignee:
Michal Dulko
Definition:
Review
Series goal:
None
Implementation:
Needs Code Review
Milestone target:
None
Started by
Michal Dulko on 2019-03-08

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/kuryr-resources-tagging,n,z

Addressed by: https://review.openstack.org/636586
    Add option to tag all resources created by Kuryr

Addressed by: https://review.openstack.org/638258
    Switch Octavia API calls to openstacksdk

Addressed by: https://review.openstack.org/638483
    Add option to tag Octavia resources created by us

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.