-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MutatingAdmissionWebhook is not working on OpenShift 3.11 #1298
Comments
/kind bug |
Is there a chance to extend Tektons CI with OpenShift? We've had quite a few problems in the past with that combination. Would be really good to have a vanilla Tekton tested continously against a vanilla OpenShift. |
So, we need to document this, as :
We have that downstream, aka in |
With the recent move to Kubernetes 1.15 being the lowest version supported, Tekton officially can't run on OpenShift 3.11 (starting at 0.11 release of Tekton), meaning OpenShift 3.11 is officially not supported by Tekton. /close |
@vdemeester: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Expected Behavior
The type of the Tekton param default is
string
. So the param type is optional. The mutatingadmissionwebhook set the default type when the custom resource (e.g. task) is created with missing default values.Actual Behavior
The taskrun for the task that has some params with unspecified type fails on OpenShift 3.11. The error is:
invalid input params: param types don''t match the user-specified type: [pathToDockerFile pathToContext]
The MutatingAdmissionWebhook in the tekton-pipelines-webhook is not called at all on OpenShift 3.11. So the default values are not set. Here is some OpenShift system info:
Steps to Reproduce the Problem
The taskrun fails with the error:
invalid input params: param types don''t match the user-specified type: [pathToDockerFile pathToContext]
Additional Info
The text was updated successfully, but these errors were encountered: