Nikhil Thomas
Nikhil Thomas
This issue is to make sure that all defaulting logic is moved to the location where all the other defaulting logic lives. For example: The following items could be something...
At present, CRDs like TektonPipeline, TektonTriggers, TektonDashboard etc, store name of the TektonInstallerSet Instances in their Status. This was required as the active TektonInstaller set was fetched (Get) using the...
### Feature request At present, whenever we use an InstallerSet instance to create/edit a resource, the installer set instance adds itself as an ownerReference. This addition of ownerReference is useful...
# Expected Behavior Deleting TektonConfig Instance should delete instances of TektonPipelines, TektonTriggers etc and the reconciler should not respond to that by trying to create TektonPipelines instances again. # Actual...
# Expected Behavior All of the transformers applied in any reconciler should apply to all kubernetes resources except when a skip logic is explicitly mentioned. # Actual Behavior Most of...
### Feature request At present, the `fetch-releases.sh` script fetches (`curl`) every time it is run. Adding a shortlived cache (ttl: 1day) could make the development experience better. 🧑💻 ### Use...
# Expected Behavior All e2e tests should pass # Actual Behavior while running e2e tests on OpenShift 2 tests are failing ``` --- FAIL: TestTektonConfigDeployment/validate-addon-params (0.60s) --- FAIL: TestTektonConfigDeployment/disable-pac (11.09s)...
At present, the images built in the versioned tektoncd/operator release pipelines are not signed by the tekton/chains instance running on plumbing cluster. We need to modify the tektoncd/operator release pipeline...
At present, in the transformer unit tests assertions are not uniform. The end transformation is verified in each tests based on the logic of the transformer. This means, knowledge of...
In some of our e2e tests our assertions check only whether the CRD instance got deleted ([example](https://github.com/tektoncd/operator/blob/5dd15099eca57afe50d01c290c0a6423ad534cf7/test/e2e/common/00_tektonconfigdeployment_test.go#L148)). From an e2e test prespective the check should ensure the deployments were cleaned...