Removing ConfigMap as suggestion for IngressClass parameters

As this is a a local object reference from a global object, referencing a ConfigMap would not be possible. Controller specific custom resources are a much better fit here, allowing for better validation.

Author: robscott

api/openapi-spec/swagger.json

@@ -297,10 +297,9 @@ type IngressClassSpec struct {
 	// "acme.io/ingress-controller". This field is immutable.
 	Controller string
 
-	// Parameters is a link to a resource containing additional configuration
-	// for the controller. This is optional if the controller does not require
-	// extra parameters. Example configuration resources include
-	// `core.ConfigMap` or a controller specific Custom Resource.
+	// Parameters is a link to a custom resource containing additional
+	// configuration for the controller. This is optional if the controller does
+	// not require extra parameters.
 	// +optional
 	Parameters *api.TypedLocalObjectReference
 }

pkg/apis/networking/types.go

@@ -298,10 +298,9 @@ type IngressClassSpec struct {
 	// "acme.io/ingress-controller". This field is immutable.
 	Controller string `json:"controller,omitempty" protobuf:"bytes,1,opt,name=controller"`
 
-	// Parameters is a link to a resource containing additional configuration
-	// for the controller. This is optional if the controller does not require
-	// extra parameters. Example configuration resources include
-	// `core.ConfigMap` or a controller specific Custom Resource.
+	// Parameters is a link to a custom resource containing additional
+	// configuration for the controller. This is optional if the controller does
+	// not require extra parameters.
 	// +optional
 	Parameters *v1.TypedLocalObjectReference `json:"parameters,omitempty" protobuf:"bytes,2,opt,name=parameters"`
 }