-
Notifications
You must be signed in to change notification settings - Fork 244
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
Automatically use in-cluster Devfile registries if any #6622
Automatically use in-cluster Devfile registries if any #6622
Conversation
Skipping CI for Draft Pull Request. |
✅ Deploy Preview for odo-docusaurus-preview ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
Addressed in #6545 /override Kubernetes-Integration-Tests/Kubernetes-Docs-Integration-Tests |
@rm3l: Overrode contexts on behalf of rm3l: Kubernetes-Integration-Tests/Kubernetes-Docs-Integration-Tests 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. |
Still to do:
|
dd817cd
to
3ef5a17
Compare
Rebased and force-pushed to fix the conflicts reported. |
Co-authored-by: Philippe Martin <[email protected]>
This is yet to be implemented. Co-authored-by: Philippe Martin <[email protected]>
Signed-off-by: anandrkskd <[email protected]>
Co-authored-by: Philippe Martin <[email protected]>
This should ideally not happen if the registry operator is installed in the cluster (because it validates the URL to make sure it is reachable), but you never know ;-)
Registries might be found in the cluster.
Signed-off-by: Parthvi Vala <[email protected]>
Signed-off-by: Parthvi Vala <[email protected]> Co-authored-by: Armel Soro <[email protected]>
…e cluster or if there are cluster-wide registry lists
CRs are now dynamically created and applied from the tests
85b9a44
to
4afb1c7
Compare
Kudos, SonarCloud Quality Gate passed!
|
/override Kubernetes-Integration-Tests/Kubernetes-Docs-Integration-Tests /lgtm |
@feloy: Overrode contexts on behalf of feloy: Kubernetes-Integration-Tests/Kubernetes-Docs-Integration-Tests, windows-integration-test/Windows-test 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. |
…per#6622) * Add kubeclient as dependency of the registry client Co-authored-by: Philippe Martin <[email protected]> * Add GetRegistryList method to the kube client interface This is yet to be implemented. Co-authored-by: Philippe Martin <[email protected]> * Implement GetRegistryList * adding test if devfileRegistryListCR is present in cluster Signed-off-by: anandrkskd <[email protected]> * Unit tests (to be continued) * Add unit test cases against kclient#GetRegistryList() Co-authored-by: Philippe Martin <[email protected]> * Ignore in-cluster registries with an empty URL This should ideally not happen if the registry operator is installed in the cluster (because it validates the URL to make sure it is reachable), but you never know ;-) * Update error message when trying to remove registry Registries might be found in the cluster. * Pass isSecure value to the registry handler * Make it possible to use in-cluster registries when calling 'odo registry --details' * Remove unused 'preferenceClient' from registry.getRegistryStacks * Handle in-cluster registries in 'odo init' non-interactive mode * Handle in-cluster registries in 'odo init' interactive mode * Add integration test for odo init --devfile-registry Signed-off-by: Parthvi Vala <[email protected]> * Use proxy when available Signed-off-by: Parthvi Vala <[email protected]> Co-authored-by: Armel Soro <[email protected]> * Make sure tests work even if the registry operator is installed in the cluster or if there are cluster-wide registry lists * Add tests for 'odo init' interactive mode * Remove useless CR file CRs are now dynamically created and applied from the tests * fixup! Add tests for 'odo init' interactive mode --------- Signed-off-by: anandrkskd <[email protected]> Signed-off-by: Parthvi Vala <[email protected]> Co-authored-by: Philippe Martin <[email protected]> Co-authored-by: anandrkskd <[email protected]> Co-authored-by: Parthvi Vala <[email protected]>
Co-authored-by: @valaparthvi @feloy @anandrkskd @ritudes
What type of PR is this:
/kind feature
What does this PR do / why we need it:
If connected to a cluster,
odo init
,odo preference view
,odo registry
commands will detect anyDevfileRegistriesList
andClusterDevfileRegistriesList
resources in the cluster, and use the registries listed there.The same behavior applies to
odo dev
andodo deploy
when there is source code but nodevfile.yaml
, as they should start by initializing a Devfile.Per the acceptance criteria, order of registries is as follows:
Which issue(s) this PR fixes:
Fixes #5128
PR acceptance criteria:
Unit test
Integration test
Documentation
How to test changes / Special notes to the reviewer:
odo
preferences, like so: