refactor: upgrade kube client version to v0.19.6. Fixes argoproj#4425, …

…argoproj#4791 (argoproj#4810)

Signed-off-by: J.P. Zivalich <[email protected]>

Makefile

@@ -131,11 +131,11 @@ define protoc
  -I ./vendor \
  -I ${GOPATH}/src \
  -I ${GOPATH}/pkg/mod/github.com/gogo/[email protected]/gogoproto \
- -I ${GOPATH}/pkg/mod/github.com/grpc-ecosystem/grpc-gateway@v1.12.2/third_party/googleapis \
+ -I ${GOPATH}/pkg/mod/github.com/grpc-ecosystem/grpc-gateway@v1.16.0/third_party/googleapis \
  --gogofast_out=plugins=grpc:${GOPATH}/src \
  --grpc-gateway_out=logtostderr=true:${GOPATH}/src \
  --swagger_out=logtostderr=true,fqn_for_swagger_name=true:. \
- $(1) 2>&1 | grep -v 'warning: Import .* is unused'
+ $(1)
 endef
 # docker_build,image_name,binary_name,marker_file_name
 define docker_build
@@ -321,7 +321,7 @@ pkg/apis/workflow/v1alpha1/generated.proto: $(GOPATH)/bin/go-to-protobuf $(PROTO
  --go-header-file=./hack/custom-boilerplate.go.txt \
  --packages=github.com/argoproj/argo/pkg/apis/workflow/v1alpha1 \
  --apimachinery-packages=+k8s.io/apimachinery/pkg/util/intstr,+k8s.io/apimachinery/pkg/api/resource,k8s.io/apimachinery/pkg/runtime/schema,+k8s.io/apimachinery/pkg/runtime,k8s.io/apimachinery/pkg/apis/meta/v1,k8s.io/api/core/v1,k8s.io/api/policy/v1beta1 \
- --proto-import ./vendor 2>&1 | grep -v 'warning: Import .* is unused'
+ --proto-import ./vendor
  touch pkg/apis/workflow/v1alpha1/generated.proto
 
 # this target will also create a .pb.go and a .pb.gw.go file, but in Make 3 we cannot use _grouped target_, instead we must choose
@@ -504,7 +504,7 @@ pkg/apis/workflow/v1alpha1/openapi_generated.go: $(GOPATH)/bin/openapi-gen $(TYP
 
 # generates many other files (listers, informers, client etc).
 pkg/apis/workflow/v1alpha1/zz_generated.deepcopy.go: $(TYPES)
- bash ${GOPATH}/pkg/mod/k8s.io/code-generator@v0.17.5/generate-groups.sh \
+ bash ${GOPATH}/pkg/mod/k8s.io/code-generator@v0.19.6/generate-groups.sh \
  "deepcopy,client,informer,lister" \
  github.com/argoproj/argo/pkg/client github.com/argoproj/argo/pkg/apis \
  workflow:v1alpha1 \

api/jsonschema/schema.json

@@ -14,6 +14,26 @@
  },
  "type": "object"
  },
