Fixing small linter complaints (#302)

Author: kfswain

api/v1alpha1/inferencemodel_types.go

@@ -202,7 +202,7 @@ type InferenceModelConditionType string
 type InferenceModelConditionReason string
 
 const (
-	// This condition indicates if the model config is accepted, and if not, why.
+	// ModelConditionAccepted indicates if the model config is accepted, and if not, why.
 	//
 	// Possible reasons for this condition to be True are:
 	//
@@ -218,14 +218,14 @@ const (
 	//
 	ModelConditionAccepted InferenceModelConditionType = "Accepted"
 
-	// Desired state. Model conforms to the state of the pool.
+	// ModelReasonAccepted is the desired state. Model conforms to the state of the pool.
 	ModelReasonAccepted InferenceModelConditionReason = "Accepted"
 
-	// This reason is used when a given ModelName already exists within the pool.
+	// ModelReasonNameInUse is used when a given ModelName already exists within the pool.
 	// Details about naming conflict resolution are on the ModelName field itself.
 	ModelReasonNameInUse InferenceModelConditionReason = "ModelNameInUse"
 
-	// This reason is the initial state, and indicates that the controller has not yet reconciled the InferenceModel.
+	// ModelReasonPending is the initial state, and indicates that the controller has not yet reconciled the InferenceModel.
 	ModelReasonPending InferenceModelConditionReason = "Pending"
 )
 

api/v1alpha1/inferencepool_types.go

@@ -207,7 +207,7 @@ type InferencePoolConditionType string
 type InferencePoolConditionReason string
 
 const (
-	// This condition indicates if the pool is ready to accept traffic, and if not, why.
+	// PoolConditionReady indicates if the pool is ready to accept traffic, and if not, why.
 	//
 	// Possible reasons for this condition to be True are:
 	//
@@ -223,13 +223,13 @@ const (
 	//
 	PoolConditionReady InferencePoolConditionType = "Ready"
 
-	// Desired state. The pool and its components are initialized and ready for traffic.
+	// PoolReasonReady is the desired state. The pool and its components are initialized and ready for traffic.
 	PoolReasonReady InferencePoolConditionReason = "Ready"
 
-	// This reason is used when the EPP has not yet passed health checks, or has started failing them.
+	// PoolReasonEPPNotHealthy is used when the EPP has not yet passed health checks, or has started failing them.
 	PoolReasonEPPNotHealthy InferencePoolConditionReason = "EndpointPickerNotHealthy"
 
-	// This reason is the initial state, and indicates that the controller has not yet reconciled this pool.
+	// PoolReasonPending is the initial state, and indicates that the controller has not yet reconciled this pool.
 	PoolReasonPending InferencePoolConditionReason = "Pending"
 )