Timothy Smith

Wrong CRD may be referenced by Custom Resource with duplicate Kind

1

# Bug report Currently, `DeployTask#discover_resources` is the following: ```ruby def discover_resources @logger.info("Discovering resources:") resources = [] crds_by_kind = cluster_resource_discoverer.crds.group_by(&:kind) @template_sets.with_resource_definitions(current_sha: @current_sha, bindings: @bindings) do |r_def| crd = crds_by_kind[r_def["kind"]]&.first r =...

Implement repeatable -f flag

7

# Feature request In following our attempt to mimic, as much as possible, `kubectl` syntax, we should make the `--filenames | -f` flag repeatable. This is simple to do (simply...

Server-side dry run can fail when an admission controller does not declare itself as having no side effects. In the case of some of our deploys, we go through the...

# Feature request Following #781, all resources are grouped together in the validation phase and batch-applied against the API server. This includes resources that are otherwise deployed via `create`, `replace`,...

`SerialDeployTest#test_deploying_crs_with_invalid_crd_conditions_fails` appears to be flaky, curiously I've only noticed it exclusively on the 1.18 CI block, though it doesn't seem to have anything to do with k8s version. On first...

see https://github.com/Shopify/krane#using-templates We recommend calling `krane deploy` without showing the required namespace/context args, which is misleading in some cases

Don't instantly fail if redeploying a Deployment past PDS

1

**Proposal:** Currently, if someone attempts to redeploy a deployment in the state `progressDeadlineExceeded`, we instantly fail the deploy. In general, this leads users to think their deploy is fundamentally broken...

CLI flag to add arbitrary metadata fields to audit results

3

# FEATURE IDEA ##### ISSUE TYPE - [ ] Bug Report - [x] Feature Idea - [x] If the maintainers agree with the feature as described here, I intend to...