Dave Protasowski
Dave Protasowski
There's a project tracking this here - https://github.com/knative/serving/projects/47 It seems like folks have added some issues to the GA column since I last looked. A big one for me is...
/unassign @Priyansurout /lifecycle frozen
You shouldn't be changing the checksum - but just applying the new config map
From: https://github.com/knative/serving/pull/14881#issuecomment-2021492474 Yeah the way this feature was implemented it uses name conflicts in the cluster scope to ensure there are no duplicates. If we wanted to support wild cards...
/hold I want to fix https://github.com/knative/serving/issues/14660 prior
Still holding for now see: https://github.com/knative/serving/issues/14567#issuecomment-1949639591 A serving point release came out two weeks ago - that might have fixed the original issue.
> Still holding for now see: [#14567 (comment)](https://github.com/knative/serving/issues/14567#issuecomment-1949639591) > > A serving point release came out two weeks ago - that might have fixed the original issue. The other fix...
@seongpyoHong thanks for the changes /lgtm /approve Are you able to follow up by adding a unit test or an e2e test?
I think integrating makes sense - let's formalize a plan - cause we'll need a migration path for existing users