remove admission again, datastructure is now validating itself for the most part

On-behalf-of: @SAP [email protected]

Author: xrstf

internal/admission/publishedresource/validation.go

@@ -24,7 +24,6 @@ import (
 	"github.com/kcp-dev/logicalcluster/v3"
 	"go.uber.org/zap"
 
-	"github.com/kcp-dev/api-syncagent/internal/admission/publishedresource"
 	"github.com/kcp-dev/api-syncagent/internal/controller/sync"
 	"github.com/kcp-dev/api-syncagent/internal/controller/syncmanager/lifecycle"
 	"github.com/kcp-dev/api-syncagent/internal/controllerutil"
@@ -275,16 +274,6 @@ func (r *Reconciler) ensureSyncControllers(ctx context.Context, log *zap.Sugared
 			continue
 		}
 
-		// If the PR is invalid, do not even start a controller for it. Since the $key contains
-		// the resource version, if the invalidt PR is fixed, a new controller can be spawned.
-		// In the future, validation issues like this should be caught by a validation webhook
-		// or more advanced CEL-based validations on the CRD itself, rather than validating in
-		// a controller.
-		if err := publishedresource.ValidatePublishedResource(&pubRes); err != nil {
-			log.Errorw("Not starting controller for published resource because of errors", zap.Error(err), "pr", pubRes.Name)
-			continue
-		}
-
 		log.Infow("Starting new sync controller…", "key", key)
 
 		// create the sync controller;