The revision labels should be a static set

[akyyy]

/area API
/kind bug

Expected Behavior

The revision should have a fixed set of labels. If the set of labels changed, the k8s deployment could end up with multiple replica sets.

Actual Behavior

A temporary solution is just exclude route as label from revision labels.

[mattmoor]

@evankanderson @mdemirhan @vaikas-google

What do we gain by having the Route label on Revisions?

We have Configuration:Revision 1:N enforcement via configuration labels, and Route:Configuration 1:N enforcement via Route labels.

Can we simply stop labelling Revisions with Route?

[grantr]

Can we simply stop labelling Revisions with Route?

I think we should do this anyway because it keeps the data model flexible enough to later support multiple routes targeting a revision (regardless of what #63 says).

[mattmoor]

/assign @mdemirhan

I think you removed the labeling of Revisions, so can we close this?

[mdemirhan]

Yes, we can close this.