Adds ExperimentalSecretApplySecretTemplateControllerMinKubernetesVTODO to cert-manager feature gate env vars#611
Conversation
to cert-manager feature gate env vars Signed-off-by: joshvanl <vleeuwenjoshua@gmail.com>
|
/lgtm (as requested in slack!) |
SgtCoDFish
left a comment
There was a problem hiding this comment.
Different repos needing different approvals makes me sad :(
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: JoshVanL, SgtCoDFish The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@JoshVanL: Updated the
DetailsIn 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. |
|
Ah, unfortunately this blocks e2e tests on every other PR which isn't based off this one because currently an unknown feature gate flag is a critical error. e.g. The
|
|
@JoshVanL I do not see the settings for this project. Could you disable "require a pull request before merging" (we have that disabled on the cert-manager repository)? Thanks! |
|
@JoshVanL I (wrongly) thought it would solve the disparity in how jetstack-bot behaves with regards to approval between the cert-manager repository and the testing repository. Thinking a second time about it, this issue does not come from the GitHub settings and probably comes from the configuration of jetstack-bot. Where do you think we can fix this? |

Currently set to
truein both feature groups to test which Kubernetes versions work with this feature.The name currently has
vTODOuntil we find out what is the minimum Kubernetes version this works with.