kubernetes/hack/testdata
Anders Eknert b423216a3b Presence of bearer token should cancel exec action
If a bearer token is present in a request, the exec credential plugin should accept that as the chosen method of authentication. Judging by an [earlier comment in exec.go](c18bc7e9f7/staging/src/k8s.io/client-go/plugin/pkg/client/auth/exec/exec.go (L217)), this was already intended. This would however not work since UpdateTransportConfig would set the GetCert callback which would then get called by the transport, triggering the exec plugin action even with a token present in the request. See linked issue for further details.

See #87369 for further details.

Signed-off-by: Anders Eknert <anders.eknert@bisnode.com>
2020-07-02 12:12:32 +02:00
..
CRD
diff
filter
kustomize
null-propagation Switch test manifests to apps/v1, remove beta workloads calls 2019-06-22 13:58:07 -07:00
prune Prune should respect namespace 2019-09-25 16:43:08 -07:00
prune-reap
recursive
retainKeys/deployment
sorted-pods
auth-tokens.csv
ca.crt Presence of bearer token should cancel exec action 2020-07-02 12:12:32 +02:00
configmap.yaml
csr.yml
deployment-label-change1.yaml Switch test manifests to apps/v1, remove beta workloads calls 2019-06-22 13:58:07 -07:00
deployment-label-change2.yaml Switch test manifests to apps/v1, remove beta workloads calls 2019-06-22 13:58:07 -07:00
deployment-label-change3.yaml Switch test manifests to apps/v1, remove beta workloads calls 2019-06-22 13:58:07 -07:00
deployment-multicontainer-resources.yaml
deployment-multicontainer.yaml
deployment-revision1.yaml
deployment-revision2.yaml
deployment-with-UnixUserID.yaml
dockerconfig.json Fix kubectl create secret docker-registry 2020-05-15 12:14:03 +08:00
frontend-controller.yaml
frontend-replicaset.yaml
invalid-pod.yaml kubectl-diff: Test return code on failure and changes 2020-01-21 15:34:22 -08:00
invalid-rc-with-empty-args.yaml
kubernetes-service.yaml
list.yaml
multi-resource-1.yaml Even with build error, kubectl apply should apply all valid resources 2020-04-04 15:48:31 -07:00
multi-resource-2.yaml Even with build error, kubectl apply should apply all valid resources 2020-04-04 15:48:31 -07:00
multi-resource-3.yaml Even with build error, kubectl apply should apply all valid resources 2020-04-04 15:48:31 -07:00
multi-resource-4.yaml Even with build error, kubectl apply should apply all valid resources 2020-04-04 15:48:31 -07:00
multi-resource-json-modify.json
multi-resource-json.json
multi-resource-list-modify.json
multi-resource-list.json
multi-resource-rclist-modify.json
multi-resource-rclist.json
multi-resource-svclist-modify.json
multi-resource-svclist.json
multi-resource-yaml-modify.yaml
multi-resource-yaml.yaml
OWNERS
pod-apply.yaml
pod-changed.yaml
pod-with-api-env.yaml
pod-with-large-name.yaml
pod-with-precision.json bump pause to 3.2 in hack/ 2020-02-14 14:03:19 -08:00
pod.yaml
README.md Ensure testing credentials are labeled as such 2020-02-04 10:36:05 -08:00
redis-slave-replicaset.yaml
rollingupdate-daemonset-rv2.yaml
rollingupdate-daemonset.yaml
rollingupdate-statefulset-rv2.yaml Switch test manifests to apps/v1, remove beta workloads calls 2019-06-22 13:58:07 -07:00
rollingupdate-statefulset.yaml Switch test manifests to apps/v1, remove beta workloads calls 2019-06-22 13:58:07 -07:00
scale-deploy-1.yaml
scale-deploy-2.yaml
scale-deploy-3.yaml
secret.yaml
service-revision1.yaml
service-revision2.yaml
tls.crt
tls.key

Keys in this directory are generated for testing purposes only.