add iam crd

Signed-off-by: hongming <talonwan@yunify.com>

vendor/github.com/openshift/api/apps/v1/generated.proto

@@ -7,7 +7,6 @@ package github.com.openshift.api.apps.v1;
 
 import "k8s.io/api/core/v1/generated.proto";
 import "k8s.io/apimachinery/pkg/apis/meta/v1/generated.proto";
-import "k8s.io/apimachinery/pkg/runtime/generated.proto";
 import "k8s.io/apimachinery/pkg/runtime/schema/generated.proto";
 import "k8s.io/apimachinery/pkg/util/intstr/generated.proto";
 
@@ -16,7 +15,7 @@ option go_package = "v1";
 
 // CustomDeploymentStrategyParams are the input to the Custom deployment strategy.
 message CustomDeploymentStrategyParams {
-  // Image specifies a Docker image which can carry out a deployment.
+  // Image specifies a container image which can carry out a deployment.
   optional string image = 1;
 
   // Environment holds the environment which will be given to the container for Image.
@@ -68,25 +67,24 @@ message DeploymentCondition {
 // A single deployment configuration is usually analogous to a single micro-service. Can support many different
 // deployment patterns, including full restart, customizable rolling updates, and  fully custom behaviors, as
 // well as pre- and post- deployment hooks. Each individual deployment is represented as a replication controller.
-// 
+//
 // A deployment is "triggered" when its configuration is changed or a tag in an Image Stream is changed.
 // Triggers can be disabled to allow manual control over a deployment. The "strategy" determines how the deployment
 // is carried out and may be changed at any time. The `latestVersion` field is updated when a new deployment
 // is triggered by any means.
 message DeploymentConfig {
-  // Standard object's metadata.
   optional k8s.io.apimachinery.pkg.apis.meta.v1.ObjectMeta metadata = 1;
 
   // Spec represents a desired deployment state and how to deploy to it.
   optional DeploymentConfigSpec spec = 2;
 
   // Status represents the current deployment state.
+  // +optional
   optional DeploymentConfigStatus status = 3;
 }
 
 // DeploymentConfigList is a collection of deployment configs.
 message DeploymentConfigList {
-  // Standard object's metadata.
   optional k8s.io.apimachinery.pkg.apis.meta.v1.ListMeta metadata = 1;
 
   // Items is a list of deployment configs
@@ -362,7 +360,7 @@ message ExecNewPodHook {
   repeated k8s.io.api.core.v1.EnvVar env = 2;
 
   // ContainerName is the name of a container in the deployment pod template
-  // whose Docker image will be used for the hook pod's container.
+  // whose container image will be used for the hook pod's container.
   optional string containerName = 3;
 
   // Volumes is a list of named volumes from the pod template which should be
@@ -422,9 +420,9 @@ message RollingDeploymentStrategyParams {
   // during the update. Value can be an absolute number (ex: 5) or a
   // percentage of total pods at the start of update (ex: 10%). Absolute
   // number is calculated from percentage by rounding down.
-  // 
+  //
   // This cannot be 0 if MaxSurge is 0. By default, 25% is used.
-  // 
+  //
   // Example: when this is set to 30%, the old RC can be scaled down by 30%
   // immediately when the rolling update starts. Once new pods are ready, old
   // RC can be scaled down further, followed by scaling up the new RC,
@@ -436,9 +434,9 @@ message RollingDeploymentStrategyParams {
   // original number of pods. Value can be an absolute number (ex: 5) or a
   // percentage of total pods at the start of the update (ex: 10%). Absolute
   // number is calculated from percentage by rounding up.
-  // 
+  //
   // This cannot be 0 if MaxUnavailable is 0. By default, 25% is used.
-  // 
+  //
   // Example: when this is set to 30%, the new RC can be scaled up by 30%
   // immediately when the rolling update starts. Once old pods have been
   // killed, new RC can be scaled up further, ensuring that total number of