+ "grpc.gateway.runtime.Error": {
+ "properties": {
+ "code": {
+ "type": "integer"
+ },
+ "details": {
+ "items": {
+ "$ref": "#/definitions/google.protobuf.Any"
+ },
+ "type": "array"
+ },
+ "error": {
+ "type": "string"
+ },
+ "message": {
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
  "grpc.gateway.runtime.StreamError": {
  "properties": {
  "details": {
@@ -764,7 +784,6 @@
  "type": "string"
  },
  "emailVerified": {
- "format": "boolean",
  "type": "boolean"
  },
  "groups": {
@@ -1691,7 +1710,7 @@
  },
  "startupProbe": {
  "$ref": "#/definitions/io.k8s.api.core.v1.Probe",
- "description": "StartupProbe indicates that the Pod has successfully initialized. If specified, no other probes are executed until this completes successfully. If this probe fails, the Pod will be restarted, just as if the livenessProbe failed. This can be used to provide different probe parameters at the beginning of a Pod's lifecycle, when it might take a long time to load data or warm a cache, than during steady-state operation. This cannot be updated. This is an alpha feature enabled by the StartupProbe feature flag. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes"
+ "description": "StartupProbe indicates that the Pod has successfully initialized. If specified, no other probes are executed until this completes successfully. If this probe fails, the Pod will be restarted, just as if the livenessProbe failed. This can be used to provide different probe parameters at the beginning of a Pod's lifecycle, when it might take a long time to load data or warm a cache, than during steady-state operation. This cannot be updated. This is a beta feature enabled by the StartupProbe feature flag. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes"
  },
  "stdin": {
  "description": "Whether this container should allocate a buffer for stdin in the container runtime. If this is not set, reads from stdin in the container will always result in EOF. Default is false.",
@@ -1714,7 +1733,7 @@
  "type": "boolean"
  },
  "volumeDevices": {
- "description": "volumeDevices is the list of block devices to be used by the container. This is a beta feature.",
+ "description": "volumeDevices is the list of block devices to be used by the container.",
  "items": {
  "$ref": "#/definitions/io.k8s.api.core.v1.VolumeDevice"
  },
@@ -2259,7 +2278,7 @@
  },
  "startupProbe": {
  "$ref": "#/definitions/io.k8s.api.core.v1.Probe",
- "description": "StartupProbe indicates that the Pod has successfully initialized. If specified, no other probes are executed until this completes successfully. If this probe fails, the Pod will be restarted, just as if the livenessProbe failed. This can be used to provide different probe parameters at the beginning of a Pod's lifecycle, when it might take a long time to load data or warm a cache, than during steady-state operation. This cannot be updated. This is an alpha feature enabled by the StartupProbe feature flag. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes"
+ "description": "StartupProbe indicates that the Pod has successfully initialized. If specified, no other probes are executed until this completes successfully. If this probe fails, the Pod will be restarted, just as if the livenessProbe failed. This can be used to provide different probe parameters at the beginning of a Pod's lifecycle, when it might take a long time to load data or warm a cache, than during steady-state operation. This cannot be updated. This is a beta feature enabled by the StartupProbe feature flag. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes"
  },
  "stdin": {
  "description": "Whether this container should allocate a buffer for stdin in the container runtime. If this is not set, reads from stdin in the container will always result in EOF. Default is false.",
@@ -2282,7 +2301,7 @@
  "type": "boolean"
  },
  "volumeDevices": {
- "description": "volumeDevices is the list of block devices to be used by the container. This is a beta feature.",
+ "description": "volumeDevices is the list of block devices to be used by the container.",
  "items": {
  "$ref": "#/definitions/io.k8s.api.core.v1.VolumeDevice"
  },
@@ -2434,7 +2453,6 @@
  "type": "string"
  },
  "serverDryRun": {
- "format": "boolean",
  "type": "boolean"
  },
  "workflow": {
@@ -2529,7 +2547,6 @@
  "io.argoproj.workflow.v1alpha1.WorkflowResubmitRequest": {
  "properties": {
  "memoized": {
- "format": "boolean",
  "type": "boolean"
  },
  "name": {
@@ -2567,7 +2584,6 @@
  "type": "string"
  },
  "restartSuccessful": {
- "format": "boolean",
  "type": "boolean"
  }
  },
@@ -3880,6 +3896,20 @@
  },
  "type": "object"
  },
+ "io.k8s.api.core.v1.EphemeralVolumeSource": {
+ "description": "Represents an ephemeral volume that is handled by a normal storage driver.",
+ "properties": {
+ "readOnly": {
+ "title": "Specifies a read-only configuration for the volume.\nDefaults to false (read/write).\n+optional",
+ "type": "boolean"
+ },
+ "volumeClaimTemplate": {
+ "$ref": "#/definitions/io.k8s.api.core.v1.PersistentVolumeClaimTemplate",
+ "description": "Will be used to create a stand-alone PVC to provision the volume.\nThe pod in which this EphemeralVolumeSource is embedded will be the\nowner of the PVC, i.e. the PVC will be deleted together with the\npod. The name of the PVC will be `\u003cpod name\u003e-\u003cvolume name\u003e` where\n`\u003cvolume name\u003e` is the name from the `PodSpec.Volumes` array\nentry. Pod validation will reject the pod if the concatenated name\nis not valid for a PVC (for example, too long).\n\nAn existing PVC with that name that is not owned by the pod\nwill *not* be used for the pod to avoid using an unrelated\nvolume by mistake. Starting the pod is then blocked until\nthe unrelated PVC is removed. If such a pre-created PVC is\nmeant to be used by the pod, the PVC has to updated with an\nowner reference to the pod once the pod exists. Normally\nthis should not be necessary, but it may be useful when\nmanually reconstructing a broken cluster.\n\nThis field is read-only and no changes will be made by Kubernetes\nto the PVC after it has been created.\n\nRequired, must not be nil."
+ }
+ },
+ "type": "object"
+ },
  "io.k8s.api.core.v1.Event": {
  "description": "Event is a report of an event somewhere in the cluster.",
  "properties": {
@@ -4648,6 +4678,20 @@
  },
  "type": "object"
  },
+ "io.k8s.api.core.v1.PersistentVolumeClaimTemplate": {
+ "description": "PersistentVolumeClaimTemplate is used to produce\nPersistentVolumeClaim objects as part of an EphemeralVolumeSource.",
+ "properties": {
+ "metadata": {
+ "$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta",
+ "description": "May contain labels and annotations that will be copied into the PVC\nwhen creating it. No other fields are allowed and will be rejected during\nvalidation.\n\n+optional"
+ },
+ "spec": {
+ "$ref": "#/definitions/io.k8s.api.core.v1.PersistentVolumeClaimSpec",
+ "description": "The specification for the PersistentVolumeClaim. The entire content is\ncopied unchanged into the PVC that gets created from this\ntemplate. The same fields as in a PersistentVolumeClaim\nare also valid here."
+ }
+ },
+ "type": "object"
+ },
  "io.k8s.api.core.v1.PersistentVolumeClaimVolumeSource": {
  "description": "PersistentVolumeClaimVolumeSource references the user's PVC in the same namespace. This volume finds the bound PV and mounts that volume for the pod. A PersistentVolumeClaimVolumeSource is, essentially, a wrapper around another type of volume that is owned by someone else (the system).",
  "properties": {